Other Parts Discussed in Thread: OMAPL138
Hello Team,
I have a customer that has a few questions related to a NAND part, reading NAND from DSP, and hardware encryption:
They are looking to replace the MT29F4G08ABADAH4, with a newer version MT29F4G08ABAFAH4. The main differences between the two chips are: the new one has 8-bit ECC instead of 4-bit ECC, the page size is doubled to 4096, and the OOB size is 256 instead of 64. We were able to read/write to the NAND. The only problem we ran into was booting up the device from that particular NAND chip.
- My understanding is that our ROM Bootloader only works with 4-bit ECC NAND, our NAND chip has 8-bit ECC. Is there a way to get around this limitation? Also, it would really help if we can get the source code for the ROM Bootloader.
We currently have a NAND-FLASH that is connected to the OMAP-L138 and is used by the U-boot and the Linux running from the NAND. We want to be able to read from this NAND on the DSP core. The DSP core is (C6748) portion of the OMAP-L138 that is running SYS/BIOS, version 6.76.2.00.
- What would be the required steps do we need to follow, and is there any documentation to be able to access and read from our NAND-FLASH, but on the DSP side within a certain offset/memory region of that NAND? Specifically, within the SYS/BIOS RTOS system.
We would like to encrypt the audio data.
- s hardware encryption supported on the OMAP-L138? If not, does TI-SDK have support for a lightweight software audio encryption? We’re open to encrypt the audio data from either the DSP side or the Linux application running on the ARM core. Our limitation is CPU resources. So the less CPU usage for the encryption the better.
Please let me know if you need clarification. Thanks for the help.
Best,
Dajon McGill