Search Results

Hello Gaugan, Would it be possible to enable the debug output of the SD / MMC driver and post the log? The debug output can be enabled by adding the following two defines to FS_Conf.h: C Source Code (2 lines) Thank you. Best regards, Marius

Hello, There are two possibilities to handle more than one partition on an SD card: 1) Using the logical volume feature that allows the application to configure a fixed partition size and offset. You can find more information in the sections "4.3.6 FS_LOGVOL_Create()" and "4.3.7 FS_LOGVOL_AddDevice()" of the emFile manual. 2) Using the disk partition logical driver that employs the information stored in the Master Boot Partition. For more information please refer to the "7.2 Disk partition drive…

Hello Martynas, We will provide you the requested information via the support email. Best regards, Marius

Hello Dave, We are not aware of this behavior. The error messages suggest that the SPI data transfer is not working properly. I suggest you to check first if the SPI controller is correctly configured: - Data is sampled on the rising edge of the clock signal. - The clock signal is HIGH in idle state. You can find more information in the section "6.5.8.1.8 (*pfWrite)()" of the emFile manual. Best regards, Marius

Hello Donal, The Micron MT29F1G01 is supported by the emFile Universal NAND driver. This driver does not perform partial writes to a NAND page. It always writes an entire NAND page at once. Regarding buffering: Using a buffer when writing small chunks of data is recommended for better write performance and for preserving the lifetime of the NAND flash. emFile comes with a configurable file buffer therefor the application is not required to buffer the data itself. Best regards, Marius

Hello Stefan, You can use FS_LOGVOL_Create()/FS_LOGVOL_AddDevice() functions to create two separate volumes on the NOR flash. An example is provided in the section "4.3.7 FS_LOGVOL_AddDevice()" of the emFile manual. The volumes can be accessed from different tasks provided FS_OS_LOCKING is set to 1 or 2. Best regards, Marius

Hello Zdenek, Only the handling of long file names is patented by Microsoft. According to swpat.org some of these patents are still valid, especially in Europe. I recommend you to get in contact directly with Microsoft in order to evaluate these legal issues. No licensing is required if your application uses file names in 8.3 format. Best regards, Marius

Hello, Could you please check the return value of FS_MkDir()? In case of an error the function returns a negative value indicating the reason why the operation failed. The possible error codes are defined at the beginning of the FS.h file (FS_ERRCODE_...) You can get a short text description of the error by calling FS_ErrorNo2Text() with the error code as parameter. Best regards, Marius

Hello, The file system treats the name of the files and of the directories in the same way. FS_FAT_SupportLFN() enables the support for long file name for files as well as for directories. Could you please check the return value of FS_MkDir()? The error code should give a hint about what went wrong during the operation. Best regards, Marius

Hello, I tested here with the version 4.00b of the file system. With support for long file names enabled, I was able to successfully create a file with the name "01-27-2016". Which version of the file system are you using? Does the file system report any errors when you try to create the file? Best regards, Marius

Hello, The file system uses the FS_X_GetTimeDate() function to generate the timestamps of files and directories. In order to have correct timestamps, you should add calls to your RTC routines in this function as documented in the emFile manual. Best regards, Marius

Hello, Would it be possible to provide more details about how do you get this date? Best regards, Marius

Hello chopra.arpita92, It seems that you are trying to create a file with a name longer than 8 characters. This works only when the support for long file names is enabled in the file system. The support for long file names is disabled by default. It can be enabled by calling FS_FAT_SupportLFN() API function. Would it be possible to try this in your application?forum.segger.com/index.php?page=User&userID=5597 Best regards, Marius

Hello leonarff, In some cases, the NOR driver needs to know only the address of a physical sector and it calls GetSectorInfo() with the pLen parameter set to NULL. You can avoid the Hardware Fault error by validating the pLen parameter before dereferencing it. C Source Code (3 lines) Best regards, Marius

Hello Felipe, In the trial version of emFile you are limited to 2 files opened at the same time. In the licensed version of emFile the number of files opened at the same time is limited only by the amount of memory available to file system. Best regards, Marius

Hello SergiiSM, R8C/33M is not supported by the Flasher 5 but it looks like it is similar to R8C/33C. You can try selecting R5F21336CDFP or R5F21336CNFP as target device. Best regards, Marius

Hello Paramasivan, Yes, it is possible to copy files from SD card to USB drive. All you have to do is to add the SD/MMC and the USB MSD drivers to your emFile configuration as in the following example: C Source Code (16 lines)

Hello Bharath, As I already wrote you in the answer to you private message the Adesto AT45DB641E part with 256 byte pages is supported by the latest emFile version (3.34a). You will have to upgrade your emFile license. Best regards, Marius

Hello, emFile does not explicitly limit the depth of a directory. There is however one API function which temporarily stores the full path to a directory: FS_CreateDir(). It uses FS_MAX_PATH define (default: 260 bytes) to allocate the path buffer. Also, when emFile is compiled with FS_MULTI_HANDLE_SAFE is set to 1 the full path to an opened file is stored internally. The maximum number of bytes in the path can be specified using the FS_MAX_LEN_FULL_FILE_NAME define (default: 256 bytes). Best reg…

Hello Sebastian, We did a quick test with a J-Link EDU on a Mac OS X and it works without any problems (see the screenshot below). Have you tried to connect your J-Link EDU to a Windows machine? Does it show the same behavior? forum.segger.com/index.php/Att…9048ec64f4a245de59f2a347d Best regards, Marius