<polprog>
hi, ive got a board with an arm cortex a8 (s5pv210) and id like to use opencd with it.. it autodetects one tap but im not sure what kind of tap is it
<polprog>
I'm looking at files for ti omap in a BeagleBone and it has three taps, one of them is the DAP used for debugging
<polprog>
what do i need to know to get access to the DAP?
<PaulFertser>
polprog: TI parts are known to lack DAP info ROM tables so you need to manually provide debug base etc, you should be able to find them in the datasheet/reference manual.
<PaulFertser>
polprog: probably you can find config files for some other jtag software and infer needed values from it.
<polprog>
allright, and then based on that I define the taps in my config file for this cpu?
<PaulFertser>
../( Dial-up modems were cool but AT command set is a real mess, especially with GSM modules
<polprog>
(its the only device in the chain)
<PaulFertser>
polprog: you likely have just one JTAG tap (according to results of autodetection) and then this TAP is used as a transport for ARM debug protocols, so you define a DAP on top of it, and then a target CPU on top of DAP.
<polprog>
got it, thanks!
<polprog>
ill ask questions when i find how some other debugger does it with this cpu
<PaulFertser>
polprog: you can probably just experiment based on data used for similar targets
<polprog>
thats my approach too but the only similar thing i see is samsung_s3*.cfg
<polprog>
ill take a look at these files
<polprog>
these are 920t or 7tdmi or 11 cores
<polprog>
s3c4510.cfg looks the most similar, its arm7tdmi
<PaulFertser>
polprog: just try minimal config. This part might have proper DAP ROM table so might be able to autodetect dbgbase.
<PaulFertser>
polprog: try defining dap on top of this tap and then cortex_a target.
<PaulFertser>
polprog: like imx51.cfg but without other taps
<polprog>
Info : s5pv210.cpu: hardware has 6 breakpoints, 2 watchpoints
<polprog>
is this from the config or from the DAP ROM?
<PaulFertser>
polprog: very good
<PaulFertser>
polprog: that's from examination of the debug unit that was connected to thanks to info from DAP tables.
<polprog>
i got the romtable under 'dap info'
<polprog>
fantastic
<polprog>
now to get arm gdb on debian ;)
<PaulFertser>
polprog: gdb-multiarch
<polprog>
youd think
<PaulFertser>
polprog: that's how it's called on Debian, yes
<polprog>
nevermind.. it installs as "gdb-multiarch", not "gdb"
<polprog>
great, i can see the memory and registers. Thank you very much :)
<PaulFertser>
polprog: glad to hear, I hope your research is going to be fruitful
bvernoux has quit [Quit: Leaving]
<polprog>
im getting some weird errors when trying to single step
<polprog>
Error: data abort at 0x00000000, dfsr = 0x00000017
<polprog>
goodnight
indy has quit [Server closed connection]
indy has joined #openocd
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #openocd
slobodan has quit [Read error: Connection reset by peer]