• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 526 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.

NOR BOOT FAILED

Y tck
Intellectual 835 points
Other Parts Discussed in Thread: SYSCONFIG, SYSBIOS

Hi,

My board is referenced  ICE board,boot from NOR Flash,but seems failed.

 I use XDS100v2 to connect the target,and read the value from memory browser,the addrss 0x50000010( GPMC_SYSCONFIG) is 0x00000000(there is no bootloader in nor flash),that meens the GPMC module is a force-idle status,and my SYSBOOT value is 0x411A. Is that normal?

BTW,I use norflash tools to erase the nor flash,and find it blocking in “ wait erase complete”。

Thanks

YanTCK

  • 0
    Intellectual 835 points

    I can write and erase the flash now,because the data-address line mux.but,it boots failed ,when I read the value from memory browser,the PC is 0x20084,and the LR is 0x0800001C or 0x08000020.

  • 0 in reply to Y tck
    Expert 2380 points

    Hi YanTCK,

    Since the LR is pointing to 0x080000xx, its clear that NOR boot loader has at-least started execution and then crashed. Need to see whats going wrong in NOR boot loader.

    By the way, are you using the boot loader binary provided by AM335x Industrial sdk?

    Regards,

    Shahid

  • 0 in reply to Shahid AC
    Intellectual 835 points

    Hi,Shahid:

    I am using the SYSBIOS SDK,but I doubt whether the SDK is correct ,Can you give me some suggestion?

    Thank you!

    YanTCK

  • 0 in reply to Y tck
    Expert 2380 points

    First we need to make sure that NOR has the right boot loader binary.

    To do this, you need to

    1. Put a hardware break point (Run-> New Breakpoint->Hardware Breakpoint) at address 0x08000000 
    2. Do a System rest  ( Run->reset->System Reset). Once this is done, a rest will occur and Program execution will halt at 0x08000000
    3. View the memroy contents at address 0x08000000 using Memory browser. (View->Memory browser)
    4. Open NOR bootloader binary file using an hex editor/viwer program and see the memory content and binary contents matches.

    Please let us know.

    Regards,

    Shahid

  • 0 in reply to Shahid AC
    Intellectual 835 points

    Hi,Shahid:

    Thank for your suggestion,the value in the memory browser and the boot_NOR.bin are same.

    And, when the PC run from "asm" to " C" code (init.asm jump to bl_start),it jumps to the exception code in the ROM_CODE,so I doubt whether the SDK is correct.do you run the SDK code successed?

    Thanks

    YanTCK

  • 0 in reply to Y tck
    Expert 2380 points

    Hi YanTCK,

    NOR boot loader was successfully executed at our end.

    By the way, are you using the pre-built NOR boot loader which was released along with ISDK 1.0.0.4 or are you building NOR boot loader your own ?

    If you are using pre-built bootloader, it would make sense to ensure that the entire binary content in NOR memory (0x08000000) matches with the boot loader binary. This can be done by saving the content to file file in PC(Tools->Save memory).

    In other case, need more investigation I believe,

    Regards,

    Shahid

  • 0 in reply to Shahid AC
    Intellectual 835 points

    Hi Shahid,

    You got it ! the bin is big than 0x1000,so the code wants to jump to the next sector,but befor I config the pinmux of the address-line-12,it can not identify the address.

    Thanks

    YanTCK

  • 0 in reply to Y tck
    Prodigy 10 points

    Hello！I've got the same problem with you. And I don't know how to deal  with it. Will I need to config the pinmux? Can you help me?

    Thanks!

    I've tried the IA_SDK file and the file I builded myself, but all didn't work. And the SPI bootloader is normal.