The solution was to rebuild xscale-elf-gcc and newlib, passing --disable-new-lib_hw_fp to the newlib configure. Without this flag, gcc was trying to initalize a hardware floating point coprocessor, which caused the nodes to crash.
This also solved the problem someone mentioned awhile ago about the "literal needs to be closer to pool" error . Hopefully this will help someone.
John.
On 5/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am trying to do some simple work with the imote2s, but I can't seem to get them to program correctly. The applications will build and program without any errors, but when I restart the node, nothing happens. Here's a quick sample:
------------------------------------------------------------------------------------
~/tinyos-1.x/apps/Blink$ make install imote2 debug
mkdir -p build/imote2
xscale-elf-gcc -c -mcpu=iwmmxt -mfpu=softfpa /home/ledbettj/build/tinyos- 1.x/tos/platform/pxa27x/../imote2/flash.s
<application compiles with a few warnings and no errors>
compiled Blink to build/imote2/main.exe
152256 bytes in ROM
4608 bytes in RAM
xscale-elf-objcopy --output-target=binary build/imote2/main.exe build/imote2/main.bin.out
dwarf2bd build/imote2/main.exe
Intel(R) DWARF2BD Object Converter, Version 2.9.24
Copyright (C) 2001-2005 Intel Corporation. All rights reserved.
installing imote2 binary using the parallel port jtag adapter
/cygdrive/c/Program\ Files/Intel/SDT2.0.1/xflash/xflash.exe -p imote2 -tt "INTEL(R) JTAG CABLE" build/imote2/main.bin.out
XFLASH - Intel(R) JTAG flash memory programmer - Version: 1.5.3
Copyright(C) 2001-2005 Intel Corporation. All rights reserved.
Selected platform: IMOTE2
Task : burn flash
File to burn : build/imote2/main.bin.out
Connecting to target via "lpt1:" ...
JTAG debug handler uses virtual address range 0x01000020..0x010007FF
INFO: To enable Mini-I-cache breakpoints use the "MINIIBP" target option.
take initial batchfile: "c:/Program Files/Intel/SDT2.0.1/xflash/action- flash.xdb"
Memory Successfully Burned.
Prepare the burn algorithm...
Downloading the burn algorithm...finished
Detect and Verify File Format...
Erasing Blocks... Current Block: 0 at address 0x0
Erasing Blocks... Current Block: 1 at address 0x8000
Erasing Blocks... Current Block: 2 at address 0x10000
Erasing Blocks... Current Block: 3 at address 0x18000
Erasing Blocks... Current Block: 4 at address 0x20000
Progress: 100%
Burning Binary File...
Burning Binary File... 148 KBytes of 148 KBytes remaining.
Burning Binary File... 84 KBytes of 148 KBytes remaining.
Burning Binary File... 20 KBytes of 148 KBytes remaining.
Progress: 100%
File successfully burned.
------------------------------------------------------------------------------------
The node is obviously being erased, since it came preloaded with Count to LEDS/RF, and no longer does so, but something is going wrong in the programming. Any ideas?
John Ledbetter
--
========================
John Ledbetter
[EMAIL PROTECTED]
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
