Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Marek Vasut
On Monday 13 December 2010 03:27:17 Jon Masters wrote: On Wed, 2010-11-24 at 23:59 -0500, Jon Masters wrote: Has anyone managed to get the TinCanTools Flyswatter working with the XM? I did with the original Beagle, but upstream OCD does this with XM: [...@constitution openocd]$ sudo

Re: [Openocd-development] STM32, openocd and eCos

2010-12-13 Thread Manuel Borchers
Hi Andreas, hi list, On Sun, 2010-12-12 at 21:12 +0100, Andreas Fritiofson wrote: It may be that the scheduler or the idle thread puts the core in low power mode if no thread is ready to run. That will break the debugger connection. See if anything executes a WFI or WFE instruction, and

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Jon Masters
On Mon, 2010-12-13 at 09:45 +0100, Marek Vasut wrote: On Monday 13 December 2010 03:27:17 Jon Masters wrote: Some logic is added to detect CPU cores that report an incorrect ARM DAP (Debug Access Port, exposed behind something called an ICEPick which sits on the JTAG chain and allows

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Marek Vasut
On Monday 13 December 2010 10:00:05 Jon Masters wrote: On Mon, 2010-12-13 at 09:45 +0100, Marek Vasut wrote: On Monday 13 December 2010 03:27:17 Jon Masters wrote: Some logic is added to detect CPU cores that report an incorrect ARM DAP (Debug Access Port, exposed behind something called

Re: [Openocd-development] [beagleboard] Flyswatter with XM

2010-12-13 Thread Jon Masters
On Mon, 2010-12-13 at 10:05 +0100, Marek Vasut wrote: On Monday 13 December 2010 10:00:05 Jon Masters wrote: snip commented out code fixup This is bogus ... I'd prefer extending the detection to be able to identify imx51 in a more precise way. Sure. I was just applying a hack in

Re: [Openocd-development] STM32, openocd and eCos

2010-12-13 Thread Spencer Oliver
On 13/12/2010 08:47, Manuel Borchers wrote: Hi Andreas, hi list, On Sun, 2010-12-12 at 21:12 +0100, Andreas Fritiofson wrote: It may be that the scheduler or the idle thread puts the core in low power mode if no thread is ready to run. That will break the debugger connection. See if anything

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Thu, Nov 25, 2010 at 15:45, Domen Puncer domen.pun...@visionect.si wrote: I can reliably reproduce this one with: jtag_khz 1000 verify_image my_image.elf # some prints about too high clock reset init # openocd aborts Additional info. valgrind: ==32465== Invalid free() / delete /

Re: [Openocd-development] HALT mode lost on SoC reset (CPU switches to RUNNING mode, OpenOCD does not hold it in HALT)

2010-12-13 Thread Drasko DRASKOVIC
On Sat, Dec 11, 2010 at 5:43 AM, Antonio Borneo borneo.anto...@gmail.com wrote: Hi Drasko, your system has an ARM946E. Should have vector_catch capability. Please check if command arm9 vector_catch shows the reset feature. In such case, after set it to catch reset, you can press the reset

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Steve Bennett
On 13/12/2010, at 8:12 PM, Domen Puncer wrote: On Thu, Nov 25, 2010 at 15:45, Domen Puncer domen.pun...@visionect.si wrote: I can reliably reproduce this one with: jtag_khz 1000 verify_image my_image.elf # some prints about too high clock reset init # openocd aborts Additional info.

Re: [Openocd-development] Reseting the SoC gives wrong reset values

2010-12-13 Thread Drasko DRASKOVIC
On Mon, Dec 13, 2010 at 12:14 PM, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote: Hi all, I run into strange behavior with reset of my SoC. I am using arm9 vector_catch reset to catch the reset event from the button on the board, although reset halt gives the similar results, where I

Re: [Openocd-development] Marvell Armada Support

2010-12-13 Thread Paul Richards
Hi Enrico, On 2010/12/05 20:41, Enrico Scholz wrote: Base operations are already possible by Thanks for this, sorry I missed your mail first time around. see [1] for full configuration. The trick is the first dummy TAP which is mentioned in some errata entry (an extra TDO is shifted in

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 8:12 PM, Domen Puncer wrote: but code only allocates space for extra len-1 objects. There is already one slot allocated for the arg. If the arg expands to 'len' elements, we only need to allocate

[Openocd-development] uClinux can not be halted

2010-12-13 Thread Drasko DRASKOVIC
Hi all, I have a setup on ARM946E that works well for loading and booting uClinux, and during the boot phase I can stop and single-step kernel. But once booted, when it gives prompt, pressing CTRL-C in GDB can not halt the board : ^CHalt timed out, wake up GDB. Program received signal SIGINT,

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Steve Bennett
On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 8:12 PM, Domen Puncer wrote: but code only allocates space for extra len-1 objects. There is already one slot allocated for the arg. If the arg

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Mon, Dec 13, 2010 at 20:32, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au wrote: Can we see the code being evaluated here? ==32465==    by 0x4B6DB2: Jim_Eval_Named

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Steve Bennett
On 14/12/2010, at 5:50 AM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 20:32, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au wrote: Can we see the code being evaluated here?

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Mon, Dec 13, 2010 at 21:17, Steve Bennett ste...@workware.net.au wrote: On 14/12/2010, at 5:50 AM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 20:32, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett

Re: [Openocd-development] STM32, openocd and eCos

2010-12-13 Thread Andreas Fritiofson
On Mon, Dec 13, 2010 at 10:16 AM, Spencer Oliver s...@spen-soft.co.uk wrote: On 13/12/2010 08:47, Manuel Borchers wrote: Hi Andreas, hi list, On Sun, 2010-12-12 at 21:12 +0100, Andreas Fritiofson wrote: It may be that the scheduler or the idle thread puts the core in low power mode if no

[Openocd-development] [Fwd: [beagleboard] ICEpick revision greater than C?]

2010-12-13 Thread Jon Masters
FYI. I am able to make the latest Rev B. BeagleBoard-xM operate after making this trivial modification. I'll send a patch when I know more about whether ICEpick has revved and what exactly was changed. Jon. ---BeginMessage--- Hi Gerald, I am trying to update the OpenOCD files for the latest