<Haohmaru>
the old board seemed to have possibly spare pins on the two sides as castelated vias, the new one doesn't appear to have them
merethan has quit [Remote host closed the connection]
merethan has joined #openocd
<PaulFertser>
memes: damex: using ft232h breakout board is usually good enough if the target voltage is 3.3 V. Also with some targets series termination resistors are needed on all data lines, proper jtag/swd adapters have them integrated.
merethan has quit [Remote host closed the connection]
merethan has joined #openocd
Guest52 has joined #openocd
<Guest52>
Hello everybody. Is it possible with openocd to access aarch64 system registers like ttbr0_el1 (registers that you would typically read/write with mrs/msr instructions). When using the stock gnu toolchain provided by ARM + OpenOCD it seems like some are available (like ESR_EL1/2). Could someone explain me (or point me to some document) how this is
<Guest52>
done? Generally, I am wondering if this is some sort of limitation by the chip manifacturers or if this is specified by ARM etc... Thanks in advance!
<Guest52>
So basically I am wondering "who decides which registers can be `trivially accessed` and which not"
<PaulFertser>
Guest52: registers are hardcoded in OpenOCD sources.
<PaulFertser>
See src/target/armv8.c
<Guest52>
So would it be possible to get access to all registers?
<PaulFertser>
armv8_regs[]
<PaulFertser>
Guest52: not sure if easily possible without modifications of source code.
<Guest52>
ok looking at the code this is exactly what I am curious about. Apart from the x-registers we have access to esr/elr/spsr registers. What about all the other registers? Is there a technical reason why they are not there? Or does the debug infrastructur in general provide all internal registers to the outside? Or maybe I should ask how does openocd
<Guest52>
actually access those registers?
<PaulFertser>
Guest52: please stay here on the channel, probably someone who knows more about aarch64 will answer.
<Guest52>
Ok, thanks!
akaWolf has quit [Ping timeout: 258 seconds]
akaWolf has joined #openocd
<karlp>
memes: you're not getting etm over jtag, it's a separate interface. you can _configure_ etm via jtag, but you will need somethign else to capture it.
<PaulFertser>
I think memes meant ETM would go to ETB (trace buffer) and then its contents can be fetched via JTAG.
Guest52 has quit [Quit: Client closed]
Guest45 has joined #openocd
erhankur has quit [Remote host closed the connection]
erhankur has joined #openocd
erhankur has quit [Remote host closed the connection]
<Guest45>
Hello
<Guest45>
i'm trying to use openocd to erase an external flash connected to a stm34l496
<Guest45>
as far as I understand in need to use the stmqspi driver
<Guest45>
if I try this command
<Guest45>
$> flash bank spi stmqspi
<Guest45>
The 'flash bank' command must be used before 'init'.
<Guest45>
I know some parameters are missing but generally openocd tell me which one