Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
Xogium has quit [Remote host closed the connection]
Xogium has joined #openocd
JakeSays has joined #openocd
JakeSays_ has quit [Ping timeout: 268 seconds]
van has joined #openocd
Guest2 has joined #openocd
Guest2 has quit [Client Quit]
Hammdist57 has quit [Quit: Client closed]
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 [Remote host closed the connection]
rigid has joined #openocd
rigid has quit [Changing host]
rigid has joined #openocd
Hammdist24 has joined #openocd
<Haohmaru>
PaulFertser, for M$OS, openocd is installed via msys2?
Guest2 has joined #openocd
<Guest2>
Hello, first time here. Hoping to find some directions on how to configure openOCD for an old MCU (NXP LPC2138 - like 2148, but without USB support) on Olimex LPC-P2138 and Olimex ARM-USB-TINY (no -h). With some effort I have managed to get -very- basic support for debugging in gdb, but seems like I can’t reset the target properly and firmware
<Guest2>
upload isn’t working at all. Not familiar with netiquette here. Will check for any replies from time to time.
Guest2 has quit [Client Quit]
<Hammdist24>
no idea what the fix for your issues might be, but you'll probably have to give some more details to get meaningful answers. when you say you got very basic debugging support in gdb, what isn't working? what happens when you try to reset the target? what happens when you try to upload firmware?
<PaulFertser>
Haohmaru: that's one of the options, yes.
nashpa has joined #openocd
dliviu has quit [Ping timeout: 252 seconds]
Haohmaru has quit [Quit: saionara]
Guest2 has joined #openocd
<Guest2>
Not sure how much from the openOCD log file to paste here - is there a way to upload files or what is the standard?
<PaulFertser>
Guest2: hey
<PaulFertser>
Guest2: you need to stay on channel to see the answers
<PaulFertser>
Guest2: normally people use some pastebin, e.g. https://paste.debian.net or any other they like.
<PaulFertser>
Guest2: firmware upload to RAM?
<Guest2>
OK, so how do I do that if I need to leave for a while? My first message was on a phone, this is on my laptop.
<Guest2>
new things here... paste.debian.net - will check out.
<PaulFertser>
Guest2: in that case people use some IRC bouncers which they leave running (or have others provide them with cloud services).
<PaulFertser>
E.g. IRCCloud
<PaulFertser>
Guest2: LPC2138 should be even supported with flash writing.
<PaulFertser>
Yeah, we'd need to see what commands you run and what results you get.
<PaulFertser>
Guest2: I do not quite understand your paste. What is the command you're starting with and what is in the config file and why?
<PaulFertser>
I would expect you just sourcing the adapter config, then setting "reset_config trst_and_srst" (assuming you have both physically connected between the adapter and the target) and then lpc2148 config (since you say it's essentially the same chip).
<Guest2>
In gdb I can create one temporary hardware breakpoint, but not more.
<PaulFertser>
Where is this all from, why?
<Guest2>
I can single step lines, but not step over a function
<Guest2>
No good answer, sorry. I have worked with ChatGPT to get something that at least is close to working. I
<PaulFertser>
Let's start afresh then.
<Guest2>
It seems like I'm unable to reset the eval board LPC-P2138 although all signals _appear_ to be OK (can at least pull high and low).
<PaulFertser>
18:27 < PaulFertser> I would expect you just sourcing the adapter config, then setting "reset_config trst_and_srst" (assuming you have both physically connected between the adapter and the target) and then lpc2148 config (since you say it's essentially the same chip).
<PaulFertser>
Do you have reset and TRST lines physically connected between your debug adapter and the target?
<PaulFertser>
Also when I was working with those old chips "arm7_9 dcc_downloads enable" and "arm7_9 fast_memory_access enable" were performing nicely.
<Guest2>
PaulFertser: sounds great. I don't have the hardware here right now. I can try the lpc2148 config. Will take a while before I have all pieces together - how do i pick up the thread?
<PaulFertser>
Guest2: about when you'll be able to talk on IRC and do experiments on hardware in parallel?
<Guest2>
yes, all lines are physically connected.
<Guest2>
aha...
<PaulFertser>
trst_and_srst is the right reset_config setting tehn.
<PaulFertser>
Guest2: IRC is a simple chat, we just talk in real time, that's it :)
<Guest2>
OK, that does sound good, but won't be able to do so today. Great to hear that there are people knowledgeable here! :-)
<Guest2>
Need to leave now, but great to have fond this!
<PaulFertser>
Guest2: see you again. For the reference, I'm at UTC+3. Mention my nick so that I get a hilight.
<PaulFertser>
Guest2: it's interesting how you found that old JTAG adapter. Non-H versions were produced very long time ago.
Guest2 has quit [Ping timeout: 240 seconds]
Hammdist24 has quit [Ping timeout: 240 seconds]
nerozero has quit [Ping timeout: 272 seconds]
<zapb_>
PaulFertser, Gerrit is again very slow
<zapb_>
Which is interesting as there should be no Jenkins jobs, right?