Re: [Openocd-development] [PATCH] CORTEX A8: Fix broken CPU identification
Hi Daniel, At 16:43 11/02/2011 +0100, Daniel Bäder wrote: S3CPC100 from Samsung is also detected as imx51 with this patch. Without this patch it works. May I ask which S5PC100 platform are you working with? Thanks, Nick Pelling ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?
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 quiet about the device, as they did when I asked for some documentation for one device that I wanted to use in open source project - they did not agree If you run into this please let me know what particular device it is. I now have the BSDL file for the S5PC100 (through Samsung support channels) which is great, but my next step is to try to find out whether or not it is covered by the NDA I've already signed - many manufacturers post their BSDLs openly (for instance, Luminary Micro), but this one wasn't on Samsung Semi's support site. There's nothing particularly surprising in there, apart from some JTAG boundary constraints which I suspect really ought to have been included in the User Manual. Cheers, Nick Pelling ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?
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. Hence I'm pretty convinced that this S5PC100 board is connected and functioning properly, but am struggling for ideas as to how best to start 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 arrive. Any other suggestions? Thanks, Nick Pelling ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?
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 this really shouldn't be the issue here. Cheers, Nick Pelling ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] OpenOCD Cortex-A8 / S5PC100 support...?
Hi everyone, I've just plugged my trusty old Olimex ARM-USB-OCD (the Swiss Army Knife of JTAG debuggers) into my shiny new S5PC100-based board and... I'm struggling to see how to get it working even slightly. Has anyone got anywhere with the s5pc100 or other CoreSight-based Cortex A8s (apart from the OMAP3530 as per http://elinux.org/BeagleBoardOpenOCD )? Firas Achkar mentioned trying this on the urbetter board (which I think is actually the original ODroid) a month ago, as did Matt Hsu in November 2009. But trying the latest openocd's autoprobe (as David Brownell suggested then) didn't seem to produce anything so revealing as an ID code. Incidentally, I've read through the CoreSight chapter in the latest Samsung datasheet but that had precisely nothing so useful as a TAP ID code or a DAP ID code to get started. Stepping through every occurrence of JTAG also revealed nothing useful. Any suggestions? Has anyone tried the same thing for the S5PC110 (as per the ODroid-T etc)? Might there be some hidden nest of Samsung SoC OpenOCD developers in a far-flung corner of Korea? Cheers, Nick Pelling ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
