Rick Altherr wrote: >> I start OpenOCD with the command: >> >> openocd -f interface/flyswatter.cfg -f target/hammer.cfg -c "init" -c >> "reset" >> > > Hurray! Someone uses the built-in configs.
By the way, there appears to be a bug/typo inside the hammer.cfg file. Instead of "arm7_9 fast_memory_access enable", it shows "arm7 fast_memory_access enable", which fails. > >> After that, I enter "halt" followed by "debug_level 3" and try to >> flash the Hammer with: >> >> flash write_bank 0 >> /home/cmsa/devel/TCT-Hammer/sources/apex-1.5.6/apex.bin 0x0 >> >> This is what I get back: >> >> Debug: 193 216589 command.c:91 script_command(): script_command - >> write_bank >> Debug: 194 216589 command.c:108 script_command(): script_command - >> write_bank, argv[0]=ocd_flash_write_bank > > [ snip many lines of boring debug logs that essentially mean > "everything was working fine"] > I just wanted to show everything to make sure that no stone was left unturned... >> >> Error: 300 217221 target.c:1794 target_wait_state(): timed out >> while waiting for target debug-running > > But we didn't hit that state in time. This probably has to do with > the fact that the device is already halted. This failure bubbles up > and causes the overall flash to fail. I don't have a arm7_9 based > device to test against, but I suggest someone step through the flash > routine and specifically the arm7_9 run algorithm code. > Yeap, this is where the operation always fails. Thanks! Carlos _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
