-
Notifications
You must be signed in to change notification settings - Fork 12
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
How to implement your work again with a pico board? #15
Comments
Hi
CS pins are not hardware specific; Any pin can be used as a CS pin as long as they are GPIO pins
Using those pins won't cause any problems tho you need to recompile the code for that
IIRC, there are no 16MB ram chips available in the market. And linux needs atleast 8MB of RAM.
Flash is different from RAM.
The size of the Linux Image he provides is around 2.5MB. |
OK, thanks a lot. You must be an embedded expert and now I know much more better! So glad to meet your repo and you! So now I encounter some new problem:
|
Hi
Absolutely not. I'm just a random kid interested in this project
Hmm actually this is @tvlad1234 's repo and his project
Which is why the project uses 2 8MB PSRAM chips
That's a 1v8 RAM, which needs voltage shifters to work as the pico is 3v3
I'm sorry, but I don't know anything about openssl |
I am so excited to read you repo and think this is a very nice project. However I still have some confusions with getting it work:
about pinout
In the
README.md
I see that you've mentioned that the pin layout of SD card and RAM chip. But it does not match the official pinout presented by raspberry pi:For example:
maybe these design just turn all GPIO as common usage? Shouldn't we use the official recommend pinout? Will these cause some other unexpected problem? Please enlight me, thanks.
about RAM chip
In the
README.md
:about linux system
buildroot
arguments can create different size of linux image. I also want to make linux image storage in an on-board storage chip to reduce total size :)Thanks a lot!
The text was updated successfully, but these errors were encountered: