INTL 3:770/1 3:770/3
REPLYADDR theom+news@chiark.greenend.org.uk
REPLYTO 3:770/3.0 UUCP
MSGID: eaad6878
REPLY: <6jg6ejlh6f0iqo84v2dlo4487fpccprjmh@4ax.com> cbf42cf6
PID: SoupGate-Win32 v1.05
XPost: sci.electronics.design
In comp.sys.raspberry-pi john larkin wrote:
> RP2040 has I think 2 PIO blocks and each has a couple of hardware
> programmable state machines, and those can be set up to drive pins.
> I'm mostly concerned now with a PCB schematic design, picking the
> appropriate and easy-to-route pins from the CPU to things.
>
> My general question, for various processors, is how to associate bits
> in integer variables with physical pins on the chip.
This is the function of a 'pinmux'. Different chips have different
capabilities of the pinmux, but it's rare to be able to connect any GPIO to
any pin - that's more FPGA territory. Typically the pinmux is just about
selecting one of multiple fixed functions for a given pin
(SPI1_MISO/I2C3_SDA/UART2_TX/...)
So either you route your DAC to consecutive pins (D0 to GPIOn, D1 to n+1,
..., ideally where n is a multiple of 8), or you're prepared to do the
necessary bit shuffling in software (which can be slow and non-atomic). I'd
suggest sticking to consecutive ordering if you can.
(although I have no experience of the RP2xxx GPIO/PIO shenanigans)
Theo
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 19/38 90/1 105/81 106/201 129/305 153/757 7715 218/700 840
SEEN-BY: 220/70 226/17 30 100 227/114 229/110 111 114 200 206 300
SEEN-BY: 229/317 400 426 428 470 550 616 664 700 266/512 267/800 282/1038
SEEN-BY: 291/111 292/854 310/31 320/219 322/757 342/200 396/45 460/58
SEEN-BY: 633/280 281 412 418 420 509 2744 712/848 770/1 3 100 330
SEEN-BY: 770/340 772/210 220 230 5020/400 5075/35
PATH: 770/3 1 633/280 229/426
|
