Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-10 Thread Nick Pelling
Hi everyone, At 07:38 10/12/2010 +0100, Peter Stuge wrote: Tomek CEDRO wrote: (replying to Nick Pelling) I've asked Samsung for documentation listing all its JTAG codes, but that may take some time to Hello Nick, the other problem is that Samsung may want you to sign the NDA and keep

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-09 Thread Peter Stuge
Tomek CEDRO wrote: I've asked Samsung for documentation listing all its JTAG codes, but that may take some time to Hello Nick, the other problem is that Samsung may want you to sign the NDA and keep quiet about the device, as they did when I asked for some documentation for one device

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-06 Thread Nick Pelling
Hi everyone, Using the Bus Pirate's JTAG macros, my S5PC100 returns a valid 3.3V JTAG chain with 250 devices (it's a highly integrated SoC, so 250 sounds like a plausible number), each with IDCODE = 0: while a Cortex-M3 microcontroller returns a single-device chain with the correct id value.

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-06 Thread Tomek CEDRO
On Mon, Dec 6, 2010 at 5:43 PM, Nick Pelling nickpell...@nanodome.com wrote: (...)constructing a suitable target cfg file for it. I've asked Samsung for documentation listing all its JTAG codes, but that may take some time to Hello Nick, the other problem is that Samsung may want you to sign

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-06 Thread Tomek CEDRO
On Mon, Dec 6, 2010 at 5:43 PM, Nick Pelling nickpell...@nanodome.com wrote: (...) constructing a suitable target cfg file for it. I've asked Samsung for documentation listing all its JTAG codes, Btw. have you tried UrJTAG and the discovery command - it helps finding such registers on unknown

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-04 Thread Nick Pelling
Hi everyone, Ah, I should have added that voltage was the very first thing I checked. On the S5PC100 the JTAG runs at VDD_EXT which has a valid operating range from below 1.8V to above 3.3V, and the board I'm trying to bring up has VDD_EXT set to 3.3V (as designed, measured to ~3.25V), so

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-03 Thread Austin, Alex
I imagine the problem is voltage, actually. The OMAP3530 and other similar devices run their JTAG ports at 1.8V, and the ARM-USB-OCD doesn't like working below 3V. From: openocd-development-boun...@lists.berlios.de

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-03 Thread Dirk Behme
On 04.12.2010 07:12, Austin, Alex wrote: I imagine the problem is voltage, actually. The OMAP3530 and other similar devices run their JTAG ports at 1.8V, and the ARM-USB-OCD doesn't like working below 3V. Therefore the Flyswatter

Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?

2010-12-03 Thread David Brownell
--- On Fri, 12/3/10, Austin, Alex alex.aus...@spectrumdsi.com wrote: I imagine the problem is voltage, actually. The OMAP3530 and other similar devices run their JTAG ports at 1.8V, True, and important. Thought I'm not sure quite what you mean by Similar. Don't the Sitara chips run at 3V3