crabbedhaloablut has quit [Ping timeout: 268 seconds]
nerozero has joined #openocd
dmh has quit [Quit: rip]
Haohmaru has joined #openocd
Hawk777 has quit [Quit: Leaving.]
<Xogium>
debugging cortex-a... Is exactly what I'm doing now hehe
<Xogium>
kernel hanging
clampz has quit [Ping timeout: 240 seconds]
clampz has joined #openocd
Xogium has quit [Quit: Leaving.]
Xogium has joined #openocd
jmp0 has quit [Remote host closed the connection]
jmp0 has joined #openocd
<Xogium>
what does this mean, generally ?
<Xogium>
Error: data abort at 0x00000000, dfsr = 0x00000005
<Xogium>
openocd printed that when I looked at backtrace with gdb
<van>
Xogium: what hw are you using?
<van>
I mean as the adapter
<Xogium>
st-link
<Xogium>
its not really jtag, but at least it does a relatively decent job
<van>
I see
<van>
I am planning to use a raspberry pi as a jtag adapter
<van>
for now
<van>
I had a quick look at olimex products but none of them state that they support cortex-a series
<van>
I don't know why though.
erhankur has quit [Remote host closed the connection]
erhankur has joined #openocd
<Haohmaru>
van you could probably ask them at #olimex
<van>
oh I see
<van>
thank you
<Xogium>
I wanted to buy olimex boards, but when I saw they don't even allow to buy from a different country from the destination I went like, meh
<Xogium>
shipping and billing address must be in the same country or your order will be refunded... Ok. What if you want to gift stuff to someone ?
<van>
interesting
<van>
I didn't know about this
<Xogium>
at least it was that way the last time I checked, could be because of covid for all I know
<Xogium>
I wrote to support asking for more details on this and they never replied
<van>
Nah, I have seen this practice in many other websites too..
<van>
I would bet it has something to do with how the payment is made.
<PaulFertser>
van: olimex usb adapters based on ft2232h are quite decent
<Xogium>
yeah, probably
<PaulFertser>
van: not sure what you really want to see them stating.
<Xogium>
so in the end I went with a dev kit from st, instead of the olimex board based on the stm32mp1
<van>
PaulFertser: I mean the webpage says that they support ARM microcontrollers.
<PaulFertser>
van: it doesn't matter
<van>
ah ok
<van>
yeah, this is what rubbed me the wrong way.
<PaulFertser>
van: if it's ft2232h plus buffering it should work with any jtag target
<van>
I see
<van>
ok, I will get it.
<PaulFertser>
van: for SWD you might want either additional adapter (Olimex sells one too iirc) or the "resistor hack".
<van>
oh
<PaulFertser>
van: you can also consider jlink edu if that applies to your usecase.
<van>
PaulFertser: I see
<van>
PaulFertser: I already asked Segger and they said that jlink edu isn't available anymore
<van>
All they have is Jlink Edu Mini
Bertl_zZ is now known as Bertl
<PaulFertser>
van: interesting, what's the difference?
<van>
PaulFertser: I think, with respect to segger, jlink edu mini only support cortex-m/r
<van>
*supports
<van>
I guess something to do with the firmware running on it.
<PaulFertser>
van: hm, probably this limitation is not present if raw JTAG communication is used, and OpenOCD does just that.
<van>
PaulFertser: Yeah, from what you said earlier, this is exactly what I thought.
<van>
I think these restrictions only apply if we use the mcu inside jlink
<van>
and openocd doesn't use it
<PaulFertser>
van: no, I didn't mean that. I think jlink communication always goes via an MCU but there're different commands it supports. OpenOCD uses the raw jtag communication commands.
<van>
oh I see
<PaulFertser>
van: ftdi-based adapters are different, they do not have any smart commands at all, only MPSSE to bitbang JTAG/SWD in an efficient way.
<van>
ah ok, now I get it.
RAMIII has joined #openocd
RAMIII has quit [Client Quit]
<borneoa_>
van: a53 and a72 should be aarch64 in openocd, not cortex_a
<borneoa_>
van: also pay attention that these devices usually close the JTAG port for security. Check if they provide info how to open it.
RAMIII has joined #openocd
wingsorc has quit [Quit: Leaving]
<van>
borneoa_: oh i see
<van>
I am actually debugging the rockpro64 from pine
<van>
The soc is rk3399
jeeebz has quit [Ping timeout: 240 seconds]
jybz has joined #openocd
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #openocd
<dormito>
out of curosity: is there any work on adding support for the NXP i.mx RT series ?
<bencoh>
considering the M4/M7/M33 core are already supported, it should "just" be a matter of writing the right tcl config script, I would say
erhankur has quit [Remote host closed the connection]
erhankur has joined #openocd
<dormito>
bencoh: thanks. I'll have to look at some of the multicore boards to see how multiple cpu's are configured for this chip, but that should be helpful figuring out if I'm on the right path.
<bencoh>
there is also a patch for one of the rt evk boards there
<bencoh>
you may want to have a look
erhankur has quit [Ping timeout: 276 seconds]
Bugies has quit [Remote host closed the connection]
piie has quit [Ping timeout: 240 seconds]
josuah is now known as cousin_mario
cousin_mario is now known as josuah
erhankur has joined #openocd
erhankur has quit [Remote host closed the connection]
erhankur has joined #openocd
<karlp>
it boils down to "swd newdap cpu hoho" aiui,
<karlp>
expected id is ignored for swd right now anyway,
<karlp>
oh, it also has a "target create loli cortex_m -chain-position loli"
erhankur has quit [Remote host closed the connection]
erhankur has joined #openocd
<Haohmaru>
o_O what's going on here
RoganDawes has joined #openocd
<RoganDawes>
Hi folks. I’m trying to figure out how to specify the nand flash bank for my Wink hub (imx28evk compatible board). I’ve been going around in circles trying to understand what is actually required. Any hints available?
<PaulFertser>
RoganDawes: does OpenOCD have a driver for the NAND controller in that SoC?
<RoganDawes>
I see there is an mxc driver, not sure if that is the right one
<PaulFertser>
RoganDawes: often times it's easier to upload u-boot to RAM and use it to access the flash
RoganDawes has quit [Client Quit]
<indy>
van, i was using rockpi 4 for rk3399, you need to upload tiny code which switch on pins for jtag
<indy>
van, or say uboot to write to some memory region
<indy>
van, jtag pins for cpu complex is on sdcard (at least for rockpi 4)
<indy>
i have somewhere 'pinmux' code to switch jtag on instead of sdio
<indy>
van, in u-boot "mw.l 0xff77e024 00f000a0"
RoganDawes has joined #openocd
RoganDawes has quit [Client Quit]
Guest52 has joined #openocd
Guest52 has quit [Client Quit]
<indy>
van, target/rk3399.cfg was merged 1y+ ago
noperator has quit [Quit: Client closed]
RoganDawes has joined #openocd
erhankur has quit [Remote host closed the connection]