none
EBOOT reading NK.bin from a FAT formatted NAND partition RRS feed

  • Question

  • Our current BSP can read and load NK.bin from a FAT formatted SD card.

    In our final product we will not have any SD card slot, and we will store the image in the NAND. However for better user experience(i.e. no need for EBOOT menu) upgrading of NK.bin, we would prefer that the NK.bin be stored in a FAT-formatted nand partition. In this way, we can replace the NK.bin via windows explorer.

    Any thoughts, how we need to update our current EBOOT to support this?

    Currently our EBOOT can boot from NAND. But a raw partitioned NAND.

    The EBOOT from TI BSP have a simple FAT filesystem in EBOOT but it's only used to read FAT formatted SD card. I believe there is a difference in reading the NAND and SD addresses. This is the part we have doubt on where to start.

    Any thoughts on this? Thanks

    Thursday, January 9, 2014 4:00 AM

All replies

  • There is no generic low level code for NAND Flash. it is all in the BSP providers hand. My  suggestion is,

    since you have a reference BSP to read or write through FATFS  on SDCard, you can find what are all the function finally involved to perform READ / WRITE operations in SD Card. Replace the Same with a READ/WRITE functions developed for NAND FLASH ( i believe the same BSP should have the low level functionality for NAND FLASH). Otherwise you have to develop the low level read/write functions to your NAND Flash in EBOOT.


    Please mark as answer, if it is correct.
    Please vote,if it is helpful post.
    Vinoth.R

    http://vinoth-vinothblog.blogspot.com
    http://www.e-consystems.com/windowsce.asp

    • Proposed as answer by Keshava GN Friday, January 10, 2014 4:44 AM
    Thursday, January 9, 2014 8:03 AM
  • Another solution would be to allow upgrading the firmware in the raw NAND partition from within CE. We've added that functionality to all our BSPs so our customers can do an easy "from their application" firmware upgrade without the need for EBOOT or even physical access to the device (all can be updated over the internet for instance).

    I think that will be the solution requiring the least amount of work...


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    • Proposed as answer by Keshava GN Friday, January 10, 2014 4:44 AM
    Friday, January 10, 2014 12:24 AM
    Moderator
  • Thanks. I think this is a good suggestion.

    But any thoughts how I can copy a file from the FAT formatted NAND partition to RAW NAND partition at run-time? My doubt is if, I mount it using CE storage manager, it will need to be wrapped by FAT partition in order to read it or at least do data transfer.

    Wednesday, January 15, 2014 7:51 AM
  • No, it's not as simple as "copying" from file explorer.

    You'll need to write some code that reads in the bin file format, and that writes the data to NAND using low level NAND calls (eg. IOCTL_WRITE_SECTOR).

    Depending on what BSP you are using the NAND driver may already implement some IOCTLs that make life easier (like IOCTL_WRITE_FIRMWARE). You need to dive deep into the NAND driver (either way).


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Wednesday, January 15, 2014 8:11 AM
    Moderator