Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allocate GPIOs for SPI/SDcard interface? #44

Open
penfold42 opened this issue Sep 7, 2024 · 10 comments
Open

Allocate GPIOs for SPI/SDcard interface? #44

penfold42 opened this issue Sep 7, 2024 · 10 comments

Comments

@penfold42
Copy link
Contributor

SPI1 on GPIO10,11,12,13 ?
and maybe GPIO 14 and 15 for additional SPI slave selects (or multiplexing via a HC139 ?)

@dawsonjon
Copy link
Owner

I have been working on a ili9341 TFT waterfall, I've provisionally allocated allocated these pins.

#define PIN_MISO 12
#define PIN_CS   13
#define PIN_SCK  14
#define PIN_MOSI 15 
#define PIN_DC   11
#define PIN_RST  10

Obviously, I'm not actually using the MISO pin, but thought it made sense to allocate it so that the SPI could be used with other peripherals such as SD card or similar. I will ditch the RST pin if I can, and might try to double up the DC pin with something else too if I can. I would like to keep GPIO28 spare for a microphone input, and 3 other pins for TX functions. Perhaps we should allocate GPIO9 as SD card CS pin?

@MrSVCD
Copy link

MrSVCD commented Sep 9, 2024

Since you are asking, what are your plans for the SD card?

@penfold42
Copy link
Contributor Author

@mryndzionek suggested sd card recording in the #15 features discussion issue

@dawsonjon re: PIN_CS on gpio 13 vs 9. Not sure there's much benefit one way or the other.
Are we rapidly running out of pins? :) I guess theres 3 options:

  • a pico2 board with the bigger package
  • layout a board with the bigger package on it
  • use a I2C gpio expander for the slower speed stuff (buttons, but not encoder)

@MrSVCD
Copy link

MrSVCD commented Sep 13, 2024

If you go the I2C expander route, you could "just" use another Pico. It is a bit more expensive than a MCP23017 but gives more options.

@penfold42
Copy link
Contributor Author

If you go the I2C expander route, you could "just" use another Pico. It is a bit more expensive than a MCP23017 but gives more options.

Quad core radio :)

Beware the I2C MCP23017 - silicon bugs require A7 and B7 be set to outputs

@mryndzionek
Copy link
Contributor

What about the bandpass filter control pins (2, 3, 4)? The breadboard version doesn't use those pins.

@penfold42
Copy link
Contributor Author

Ideally the one firmware would work on both with no runtime config.

For best image rejection (and noise) you should really use the band select filters.

@MrSVCD
Copy link

MrSVCD commented Sep 15, 2024

As I was looking for other ways to add buttons. Can ADC2 be used to add a keypad?
There is a way to add a keypad using a bunch of resistors.
Here is some maths and designs Keypad.zip
The only change to the circuit when the keyboard is not installed would be a 10k resistor from ADC2 to ground. The RP2350 has a currently a bug for the internal pull-down resistor and I don't know the value so a external one would be a safer bet.

@dawsonjon
Copy link
Owner

I'm quite keen to keep the spare ADC input as a mic input when I add TX capability. It will probably double as a morse paddle input too.

Another option to consider is to add an IR remote. Only needs one IO pin... IR remotes are also very cheap, often cheaper than a keypad.

@MrSVCD
Copy link

MrSVCD commented Sep 19, 2024

Not a really serious suggestion but something to be inspired by:
Since I am computer collector I have some Apple Desktop Bus stuff and it uses only one I/O pin. There is another signal in the standard that is only used for a remote power button.
https://en.wikipedia.org/wiki/Apple_Desktop_Bus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants