Hello David, Am 2010-03-04 14:21:16, schrieb David Brownell: > Surely that's because OpenOCD doesn't claim to support those > chips in the first place...
Right, and I was trying to get no mather what from the chip as a starting point... > from GCC or GDB, either. Though it does at least seem to use JTAG for > the transport to its on-chip debug (OCD) module... The preliminary "MAXQ69 User Guide" is speaking about ISP and debuging > The most I'd expect you to be able to do with OpenOCD is use the > autprobe mechanism to discover that one exists on the scan chain, > and report a few basic TAP attributes. And as Michael noted, > maybe SVF and/or XSVF support would work. Hmmm... > I'd not think it would happen soon either. Maybe GCC 4.5.x > versions could start to use the named address space feature > from ISO/IEC TR 18037 to help sort out the mess with SFRs (they > need their own address space.) 8051 is not compiler-friendly. > I've never seen a compiler that generated 8051 code without > requiring extensions to C ... (I looked at C for 8051 a few years > back. At that time SDCC was the main non-payware option, and > it wasn't IMO very good.) I use "sdcc" since 2 years without problem, but have to use a Windows tool to upoad my code. But sometimes it does not start in "wine". > Likewise, no OpenOCD for that particular chip. A quick scan of > the manual for that chip doesn't find any reference to JTAG. > Evidently it uses yet another proprietary transport for OCD. I have read there is someone which used OpenOCD to access the C8051F5xx but I do not find any hints... > Switch to chips with good GCC/GDB/OpenOCD tools support, or > help develop that support for your chosen chips. Do yu know a chip which is 1) physical small 2) possibel TSOP, QFP or equivalent 3) consumes ony som mA of energy 4) mostly automotive 5) 1x I²C 6) 1x SPI and chip one has either a) 1x USB device b) 1x CAN Sorry, but any ARM7TDMI suck to much I use already the SAM7S, SAM7SE and SAM7XC plus a bunch of others. > Also: Read the Fine Manual; we've been working to make sure > the OpenOCD User's Guide covers all the important stuff, like > which cores are supported. > > Current manuals can be read (HTML or PDF) at > > http://openocd.sourceforge.net/ I am looking for a documentation on how to get support into OpenOCD if a (yet) non-supportet microchip is needed... What are the steps? Thanks, Greetings and nice Day/Evening Michelle Konzack Systemadministrator 24V Electronic Engineer Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ ##################### Debian GNU/Linux Consultant ##################### <http://www.tamay-dogan.net/> Michelle Konzack <http://www.can4linux.org/> Apt. 917 <http://www.flexray4linux.org/> 50, rue de Soultz Jabber [email protected] 67100 Strabourg/France IRC #Debian (irc.icq.com) Tel. DE: +49 177 9351947 ICQ #328449886 Tel. FR: +33 6 61925193
signature.pgp
Description: Digital signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
