# uCLinux on connect me **URL:** \ **Category:** Linux\ **Tags:** compatibility\ **Created:** [May 13, 2004, 10:44am UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157 "2004-05-13T10:44:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![sijuma00](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@sijuma00](https://forums.digi.com/u/sijuma00)\ **Post date:** [May 13, 2004, 10:44am UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157/1 "2004-05-13T10:44:18Z")
Hi there. Don’t know does this really belong under this category, but it is related to ME. So is there anyone runnin uCLinux on this device? I found a port (armadillo-j) on the net, which is based on Connect ME. Now we have the linux image, but no working bootloader. I’m not very experienced with the GNU toolchain so this might also be my stupidity:P With Armadillo they ship a hermit bootloader (hermitXK.bin) which should work. I’ve tried to program it with naftpapp and it is recognized as proper image -\> flashing starts, but then it stops saying something about image transfer error. And if I have understood correctly, this bootloader should be used to program the “real” linux image to the device. Now I have hermit sources, but it seems I can’t compile a proper image from it - Flash header seems to be different and it is not recognized as proper image (I’m probably missing something here, linker switch maybe - to tell which kind of a header we would need?) Second problem is related to elf files. When I try to load an elf to gdb it says "Dwarf error: Bad offset (0x60000000) in compilation unit header (offset 0x0 +6) We are trying to compile these under linux using arm-elf toolchain 20030314. arm-elf gcc is version 2.95.3. Thanks in advance if someone can help. ---
**Author:** ![joshj](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@joshj](https://forums.digi.com/u/joshj)\ **Post date:** [May 25, 2004, 3:56pm UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157/2 "2004-05-25T15:56:05Z")
I’ve been working on an ARM port of kgdb and ran into the same Dwarf error. In your linker script (a .ld file) you need to add the following lines to force all Dwarf addresses to zero: /\* DWARF 1 \*/ .debug 0 : { \*(.debug) } .line 0 : { _(.line) } /_ GNU DWARF 1 extensions \*/ .debug\_srcinfo 0 : { \*(.debug\_srcinfo) } .debug\_sfnames 0 : { _(.debug\_sfnames) } /_ DWARF 1.1 and DWARF 2 \*/ .debug\_aranges 0 : { \*(.debug\_aranges) } .debug\_pubnames 0 : { _(.debug\_pubnames) } /_ DWARF 2 \*/ .debug\_info 0 : { \*(.debug\_info) } .debug\_abbrev 0 : { \*(.debug\_abbrev) } .debug\_line 0 : { \*(.debug\_line) } .debug\_frame 0 : { \*(.debug\_frame) } .debug\_str 0 : { \*(.debug\_str) } .debug\_loc 0 : { \*(.debug\_loc) } .debug\_macinfo 0 : { _(.debug\_macinfo) } /_ SGI/MIPS DWARF 2 extensions \*/ .debug\_weaknames 0 : { \*(.debug\_weaknames) } .debug\_funcnames 0 : { \*(.debug\_funcnames) } .debug\_typenames 0 : { \*(.debug\_typenames) } .debug\_varnames 0 : { \*(.debug\_varnames) } - Josh ---
**Author:** ![egawtry](https://avatars.discourse-cdn.com/v4/letter/e/8e8cbc/32.png) [@egawtry](https://forums.digi.com/u/egawtry)\ **Post date:** [May 27, 2004, 4:34pm UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157/3 "2004-05-27T16:34:58Z")
I have been looking seriously at uCLinux because of the serious bugs in NetOS. Please post comments during your development to tell us all how it goes. Thanks, -Erik P.S. BTW - How much does the armidillo package cost? I haven’t studied Japanese in 20 years and so can’t read the website. ---
**Author:** ![sijuma00](https://avatars.discourse-cdn.com/v4/letter/s/f6c823/32.png) [@sijuma00](https://forums.digi.com/u/sijuma00)\ **Post date:** [June 2, 2004, 7:11am UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157/4 "2004-06-02T07:11:23Z")
Thanks alot for your help. We were now able to compile the hermit loader, but for the next (newbie) problem. When I try to run the elf in the debugger, i get the following error: (gdb) source …/…/…/gdbconnectme.raven Setting up the environment for debugging gdb. The target is assumed to be big endian …/…/…/gdbconnectme.raven:270: Error in sourced command file: No struct type named bios\_comm. So what are is this bios\_comm and bcomm entries for in the gdbconnectme.raven? Should I just comment them out or…? Any pointers to a documentation are welcome! –Juha ---
**Author:** ![bugfixer](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@bugfixer](https://forums.digi.com/u/bugfixer)\ **Post date:** [May 31, 2004, 10:21am UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157/5 "2004-05-31T10:21:27Z")
egawtry, What are the serious bugs you’re talking about? I’m fighting against a serial port dying without any error code in the several primitives I’m calling, so I’m interested! – bugfixer ---
**Author:** ![egawtry](https://avatars.discourse-cdn.com/v4/letter/e/8e8cbc/32.png) [@egawtry](https://forums.digi.com/u/egawtry)\ **Post date:** [June 8, 2004, 4:38pm UTC](https://forums.digi.com/t/uclinux-on-connect-me/4157/6 "2004-06-08T16:38:03Z")
For the serial port problem, try using a mutex on the output so each thread waits for its turn. That fixed it for me. Also stop using the built-in printf() and putchar() functions. The bugs I was referring to are the Sockets API bugs, specifically the select() bug (it is not reenterant!).