Magnus Lundin wrote: > >>>> >>> At the end of the reset handling we reinitialise the tap and the >>> debug interface with omap3_dbginit >>> omap3_reset is really reset+reinit+halt and you call it if you want >>> to debug the loading of u-boot by the X-Loader >> >> Do you mean omap3_reset should be called 'manually' if needed, same >> like omap3_dbginit? >> > Yes, try to use reset and omap3_reset in a telent session and see > what happens, also check the output from BeagleBoard console window > connected to the serial port. >>> New patch attaced. >> >> Tested with 2771 and LEDblink example. No differences seen to svn >> version. >> >> Best regards >> >> Dirk >> >> Btw.: We still have the issue that first load of LEDblink with gdb fails: >> > Are you running gdb from a script ?
No. I just do > arm-none-linux-gnueabi-gdb with > cat .gdbinit echo Setting up the environment for debugging gdb.\n # This connects to OpenOcd at localhost:3333 target remote localhost:3333 # Increase the packet size to improve download speed. set remote memory-write-packet-size 1024 set remote memory-write-packet-size fixed #omap3_dbginit must be run in OpenOCD after every reset monitor omap3_dbginit # Load the program executable called "LEDblink" load LEDblink # Load the symbols for the program. symbol-file LEDblink Dirk _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
