Search Results

Hello Caster, You can try to enable the CRC verification of the data via the FS_MMC_ActivateCRC() API function to check if it helps preventing file system corruptions. The emFile SPI MMC/SD driver retries a data read operation (up to 10 times by default) if it detects a CRC error in the data received from SD card. Best regards, Marius

Hello, FS_FindFirstFile() and FS_FindNextFile() always return the directory entries in the order they are located physically on the storage device. Any other ordering will have to be implemented in the application. Best regards, Marius

Hello Craig, The latest emFile version (5.16.0) comes with support for the Alliance Memory AS5F34G04SND serial NAND flash device (segger.com/downloads/emfile/Release_emFile.html). Best regards, Marius

Hello anas, You will have to build emFile with FS_MULTI_HANDLE_SAFE set to 1 (FS_MULTI_HANDLE_SAFE) if your application is required to access the same file in read and write mode using different file handles. Would it be possible to give this a try? Thank you. Best regards, Marius

Hello Len, The write latencies your application is experiencing are probably related to some internal operations performed by the SD card such as wear leveling or garbage collection. emFile does not have any influence on the timing of these operations. All the file system operations are blocking which means that an API function returns only when the operation is completed. Currently, emFile does not support non-blocking operations. You can try to reduce the write latencies by configuring a secto…

Hello John, The low-level drivers are called hardware layers in emFile. The type of the hardware layer that has to be implemented depends on how the NAND flash device is interfaced with the MCU. The NAND hardware layers are described in the section "6.3.5.1 NAND hardware layer" of the emFile manual. Two hardware layers are applicable for the type of NAND flash device you are using: FS_NAND_HW_TYPE_QSPI and FS_NAND_HW_TYPE_SPI. If the NAND flash device is interfaced via an quad SPI controller the…

Hello John, The management data has to be stored on the same storage device as the file data. It is not possible to store them on separate storage devices. You can reduce the number of write operations performed by the file system by configuring a sector cache in write back mode. You can find more information about the sector cache in the section "5.1 Sector cache" of the emFile manual. Best regards, Marius

Hello, The error code 63 is an indication that the internal storage of the Flasher 5 is damaged. This error has nothing to do with the type of device selected and is probably the difference in the the size of the data file being programmed that makes the error being reported for one device and not for the other. I am afraid that your Flasher 5 device is damaged and cannot be used reliably anymore. You can take advantage of our trade-in program and purchase a new Flasher 5 at a discounted price: …

Hello, We plan to add support for the Cypress S25FL256L device but I cannot give you a fixed availability date. We will try to have it ready by the beginning of next year. Best regards, Marius

Hello Rune, emFile does not provide any API that can be used to get progress information about the high-level format operation. You will have to get that information by looking a the low-level operations performed in the hardware layer of the SD / MMC driver. Best Regards, Marius

Hello Dave, Quote: “ Is emFile suitable for: - nor SQI flash 64Mb - use under FreeRTOS (customer requirement) ” emFile supports SPI NOR flash via the NOR driver. The file system can be used with any operating system including FreeRTOS. Quote: “Is a hook provided to flush any cache for use entering power-down? ” emFile does not provide such a functionality. Quote: “Or is it expected that external hardware resets the processor while giving the flash time to finish up any operations in progress? ” …

Hi, The libraries found in the emFile_Trial_V404f.zip archive can be used only on Windows. You can used this trial package to test the file system on a Windows PC as described in the section "2.2 Using the Windows sample" of the emFile manual. If you want to test emFile on a target hardware you will have to use the emFile libraries that come with one of the evaluation software packages available from here: segger.com/evaluate-our-software/ I am not sure what CPU you are using but if it is a Cort…

Hello, There are many reasons why the file system gets corrupted. The typical reason for the corruption of the file system stored on a NAND flash is the occurrence of uncorrectable bit errors. Bit errors can occur during the normal operation of the NAND flash and ECC has to be employed to correct them. If more bit errors occur than the ECC is able to correct the data gets corrupted. The datasheet of the NAND flash documents how many bit errors the ECC have to be able to correct in a specified da…

Hello Kari, eMMC devices use a request-response serial protocol to communicate with the host. There is an overhead related to exchanging data transfer that involves selecting the device, sending the command that starts the data access, etc. Your application can achieve better performance by keeping this overhead to a minimum. This means that the application has to transfer as much data at once as possible. The data to be exchanged has to be aligned to a logical sector boundary and a multiple of …

Hello Micaël, It looks like your Flasher 5 device has been damaged. The data file is stored to a non-volatile memory and should survive a power cycle. You can trade in your defective device under the conditions described here: segger.com/purchase/trade-in-program/ Best regards, Marius

Hello, The error indicates that the file system has been corrupted. More exactly, a FAT cluster is marked as in use in the allocation table but FS_CheckDisk() cannot find any file or directory that actually uses this cluster. The FAT file system is not fail-safe by design and a sudden reset can easily corrupt it. SEGGER provides a Journaling add-on that can be used to make the FAT file system fail-safe. You will have to use this add-on to protect the structure of the file system against sudden r…

Hello John, Unfortunately there is no other way to update the firmware of the Flasher 5 PRO. The firmware image you generated seems to be OK. I was able to downgrade my Flasher 5 PRO from version 2.14b to using it. Do you see any activity on the green LED after you plug in the USB cable to perform the firmware update? Is the firmware image still present on the internal storage of the Flasher 5 PRO after the firmware update? Best regards, Marius

Hello John, I have uploaded the version 2.00x of the Flasher software to our website. You can download it from here: segger.com/downloads/flasher/SetupFlasher_V200x.zip The "firmware.bin" file can be created by converting to binary the "Firmware/FW600.mot" file located in the installation directory of the Flasher software. Best regards, Marius

Hello, Would it be possible to try to update the firmware of the Flasher 5 PRO as described in the following steps? Thank you. - Remove the USB cable. - Insert the USB cable while keeping pressed the "Start/Stop" key of the Flasher 5 PRO. - Release "Start/Stop" key of the Flasher 5 PRO after the green LED stops blinking. - Open the "Computer" window on the Windows PC. The internal persistent storage of the Flasher 5 PRO should be visible in there as removable device. - Right-click on the removab…

Hello Gaugan, I analyzed the logs but I was not able to find any reason why the mounting of the SD card fails The communication to SD card seem to work properly. Could you please post a screen capture of the call stack showing in which function the code actually blocks? Thank you. Best regards, Marius