-
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
Can Not get (2) PSRAM chips to work together #33
Comments
I tried that using a 74hc4051. Whats wrong with just (2) gpio to (2) CS pins - instead of MUX ? So, I tried with just : That was the code above. |
How about : SN74LVC138APW ? |
Why MUX every SpiRam chip pin to the GPIOs ?
I dual connected each SpiRam Pin to the same W806 GPIO pins , I could then Intitialize PSRAM / SpiRam # 1 , using SpiRam as CS->PB1 , But when I changed GPIO PB1 to Input , |
Yeah, got that. PSRAM # 1 Initializes and runs SUCCESSFULLY - even though both PSRAM chips are stacked - as the diagram above. -- But I can not figure out how to switch to PSRAM # 2 successfully, I think it needs something to De-Initialize current PSRAM # 1 with CS=PB1 in the code. And vice-a-versa, to switch back to PSRAM # 1 again : It may be slower, but I can switch back and forth between PSRAMs. -- Btw: Where are these located in the Libraries / Include Files (I can not find them) : |
Ok Thx , I also ordered : I found the code.
|
jcoleman-oneaihealth |
It is useful. One of the projects is using the Ov7670 camera (from the Arduino Library) on the W806. |
Hey AnatolSher , thanks for the help with getting the 1st PSRAM chip to work !
--
But now I am using Multiple PSRAM chips.
I stacked (2) chips.
PSRAM Wiring :
1st Chip has CS connected to BP1 - with 100K resistor tied to V++.
2nd Chip has CS connected to BP6 - with 100K resistor tied to V++ also.
It works fine, if I ONLY Initialize PSRAM with CS PB1.
--
But if I disable PB1 cs as :
Then ReInit PSRAM :
PSRAM_ReInit_CS( GPIOB , GPIO_PIN_6 );
=>
*** It Just Reads FFs from either PSRAM ... !!!
-- Maybe I need to DeInit PSRAM before Init_PSRAM() again ???
The text was updated successfully, but these errors were encountered: