boru has quit [Killed (NickServ (GHOST command used by boru`))]
boru` is now known as boru
tsal_ has quit [Ping timeout: 244 seconds]
tsal has joined #openocd
nerozero has joined #openocd
Haohmaru has joined #openocd
Steffanx has joined #openocd
Steffann has quit [Ping timeout: 244 seconds]
lh has quit [Ping timeout: 252 seconds]
lh has joined #openocd
mithro has quit []
mithro has joined #openocd
tarekb has joined #openocd
rkta has quit [Ping timeout: 245 seconds]
rkta has joined #openocd
pisquo[m] has joined #openocd
<pisquo[m]>
Hi everyone, I'm have to debug a CC2544 for a university project using TI's CC-debugger. On the official manual of cc-debugger the official tools listed are IAR Workbench and SmartRF, does anyone know if there's a way to use it with openocd?
<pisquo[m]>
P.s. I tried searching but my google-fu failed me and sorry if it's a dumb question but I'm a beginner in this field.
<olerem>
pisquo[m]: the official TI debugger will probably not work with openocd. You'll need to use some thing different. For example something ftdi based
<pisquo[m]>
olerem: Ok, I'll look into it. Thank you very much!
<NishanthMenon_>
olerem, xds110 works :D there is xds560 that does'nt probably work.
<olerem>
NishanthMenon_: ach, cool!
<olerem>
pisquo[m]: ^
<NishanthMenon_>
btw, I'd like folks' opinion on this little connundrum I ahve: I am trying to get a jtag debugger that works with openOCD.. I'd like to get a level of performance i get from lauterbach (at least some level).. I have been looking at segger j-link.. but curious if there are better options
<NishanthMenon_>
the SoCs i deal with from TI are some complex high bandwidth chips cortex-A based mostly..
<olerem>
NishanthMenon_: hard to say, for example on imx6 i was able to get max speed supported by board which i worked with. It was 15-30MHz JTAG clock speed.
<olerem>
The same clock rate was used on lauterbach for the same board
<olerem>
i used Bus Blaster v3
<NishanthMenon_>
olerem, were you able to get upto 30 on bus blaster?
<karlp>
NishanthMenon_: there's a few ti debuggers that work, but there's no support for the 8051 targets that I'm aware of.
<NishanthMenon_>
karlp, yeah - i am getting no where close to 30MHz with TI xds110... (i get maybe 2MHz or so).
<olerem>
30MHz is max supported by the ftdi, yes. but the board designe was not able to handle it
<karlp>
I was talking about pisquo's queery, not mega trace :)
<NishanthMenon_>
karlp, aah :D
<karlp>
orbtrace willd be an option for mega trace, but it's still pretty early days.
<NishanthMenon_>
olerem, how fast did you get it to go? just curious..
<olerem>
NishanthMenon_: 15MHz. ftdi has simple devider, there is no way to get anything in between 15 and 30MHz :)
<NishanthMenon_>
olerem, anyday better than what I got :(
<NishanthMenon_>
olerem, thanks..
<olerem>
NishanthMenon_: what do you get?
<NishanthMenon_>
paltry 2MHz :(
<olerem>
not a lot :)
<NishanthMenon_>
i mean, i was using xds110. i will buy a bus blaster and compare the data rates with lauterbach and see.. that should give me a better view.
<NishanthMenon_>
olerem, karlp thanks for the hints..
<pisquo[m]>
<karlp> "NishanthMenon_: there's a few ti..." <- Ok, thank you very much for the help
<karlp>
pisquo[m]: but it _won't_ help you with that cc2544, which is an 8051
<karlp>
you want one of the newer cortex-m radio socs.
emeb has joined #openocd
<NishanthMenon_>
pisquo[m], openoCD needs to support the debugger interface AND the processor (how to set a breakpoint etc).. he is indicating that even if the board has a compatible debugger, the processor is not supported.
<PaulFertser>
NishanthMenon_: btw, other ft?232H-based adapters should be as fast.
<NishanthMenon_>
else i am going to the $1000+ $ range.. which I dont want to do..
<PaulFertser>
NishanthMenon_: I mean there're plenty of ftdi adapters, the cheapest being TUMPA.
<NishanthMenon_>
yup. thanks PaulFertser
<PaulFertser>
NishanthMenon_: and in some cases (3.3 V target Vcc and certain features of hardware line matching) even a plain ft232h breakout board would work.
<NishanthMenon_>
yup. trying to put out a "standard" for my team so that everyone has one.. i think i like BBv3 over all other options i have seen so far..
<karlp>
things like Tumpav2 are meant to be perfectly reasonable too, and not as fragile
<karlp>
that looks like a v2 with the 6pin swd header on the corner
<NishanthMenon_>
uggh.. everything is 14 week lead time.. Sigh the supply chain issues are irritating..
<NishanthMenon_>
karlp, thanks.. i will send both of these to my team.. though i personally like the form factor of bbv3 - easier to packit in a little 3d printed box and swap tagconnect etc in the middle of all the other mess on the desk..
<PaulFertser>
karlp: yes, v2 is with SWD resistor hack integrated, unfortunately, only 3.3 V.
<PaulFertser>
NishanthMenon_: I think TUMPA should be sturdier as it uses a special drive IC rather than a CPLD.
<NishanthMenon_>
aaah.. thanks..
<PaulFertser>
But it has some annoying features too, iirc SRST line isn't open-drain there.
The_Jag has joined #openocd
<PaulFertser>
NishanthMenon_: if you need proper SWD then TUMPA is not suitable.
<PaulFertser>
NishanthMenon_: have you considered trying fake jlink for evaluation purposes?
<NishanthMenon_>
like mini-Edu?
<PaulFertser>
There're 10$ clones from China I mean.
<PaulFertser>
Or the full official EDU version for like 60-70 but you are not allowed to use it in commercial setting.
<NishanthMenon_>
not really.. i mean, i am not that bad on budget.. i can afford jlink edu as well.. but i am a bit umm-umm on jlink
<PaulFertser>
Why?
<PaulFertser>
EDU is not suitable for commercial purposes
<PaulFertser>
I mean probably ebay has fake jlink in stock and you can evaluate it fast.
<NishanthMenon_>
the main reason i am looking is @ 2MHz, folks are complaining on debug speed.. and i want that off the table..
<karlp>
what are they doing that debug speed is the problem?
<karlp>
I mean, is there something else underlying?
<PaulFertser>
karlp: I wasn't able to reproduce Werror in jimtcl, can you please recheck some day?
<NishanthMenon_>
karlp, data refresh rates of memory, etc.. many guys like lauterbach as front end ide view and register views of various peripherals and data structures etc..
<karlp>
PaulFertser: only on fc33 at work, will have to try at home
<karlp>
NishanthMenon_: ah right, people who are expecting all that shit to be updated, allllll the time flickering across their screens.
<NishanthMenon_>
karlp, yup
<karlp>
I've not normally been constrained by "slow" debug, because i'm only having it present what I want, with ITM channels
The_Jag has quit [Quit: The_Jag]
<karlp>
I'm not trying to have a tab in my editor open that continuously updates with live register contants and a chunk of memory :)
<karlp>
I'm guessing this is rtt related as well
<karlp>
gotta sell those faster dongles I guess :)
<NishanthMenon_>
karlp, https://lore.kernel.org/all/20210903050550.29050-1-nm@ti.com/ was interesting one for example i debugged yesterday night.. i was'nt sure of quite a few conditions.. so i did have variable views, uart reg peripheral view + a few other watchpoints all going in parallel
<karlp>
oh, don'
<karlp>
t get me wrong, I get it happens
<karlp>
it just also happens for people who seem to have underlying issues,
<NishanthMenon_>
hehe... ofcourse..
Haohmaru has quit []
tsal has quit [Quit: ZNC 1.6.5+deb1+deb9u2 - http://znc.in]
tsal has joined #openocd
nerozero has quit [Ping timeout: 252 seconds]
tarekb has quit [Read error: Connection reset by peer]
crabbedhaloablut has quit [Ping timeout: 276 seconds]
crabbedhaloablut has joined #openocd
sbach has quit [Read error: Connection reset by peer]
sbach has joined #openocd
Steffanx has quit [Quit: Whop whop]
Steffanx has joined #openocd
zjason` has joined #openocd
zjason has quit [Ping timeout: 252 seconds]
c4017w has joined #openocd
<pi0>
olerem: is there a cheap way to transmit 1-1000mhz that does not require hackrf