• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 905 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RTX Flash_FS for LPC2148

Ganesh K

Hi all,

I am using RL_RTX Flash_FS . I follow the steps given in the Keil forum. i face some issues like this

C:\Keil\ARM\RV31\INC\File_lib.c(150): error: #5: cannot open source input file "FS_FlashDev.h": No such file or directory

I want the details for including files for Flash_FS, i include File_Config.c, RTX_Config.c, FSN_ARM_L.LIB.

Thanks in advance,
K.Ganesh

Parents
  • 0 in reply to Westonsupermare Pier

    I'm not sure that this will work at all for NXP devices. NXP uses ECC - single bit error correction with Hamming code. ECC works on a page of 16 bytes, but FlashFS needs to re-program units of 4-bytes.

    So, when FlashFS tries to program additional 4-bytes in a page, which were left un-programmed (at 0xFF), ECC get's corrupted. The data which is read from that location, is also corrupted, because ECC tries to do it's work on data read. This prevents FlashFS to work from internal embedded flash on NXP devices.

Reply
  • 0 in reply to Westonsupermare Pier

    I'm not sure that this will work at all for NXP devices. NXP uses ECC - single bit error correction with Hamming code. ECC works on a page of 16 bytes, but FlashFS needs to re-program units of 4-bytes.

    So, when FlashFS tries to program additional 4-bytes in a page, which were left un-programmed (at 0xFF), ECC get's corrupted. The data which is read from that location, is also corrupted, because ECC tries to do it's work on data read. This prevents FlashFS to work from internal embedded flash on NXP devices.

Children
No data