-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Make the addition of support for new flash chips easier (ESPTOOL-719) #903
Comments
Hi @ESP32DE, Your example shows the current behavior of esptool. Do you think more information should be displayed? Please describe your feature request a little more. Thank you! |
Hi @radimkarnis, asking for support for new (octal) flash chips. I can't see/found the octal flash list/DETECTED_FLASH_SIZE entry for the used MX25UM25645G in ESP32-S3-WROOM-2 / ESP32-S3-N32R8v-DevKitC-1 in esptool. Is this 32MB octal and the 16MB octal the only one which is supported by espressif? esptool info example from ESP32-S3-WROOM-2 which is based on ESP32-S3R8v :
txs edit: same manufacturer "Macronix" IC FLASH but in 512MBIT SPI/OC 24CSPBGA Infineon 512 MBIT GigaDevice 1Gbit ..and many more MP exist now. ESP32-S3 supports up to 1 GB off-package flash and 1 GB off-package RAM. |
I'm afraid that adding support for new flash chips is not very easy and straightforward at this moment. Yes, it is possible to add a new size to lists like you mention. It might work if one of the drivers can be used automatically. However, especially for larger chips new drivers are needed and the general ones could not be used (different ROM calls & SPI commands are needed supporting larger address space, or sometimes just different SPI command is needed because the manufacturer is different). I renamed the title to better sum up what is needed here. We are planning some big changes regarding the flasher stub. So I'm afraid this won't be addressed soon. |
hi @dobairoland , exactly this. thank you. i noted the drivers/header in esp_rom this the way i would add the new manufacturer; i was wounder where the 32MB info comes - so i thinked it is in the flasher stub binary embedded ... which we can not change / add, expand "so easy". thanks for rename the title - it is very better and clear what is mean, sry @radimkarnis for not to be clearer what i was request and thanks for you effort to try figure this out and help me. JFYI: ESP32-S3-WoWZa-N256R256 (compatible wroom pin and size ) makes the start and is now in a test phase (without castellated holes ) (release day 13. Oct 2023 castellated holes ) i use the same flash which is on WROOM-2 ( MX25UM256..) from this side the test goes successful best wishes |
Is your feature request related to a problem?
No response
Describe the solution you'd like
We have the usually flash sizes for usually SPI flashes. For testing newer flash we can set the manufacturer and size there.
How will it be handled for DDR / octal Flashes, since there are more and more manufacturer on DDR octal side also HYPERBUS?
I can't find the DDR octal flash sizes "table" for the used MX25UM in the S3-WROOM-2 or i am going been old.
there is a header yes, but where we can add more manufacturer we did in the esptool "DETECTED_FLASH_SIZE"
example:
ESP32-S3-WROOM-2 N32R8v
it is 32MB Flash
Just a question and an idea note what happens next:
i noted that the outside flash package is "eFused" octal ( 8 data lines ) in the DevKit-C and WROOM-2 ( N32R8v ) and burned -
why extended Flash efused and eMbedded PSRAM ( also 8 data lines ) not?
this give me an experimental idea to try to append more as 8MB PSRAM ( octal ) on the exposed shared flash lines next days.. great. but i think - it will fail cause it is not supported by the IDF "bootloader" and toolchain ..yet .. but i will try to run it outher this limitations customized.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: