• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 1091 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.

WinCE 7 BSP building XLDRNOR.nb0

Terry Yam
Prodigy 60 points
Other Parts Discussed in Thread: AM3358, TMDXEVM3358

Hi.

I'm using the AM3358 sample board, please tell me the setting of XLDRNOR.nb0 of Windows Embedded Compact 7.

1. If I build an environment of "\ BOOTLOADER \ XLDR \ NOR" folder of AM35x BSP, XLDRNOR.nb0 that can be NOR boot or be generated.

2. Writing to address 0x08000000 the XLDRNOR.nb0 I was produced in 1., Does it do NOR boot.

3. I believe GP Image Header that's not required for the XLDRNOR.nb0. Is it correct.

4. Is there any settings that are different from the NAND boot in GP Image Header other than.

 

Terry Yam

  • 0
    Mastermind 9310 points

    Hello Terry Yam,

    First, could you please tell me which platform you have? Is it the AM335x Starter Kit or the EVM or other? Also please tell me what BSP version you are using.

    You mention you are looking at the NOR folder in the AM35x_BSP folder; however, this target folder is not used for the AM335x platforms. The AM335x platform uses the C:\WINCE700\PLATFORM\AM33X_BSP (depending on the platform you have). You will notice that there is no equivalent NOR folder for this platform because the BSP does not support it by default.

  • 0 in reply to Adeneo Embedded support team
    Prodigy 60 points

    Hi Support team staff

    I'm using, TMDXEVM3358, Beaglebone TMDSEVM3517C.
    TMDSEVM3517C is connected to the NOR Flash in the expansion board.
    The TMDXEVM3358, and to suppress the LCD output, we have to be able to start the NOR Flash built-in.
    TMDXEVM3358 description, it is less than 4KB in XLDR NonMux setting.
    Beaglebone is connected to the NOR Flash in the expansion board.
    NOR Flash is mapped to 0x08000000 of CS0.
    Version of "Windows Embedded Compact 7 BSP" is 2.30.00.03.
    This is where you are looking sample of XLDRNOR is not present only in the BSP AM35x, settings, etc. appears to be not enough.
    Including configuration and value of IMAGE_XLDR_CODE_PA of image_cfg.inc, xldrnor.bib, the makefile.inc, I, I'd like to tell me if there is a file or value to be changed.
    I must be NOR Flash boot TMDX board.
    I'm sorry not good at English.

    Terry Yam

  • 0 in reply to Terry Yam
    Prodigy 60 points

    Hi Support team staff

    Each board, SD boot (MLO) will succeed. "SD boot" after, from EBOOTSD.nb0, LDRNOR.nb0 write to the NOR Flash is successful. XLDRNOR.nb0 are writing to address 0x08000000. MLO and XLDRNOR.nb0 are used in common platform.c. and main.c sdmain.c are very similar.
    Please tell me if there is a configuration file or should examine other.

     

    Terry Yam

  • 0 in reply to Terry Yam
    Mastermind 9310 points

    Hello Terry,

    The BeagleBone BSP v010 and the BeagleBone platform in the 02.30.00 BSP do not support the NORFlash on the expansion board of the BeagleBone. There is neither a bootloader or a driver for communicating with a NORFlash device.

    To support a NORFlash device, you will have to start your own adaptation of the bootloader to support this device. This means first setting the boot pins on the SoC to boot from the NORFlash device. You will then have to create a version of the xldr called XLDRNOR.nb0 that you can write onto the NORFlash device (refer to the AM335x reference manual for instructions on how the romcode boots from NORFlash). The processor will copy this bootstrap into memory and will jump to the first address for execution. In this code, you will want to initialize all of the system's clocks (same as the existing bootloaders do), and then you will want to initialize the NORFlash device. This will require initializing the clocks to the controller and the pad configuration for the pins the device uses. Once the initialization of the NORFlash device is done, you can have the XLDRNOR.nb0 code copy EBOOTNOR.nb0 (which you will have to create) out of the NORFlash into main memory and then jump to that address for execution.

    These are the general steps for supporting booting from a NORFlash device. For specific questions regarding how to initialize the controller or the NORFlash device itself, refer to the AM335x TRM and the NORFlash's reference manual. You will have to create your own disk access layer (FMD for example, similar to NAND)  for reading data out of the device and writing data (boot configuration) back to it.

  • 0 in reply to Adeneo Embedded support team
    Prodigy 60 points

    Hi Support team staff

     

    Thank you for reply.

    I have fixed the start-up for Reading and XLDR. Now, on any of EBOOT that you deployed to the SDRAM is an error in the RAM area reference during startup, I am examining the difference between SDBOOT.

    I'm having problems why the same SDRAM address, I could have written the same EBOOT.nb0, different results SD boot XIP and the boot does not know.

     

    Terry Yam