8000 Use W25Q080 second stage loader for Nano RP2040 Connect by facchinm · Pull Request #537 · raspberrypi/pico-sdk · GitHub
[go: up one dir, main page]

Skip to content

Use W25Q080 second stage loader for Nano RP2040 Connect #537

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

Merged

Conversation

facchinm
Copy link
Contributor

Due to the well known electronic market situation, we were forced to mount an alternative part number in a batch of Arduino Nano RP2040 Connect.
These flash chips, from ISSI, need yet another way to configure the QE sticky bit 😞
At the moment, the safest way to handle the dual sourcing is to fallback using W25Q080 loader, and requiring that the sticky bit has already been programmed during production.

@pnndra @alranel @iabdalkader

Due to the well known electronic market situation, we were forced to mount an alternative part number in a batch of Arduino Nano RP2040 Connect.
These flash chips, from ISSI, need yet another way to configure the QE sticky bit :|
At the moment, the safest way to handle the dual sourcing is to fallback using W25Q080 loader, and requiring that the sticky bit has already been programmed during production.
@dhalbert
Copy link
Contributor

What is the part number you are substituting? We have seen Nano's with AT25SF128A and IS25LP128F. Thanks.

@pnndra
Copy link
pnndra commented Aug 10, 2021

AT25SF128A is the chip we'll be using for most of the production. for now we just had a small batch with IS25LP128F.

@kilograham kilograham added this to the 1.2.1 milestone Oct 4, 2021
@kilograham kilograham merged commit cd4e53a into raspberrypi:develop Oct 4, 2021
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

Successfully merging this pull request may close these issues.

4 participants
0