I’m receiving an error when compiling a simple tutorial program. I’ve already researched and found that this seems to be an issue with Vista 64 support. The fix is supposedly here, with a new msys-1.0.dll.
Unfortunately this doesn’t work for me. I’ve found that open-ocd and Yagarto tools directories both have this file. I’ve replaced it in both spots, with no luck.
This inconveniences me a bit, since my main system is unusable for development right now, but I do have a laptop with Vista 32, which will compile just fine, so it’s not a show stopper. I’m just placing this out here in case someone has an answer in the near future.
**** Build of configuration Default for project tutorial-blink-flash ****
make all
.assembling
arm-elf-as -ahls -mapcs-32 -o crt.o crt.s > crt.lst
0 [main] sh 1188 sync_with_child: child 4092(0x1DC) died before initialization with status code 0x0
19 [main] sh 1188 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
make: *** [crt.o] Error 128
Well, like I said, I have another option, so it’s not urgent, but I’d really like to use my main system for development. Working with a larger monitor is so much nicer.
I have a Fedora server, but I’m not using it as a development platform and I’m not going to run a VM just for this. I got my hopes up with the replacement DLL, since it’s exactly the error I’m getting and I was sure that would correct it, but no luck.
I guess I spoke too soon. On my laptop I tried this, and I was able to compile, but I get a problem flashing. Actually, I think it completes the flashing fine, but then it freezes and the little red LED on the ARM-USB-TINY is flashing.
**** Build of configuration Default for project AT91-SAM Blinker Demo ****
make -k program
Flash Programming with OpenOCD...
'C:/Users/Mark/Documents/openocd-r717/bin/'openocd-ftd2xx.exe -f 'C:/Users/Mark/Documents/openocd-r717/bin/'armusbocd_tiny.cfg
Open On-Chip Debugger (2008-06-19 19:00) svn: 717
URL: http://svn.berlios.de/svnroot/repos/openocd/trunk
Info: options.c:50 configuration_output_handler(): jtag_speed: 2, 2
Info: options.c:50 configuration_output_handler(): Open On-Chip Debugger (2008-06-19 19:00) svn: 717
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: 0x3f0f0f0f (Manufacturer: 0x787, Part: 0xf0f0, Version: 0x3)
Info: target.c:237 target_init_handler(): executing reset script 'sam7flash.script'
Info: options.c:50 configuration_output_handler(): core state: ARM
Info: options.c:50 configuration_output_handler(): flash 'at91sam7' found at 0x00100000
Info: options.c:50 configuration_output_handler(): erased sectors 0 through 0 on flash bank 0 in 0.045000s
Info: options.c:50 configuration_output_handler(): cleared protection for sectors 0 through 1 on flash bank 0
Info: options.c:50 configuration_output_handler(): wrote 5064 byte from file main.bin in 0.577500s (8.563312 kb/s)
So it looks like the flash operation completes, and then it’s stuck. Anybody have an idea on this one? I guess I should put this in the OpenOCD forum.
I’m thinking this might be a hardware issue. I went to the evaluation version of Crossworks just to see if I could get it to work. Entered a sample program, compiled it fine, but when I try to send it to the target, I’ve getting a data verification error.
Download complete
Verifying “Loader_rpc.elf” on Olimex ARM-USB-TINY
Verifying
Verifying 4.5 kB of addresses 00200000 — 0020122b
Verifying completed in 88 ms — 52,863 bytes/sec
Verify failed
ARM-USB-TINY and the Olimex SAM7S-256 header board.
Update. Crossworks worked when I changed my USB cable and plugged it into the computer directly rather than through the USB hub I have. I’ll give Yagarto another try on my laptop later, but Crossworks is so much easier and it works on my Vista 64 system, that it might be worth it to me to just pay for the personal license.
