[Openocd-development] at91sam9260 errors

Hi Paul, The software first tells you it found a device with id-code 0xf074203f. Then it tries to tell you that an error has occured. The error is split up into 2 lines. Firt it less you wat it got and then it tells you what it had expected. I also have a board with an at91sam9260 chip. This one

[Openocd-development] at91sam9260 errors

hello, I'm trying to use openocd on our at91sam9260 board. This board works fine and a colleague has been using the j-link with the Segger software just fine. The output from starting is below. It looks like it's doing something, when I run it without the board connected I get "Error: JTAG communi

Re: [Openocd-development] 0.2.0 "FT2232 jtag power-up" bug for various ARMs

Freddie Chopin pisze: > Situation: > Board with STM32 (ARM Cortex-M3) and JTAG based on FT2232 (JTAGkey > clone). OpenOCD 0.2.0 using ftd2xx.dll > > When I connect the JTAG to the PC (power-up) and run OpenOCD I get: > >> Open On-Chip Debugger 0.2.0 (2009-07-19-11:13) Release >> $URL: >> http:/

Re: [Openocd-development] Compile warning on cygwin 32-bit

Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] Split LM3S811 config file into target file and board file

Committed. Thanks! On Sat, Aug 8, 2009 at 1:31 PM, Xiaofan Chen wrote: > The following patch splits LM3S811 config file into target file and board > file. > I also modified the target config file based on the some suggestions of David > Brownell on the LM3S1968 file. > > But I do not have the bo

Re: [Openocd-development] [PATCH] Adding support for X and F GDB Stop ReplyPackets and additional signals

I've looked over the patch and I believe the chances of collateral damage should be minimal + it might be others who want this sort of functionality. Before committing it I believe it requires a bit more work though: - add a configuration command (default disabled) to enable this functionality -

Re: [Openocd-development] Is 16-bit access broken on arm11?

Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [PATCH] Add config file for TI-Luminary LM3S1968 chip and EK-LM3S1968 board

Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] memwrite with burst enabled not working anymore

What interface are you using? Perhaps this is a bug in the interface pathmove driver code rather than arm11 code? -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-d

Re: [Openocd-development] arm11 hangs jtag scan if there is no valid image in boot flash

On Wed, Aug 5, 2009 at 12:43 AM, michal smulski wrote: > > When I erase flash from which arm11 boot, I can no longer attach to JTAG > port of the the arm11. I can still scan-out the the two cores but then > jtag_validate_chain() reports errors (see debug output). > > With a valid image (that basica