Search Results
Search results 1-5 of 5.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi Marius, Looking through the NAND Flash examples, why did the developer not use higher level calls for SPI/QSPI, like HAL from ST or the SPI peripheral driver from Nordic, etc. Working at such a low level doesn't help illuminate the functionality required in your NAND drivers. Regards, John
-
Hi Marius, Let me give you and example. The example FS_NAND_HW_QSPI_STM32H743_SEGGER_QSPI_Flash_Evaluator.c. Clearly this software runs on your "(Q)SPI Flash Evaluator” board, but what NAND Flash part did they put on one of the adapter board when they tested this software. Does Universal driver look at the Device ID and adapt the command/“message protocol” for each manufacturer? Regards, John
-
H Marius, Thank you for the info. I'm working on the FS_NAND_HW_TYPE_SPI type driver, but it would be helpful if I could learn how your example implementations work by referencing the datasheets of the NAND flash devices used in those examples. The part numbers and or the datasheets to these parts should have been included in the header comments. Even a readme file explaining the setup would have been helpful. Regards, John
-
I’m mentoring a student from Georgia Tech who is helping develop a biomedical device that uses NAND flash, specifically Toshiba/Kiokia TC58CVG2S0HRAIG, which in the list of Universal drivers supported by Segger. How do I use the Universal driver to write to this device? The board is using a Nordic nRF52840 processor, so I downloaded the Nordic Semiconductor nRF52840-DK evaluation software. I managed to get the USB_MSD example to work, but it is using a ram disk by default. How do I modify this p…
-
If we use FAT32 format for NAND flash, the flash will wear out quickly because we are updating the directory structure each time we write a page of data. We are using a 512MB flash device and storing 400MB each day, so there isn’t a lot of space for wear leveling. One though would be to use FRAM to store the file metadata (directory structure) and the NAND to store only the sample data. Is there a way to separate the metadata and data in emFile so that they can be stored on different devices?