We are Using:
Version: 2022-04 (22.4.0)Build Id: R20220331-2313
We want to use 16GB eMMC all of which use a JEDEC v5.0/5.1.
when we use such a chip in our system it does not work.
We are using SSP 2.3.0
Are you using this eMMC as the extension of the flash memory?
S7G2 is the 32-bit MCU, so the maximum addressable space is limited with 4 GB, maybe that's the reason.
If this response, or one provided by another user, answers your question, please verify the answer. Thank you!
Renesas Engineering Community Moderatorhttps://community.renesas.com/https://academy.renesas.com/https://en-support.renesas.com/knowledgeBase/
Thank You for your prompt reply.
We are not using eMMC as flash memory,
It is used with FileX to store data as an external Media,
We have tested with 16GB SD-Card and it works fine.
4 GB eMMC works fine but 16GB eMMC is not working.
According to the S7G2 Hardware User's Manual, "The MMC interface supports 1-bit, 4-bit, and 8-bit MMC buses that provide eMMC 4.51 (JEDEC Standard JESD 84-B451) device access. This interface also provides backward compatibility and supports for high-speed SDR transfer modes." (https://www.renesas.com/us/en/document/man/s7g2-microcontroller-group-users-manual?r=1054631#G47.2512524)
So probably, it just doesn't support the later JEDEC version.
We need to use a 16GB eMMC can you suggest any work around?
Since eMMC 5.0+ is being used globally by the vendors, the SSP must be updated to support the same,
It is the need of the hour,
Please Contact your Development Team.
Do keep me posted.
Sure, I'll contact them and will keep you updated.
Thank you for treating this as urgent.
Please share about any development regarding this issue.
If your need is urgent, you should be able to init you eMMC in an earlier, pre-5.1 mode and use the existing driver. Check your datasheet and the HAL layer documentation.
We have checked the datasheets and no such option is available.
You should talk to the part vendor - my understanding is that if the driver only uses jedec 4.52 features, a 5.0 part should work. Or you could add the jedec 5.0 support yourself - the vendor may have a block driver, or you could mod the one from the linux tree for ThreadX. So what doesn't work? Can you ID the part, check size, etc? Something must work unless the connection is different
Suggest leaving DS disconnected
None of the vendors are providing 8Gb or more capacity for eMMC which can be used with an older version than 5.1
Sorry, I meant 5.1 in my post. A 5.1 eMMC should work with an old controller cpu. Leave DS disconnected.
Are any of the command I mentioned working?
I will try this and get back to you soon,
Appreciate your help in the matter.
DS is not connected still we are not getting anything like ID and storage details etc.