• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 3032 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Download NK.bin using EVM Flash

David Headley
Prodigy 80 points

I'm trying to load a Windows CE image using the EVM Flash tool so that some of the guys working with the 3530 EVM board don't have to have Platform Builder installed, or mess with the SD loading method.

With previous WinCE eval products, I've loaded the NK.nb0 file directly into NAND without any issues.  However, the EVM Flash tool doesn't allow downloading of .nb0 files.  I found an option to convert nk.bin files into .raw format within the EVM Flash tool, but that didn't seem to load correctly.  In looking at the memory map of the NAND, it appears as though the WinCE image binary gets loaded at 0x201C1800.

How do I get an NK file loaded into NAND using the TI EVM Flash application?

Thanks

dave

 

  • 0
    Prodigy 80 points

    Sorry to bump, but I've received 0 replies.  Is there a method for downloading NK (either NK.bin or NK.nb0) files through the EVM Flash utility?

     

  • 0 in reply to David Headley
    Prodigy 20 points

    David,

     

    Did you ever get any resolution to this issue? I am in the exact same boat as you.

    We need a way to reflash the NAND with XLDR, EBOOT and NK.* without the use of PlatformBuilder.  I tried the same route you took by using EVMFlash to load the NK.nb0 file, but it complained that "the file would not load or is the wrong format".  I was able to use the EVMFlash tool to look at the flash memory after successfully flashing the NAND from PB.  By comparing the signature of the NK.nb0 file with what I found in NAND, I concluded the NK image was being loaded at 0x201C0800, not 0x201C1800, but that didn't seem to make a difference.  I am currently rebuilding NK.nb0 with different values for the ROMSTART an ROMOFFSET values in config.bib.  I am not clear whether these values need to be addresses in NAND or RAM - I've assumed NAND.

    I also tried using the EVMFlash tool to create NK.raw from the .bin file, but that produced the same result.

    Any other insights you have would be a great help.

    Glenn

    Righthand Technology

  • 0 in reply to Glenn Racette
    Prodigy 80 points

    Hi Glenn, unfortunately I've had no resolution to this. You've pretty much retraced all the steps I tried - have you discovered anything more?

     

    I did find an MSDN article that might work for us, but I haven't set aside the time yet to try it:

    http://msdn.microsoft.com/en-us/library/aa446908.aspx

     

    I don't understand why more people aren't having the same issue - seems like it would be more common.

  • 0 in reply to David Headley
    Expert 2280 points

    Hi David and Glenn,

    Have you had any resolution to this issue?  How do you plan to flash OS image in production?  I have been looking for some way to do the same but have not found it yet.

    I appreciate any help that you can give me.

    Thanks,

    Luan

  • 0 in reply to Luan Le
    TI__Expert 8785 points

    This forum is for OMAP-L1x devices.  It seems like your issue is for OMAP35x.  I would suggest posting this question to either ...

    Hopefully the folks monitoring those forums will be able to assist you.

    --Christina