f_ changed the topic of ##raspberrypi-internals to: The inner workings of the Raspberry Pi (Low level VPU/HW) -- for general queries please visit #raspberrypi -- open firmware: https://librerpi.github.io/ -- VC4 VPU Programmers Manual: https://github.com/hermanhermitage/videocoreiv/wiki -- chat logs: https://libera.irclog.whitequark.org/~h~raspberrypi-internals -- bridged to matrix and discord
jcea has quit [Ping timeout: 276 seconds]
CarlFK1 has joined ##raspberrypi-internals
<CarlFK1> clever: pico io - consecutive pins or gpio?
<clever> the PIO is a dedicated co-processor, designed to hw accelerate bit-banging protocols
<CarlFK1> oh look, pi jtag is gpio 22-27
<clever> CarlFK1: yep, you can see that on https://elinux.org/RPi_BCM2835_GPIOs
<clever> but RTCK isnt needed
<clever> and TRST is optional
<clever> CarlFK1: i think that will work fine
<CarlFK1> yay
gordonDrogon has joined ##raspberrypi-internals
<clever> CarlFK1: and after bashing at the code for a day, ive figured out why netboot is unstable
<clever> my network init code, gets ran as a callback , within the tinyusb thread
<clever> and until it returns, usb cant process events well
<clever> and something else starts doing usb transfers in the middle of all of that
<clever> jn: and my pi3 is now booting the arm into the bootloader, entirely over the network
jcea has joined ##raspberrypi-internals
Herc has quit [Ping timeout: 246 seconds]
Herc has joined ##raspberrypi-internals
<CarlFK1> clever: \o/
inara has quit [Ping timeout: 248 seconds]
inara has joined ##raspberrypi-internals