NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
wingsorc has joined #openocd
Hawk777 has quit [Quit: Leaving.]
IoTMaker has joined #openocd
nerozero has joined #openocd
nerozero has quit [Ping timeout: 268 seconds]
nerozero has joined #openocd
IoTMaker has quit [Ping timeout: 260 seconds]
IoTMaker has joined #openocd
zjason` is now known as zjason
IoTMaker has quit [Quit: Client closed]
IoTMaker has joined #openocd
<IoTMaker> PaulFertser today i tried cpuidle.off=1 as env variable, doesn't change anything. But i read something about WAIT signal in TI's reference manual: Depending on the SYSBOOT pins, the GPMC is configured to use the WAIT signal connected on the WAIT0
<IoTMaker> pin or not. Wait pin polarity is set to stall accessing memory when the WAIT0 pin is low. The wait monitoring is intended to be used with memories which require long time for initialization after
<IoTMaker> reset or need to pause while reading data.
<IoTMaker> I guess that is the moment when openocd has problems
<PaulFertser> Doesn't sound related, and you do not have that hardware signal connected to jlink I guess?
<PaulFertser> IoTMaker: ^
<IoTMaker> Found it in chapter 26.1.8.2 https://www.ti.com/lit/ug/spruh73q/spruh73q.pdf
<Mis012[m]> IoTMaker: `cpuidle.off` is not u-boot env variable, it's a linux kernel cmdline parameter
thinkfat has joined #openocd
nerozero has quit [Ping timeout: 252 seconds]
thinkfat has quit [Quit: Konversation terminated!]
thinkfat has joined #openocd
thinkfat has quit [Quit: Konversation terminated!]
thinkfat has joined #openocd
IoTMaker has quit [Ping timeout: 260 seconds]
<phr3ak> forum is locked