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.

Sign up for GitHub

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

Jump to bottom

QSPIM1_CSN3 is not accessible #279

Open
1 task done
MikeOpenHWGroup opened this issue Dec 29, 2022 · 2 comments
Open
1 task done

QSPIM1_CSN3 is not accessible #279

MikeOpenHWGroup opened this issue Dec 29, 2022 · 2 comments
Labels
bug Something isn't working good first issue Good for newcomers wontfix This will not be worked on

Comments

@MikeOpenHWGroup
Copy link
Member

Is there an existing core-v-mcu bug for this?

  • I have searched the existing bug issues

Bug Description

The IO assignments in pad_control.sv do not include QSPIM1_CSN3, the fourth chip-select for QSPI master 1. Note that the IO assignments in do include QSPIM1_DATA3, so one would expect the chip select to be also included.

AFAIK, this will not affect the operation of QPSI master 1 other than to limit the number of QSPI slaves to 3. @gmartin102 can you confirm this?
@MikeOpenHWGroup MikeOpenHWGroup added bug Something isn't working good first issue Good for newcomers wontfix This will not be worked on labels Dec 29, 2022
@MikeOpenHWGroup
Copy link
Member Author

Joseph Julicher of AWS reports that the CORE-V-MCU Devkit will not use QSPI1_CSN3, so I have added the wontfix label. Recommend we fix this issue for future releases after RTL freeze of the next release.

@n9wxu
Copy link

n9wxu commented Jan 11, 2023

Correct, CSN3 is not used by the devkit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working good first issue Good for newcomers wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@n9wxu @MikeOpenHWGroup