rigid has quit [Read error: Connection reset by peer]
jn has quit [Ping timeout: 252 seconds]
jn has joined #openocd
jn has joined #openocd
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
rigid has quit [Read error: Connection reset by peer]
rigid has joined #openocd
rigid has joined #openocd
rigid has quit [Changing host]
rigid has quit [Ping timeout: 260 seconds]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
rigid has quit [Remote host closed the connection]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
rigid has quit [Ping timeout: 252 seconds]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
rigid has quit [Client Quit]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
Hawk777 has joined #openocd
zjason` has joined #openocd
zjason has quit [Ping timeout: 276 seconds]
nerozero has joined #openocd
rigid has quit [Read error: Connection reset by peer]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
rigid has quit [Ping timeout: 246 seconds]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
rigid has quit [Read error: Connection reset by peer]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
Haohmaru has joined #openocd
Xogium has quit [Ping timeout: 260 seconds]
Xogium has joined #openocd
rigid has quit [Ping timeout: 246 seconds]
Hawk777 has quit [Quit: Leaving.]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
<indy>
hi all, anybody experience with threadx and openocd?
<Haohmaru>
openocd - most of the people here, supposedly
rigid has quit [Read error: Connection reset by peer]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
<gamiee>
indy: yes, I use OpenOCD with threadx. Whats up?
<indy>
gamiee, have you used it for porting?
<gamiee>
indy: porting of what?
<indy>
gamiee, to new mcu/soc
<gamiee>
indy: there is no need of porting. It should work out just fine, you just need to configure it in TCL script supplied to OpenOCD.
rigid has quit [Read error: Connection reset by peer]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
<indy>
gamiee, misunderstanding :) porting threadx to new hw, not openocd. i have openocd already configured, communicating with jtag
<indy>
so question reformulation - have you used openocd to port threadx to new board/mcu,etc? :)
<gamiee>
indy: oh, in that case, no idea. I used ThreadX only in already ported MCU, I never get into insides of it at all.
joconor has quit [Ping timeout: 260 seconds]
joconor has joined #openocd
zjason` is now known as zjason
<indy>
gamiee, which board/mcu?
<gamiee>
indy: STM32U5
<PaulFertser>
indy: sorry for offtopic but what would be the main advantage of ThreadX over FreeRTOS for you? And what exactly makes porting challenging? Are you already running it but want to have OpenOCD with working thread awareness?
<indy>
PaulFertser, threadx has certifications for safety critical areas like automotive
<PaulFertser>
SafeRTOS too
<PaulFertser>
And if you self-port ThreadX you'd need to somehow re-certify it anyway?
<indy>
threadx is ported to many architectures (understand smp multicore cortexes a35/a53/....) so i assume it doesn't need re-certification
<indy>
problem is hw initialization
<indy>
i was looking at getting-started repo, and compared similar mcus
<indy>
but still it is for mcus
<indy>
as rk3399 and lot of other sbcs have pcie controllers capable of endpoint mode, i would like to play with pcie.
<PaulFertser>
Are you connected to RK3399 with SWD and debugging basic init of bare metal ThreadX? Like bringing up a timer or are you past that and working on multi core?
<indy>
i have only few assembly instructions to enable swd
<indy>
i would prefer to be able using jimtlc to access usb to load that code instead of loading it using rk tools
<gamiee>
PaulFertser: not sure if you know, but ThreadX is now fully open
<PaulFertser>
gamiee: I wasn't aware, yes.
<gamiee>
The documentation for ThreadX kinda sucks, but else, it's quite nice RTOS, so far, I didn't had any major issues with it.
<indy>
now it is eclipse threadx
<gamiee>
And I am happy it's not named Azure RTOS anymore :D
<indy>
:-D
<karlp>
oh, the dump has finally happened, not just the announcement?