NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
nerozero has joined #openocd
indy has quit [Ping timeout: 276 seconds]
<borneoa__> Notice: OpenOCD master branch build is broken with MacOS clang. I'm working for a fix. Wrong commit is mine https://review.openocd.org/7519
<PaulFertser> borneoa__: do you know why Jenkins didn't catch it? Clang too old?
<borneoa__> PaulFertser: apple anticipates patches from future clang. Also in Arch Linux with latest clang I don't get the error.
<PaulFertser> borneoa__: oh, ok, so not much we can do about it, probably not to worry then?
<PaulFertser> Also, the discussion on the mailing list about issues with multi-interface devices (such as ft2232h) on macOS is kinda disappointing, nobody gives advice there.
<borneoa__> I only have remote access to a Mac for compile test. No physical access for the ftdi issue, unfortunately
<PaulFertser> Probably the macOS users should take care of themselves more.
<borneoa__> Maybe we could add Mac cross compiling on Jenkins, but has to be constantly updated
<PaulFertser> Not worth it imho.
<borneoa__> Anyway, I get alert from ACI in ST when master branch fails the build. Probably good enough for the time being
<PaulFertser> BTW, I am still surprised by the feedback I'm getting on the patch by some new ST guy there.
<PaulFertser> (getting not)
<borneoa__> Haven't check it, yet...
Guest95 has joined #openocd
<Guest95> Hi every one.
<Guest95> I got a problem i cant find any good answer on google for.
<Guest95> I have a raspberry pi zero 2w that is connected to esp32 over the gpio pins.
<Guest95> using openocd and it works.
<Guest95> Here comes the tricky part:
<Guest95> im trying to send openocd in/output to a virtual ttyUSB* but no success.
<Guest95> im using the esp32 on the serial interface for communications and jtag for otherstuff, but need jtag to act like i connected it throu USB, ttyUSB**
<Guest95> Any sugestion how to achive this?
<PaulFertser> Guest95: hello
<PaulFertser> Guest95: JTAG doesn't work over tty devices, so your question is just odd.
<PaulFertser> Please rephrase.
<Guest95> I am trying to make a connection to the esp32-wrove throu the raspberry pi.
<Guest95> I have gotten response from the jtag connection with the openocd over gpio.
<Guest95> the thought is to run something called baktooth, its for fuzzing bluetooth units when you check for errors.
<Guest95> the program comuncate throu the usuall usb. BUT the jtag is to see whats happens and recive updatets and interuptions and things.
<Guest95> Because i dont have the "dev board with esp32wrove", that has this built in due to the hardware.
<Guest95> im trying to solve it with a pi zero -> usb -> esp32 AND pi zero gpio ->jtag -> esp32.
<Guest95> The USB will act as a serial communication
<Guest95> the JTAG will act as a JTAG.
<Guest95> But i need to send the communication from openocd to ttyUSB1 to make the program to work propperly.
<Guest95> What i have seen is that the devboard makes 2 connections over USB. One for USB - serial AND one for USB - jtag.
<Guest95> Thats what im trying to achive with the openocd jtag -> ttyUSB1 in raspian.
<Guest95> Sorry for my explenation, i never done this and dont know if this is the right way to achive this. But i only have my Pi zero and esp32 wrover.
<PaulFertser> Guest95: please show the documentation to a known working way of what you're trying to do.
<Guest95> There isnt any documentation on it, more then that you can access the jtag and the serial part of the wrover over pins.
<PaulFertser> Guest95: why is jtag needed at all?
<PaulFertser> Guest95: and I still can't understand how USB and tty devices come into play.
<PaulFertser> Guest95: you're confused and confusing me ;)
<Guest95> is it possible to rederect the input/output from openocd to a ttyUSB? so another program can read it or interact with it. That is the most basic question i need to check :)
<Guest95> any suggestion?
<Guest95> or should it be a pipe that this needs to be sent over?
<Guest95> yesss
<PaulFertser> Guest95: it says flash firmware by whatever way.
<PaulFertser> Guest95: then talk to esp32's UART.
<PaulFertser> Guest95: after you flashed the firmware you do not need JTAG and OpenOCD anymore.
<Guest95> hmmmm, then i miss read the whole thing (my english is,,,, wobbly?)
<Guest95> Thanks, i will se if i can make this work then:)
<PaulFertser> Probably the host python code assumes you have access to both the first and second UARTs of the target MCU.
<PaulFertser> Guest95: well, not so much misreading but missing the context probably, if you do not have much experience with MCU firmware development.
<PaulFertser> Guest95: look, the right way to approach the topic would be to take a look at ESP32-WROVER-KIT documentation to understand what exactly are those USB serial ports connected to.
<PaulFertser> Guest95: and why is the doc implies that flashing the kit is possible without JTAG adapter and by using some serial communication instead. Probably the board comes with a serial bootloader pre-configured or some such.
<Guest95> i will check it out:)  Thx for your time:)
<PaulFertser> Guest95: have fun :)
<PaulFertser> Guest95: also reading the source code of all those python scripts in question would clarify things.
<PaulFertser> As it's not clear what it uses the first serial port for if https://docs.espressif.com/projects/esp-idf/en/latest/esp32/_images/esp-wrover-kit-block-diagram.png shows interface A of the integrated ftdi chip is only connected to target's JTAG.
<Guest95> hci over uart and the other one is made for some custom protocoll if i understand right what purpouse is if you check the pic in :
Guest95 has quit [Quit: Client closed]
Hawk777 has joined #openocd
nerozero has quit [Ping timeout: 246 seconds]
Hawk777 has quit [Quit: Leaving.]
torbenh3 has joined #openocd
tsal has quit [Ping timeout: 248 seconds]
tsal has joined #openocd