INTL 3:770/1 3:770/3
REPLYADDR theom+news@chiark.greenend.org.uk
REPLYTO 3:770/3.0 UUCP
MSGID: <0al*8W4Rz@news.chiark.greenend.org.uk> 68aab0d1
REPLY: ccbdee4d
PID: SoupGate-Win32 v1.05
XPost: sci.electronics.design
In comp.sys.raspberry-pi john larkin wrote:
> Yes, but the port pin nunbering is different from the Pi 4 and 5, so I
> was concerned about which pins to connect to a Pico (or a 2040 chip)
> for program loading and debugging.
>
> This apparently works
>
> https://www.dropbox.com/scl/fi/sd8mkqz3rw55fcevjouvi/OKdo_Pi40
_debug_Pico.jpg?rlkey=kb5xjo75n5e5k3ncy4qs2caur&raw=1
>
> and one can actually count the pins on the connectors.
>
> One of my guys is hacking some connections and verifying. We're laying
> out some PCBs for debugging and production test, and we need to get
> the pins right.
Ah, that's SWD *output*. None of the Pis have specific hardware to act as
an SWD debugger, so it's just bitbanged GPIOs. For that it's just down to
whatever pins your software has decided to use. You can presumably
reconfigure it to use any GPIO pins.
(5 and Pico have dedicated SWD input connectors, but that's to allow *them*
to be debugged)
Theo
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757
SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364
SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100
SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
