• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 1343 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.

vxworks through spi

Eliah Ninyo
Intellectual 820 points

hello,

i managed to start the EVM with u-boot through spi and the NOR flash. with the help of this (http://e2e.ti.com/support/arm/sitara_arm/f/791/t/246353.aspx)

now i want to do it with vxworks boot.

in the Windriver help they explain what to do to make the vxworks be on the NAND and it is working for me. (starting with u-boot, transfering the boot file with tftp, writing it ro the NAND, change the swittches to boot from NAND and walla).

what do i need to do to make vxworks start from NOR (SPI)?

thanks in advance,

 

  • 0
    TI__Mastermind 25235 points

    Hi Eliah,

    VxWorks OS is not supported from TI. Please post a link to this "booting from NAND" tutorial (or copy and paste it here) and I'll take a quick look at it, but for more adequate answers I suggest you ask for support on their official site.

    Best regards,
    Miroslav

  • 0 in reply to Miroslav Kiradzhiyski XID
    Intellectual 820 points

    4774.target.ziphi,

    i contact their official help and they are not familier with this issue. they are checking to me.

    they need to know what is this MLO.byteswap file to maybe modify it for vxworks boot.

    this is why i'm addressing this forum.

     

    attached is the toturial on how to make it work from nand.

     

     

  • 0 in reply to Eliah Ninyo
    TI__Mastermind 25235 points

    Hi Eliah,

    The MLO and MLO.byteswap (for SPI NOR boot) files are the Secondary Program Loader (SPL). The default boot sequence used in the AM335x evaluation modules is:

    ROM Boot Loader (RBL) --> Secondary Program Loader (SPL) --> U-Boot --> Kernel

    Here is an excerpt from the Giving Linux the Boot training presentation regarding the different boot stages and their purpose:

    Components of the Linux Boot Process (Stages)
    RBL –  ROM Boot Loader, Contained in the ROM of the Part, minimal capability to initialize the processor and read in from off chip into internal RAM the SPL.
    SPL – Secondary Program Loader, called many different names depending on processor (UBL,Xloader) but is code of a minimal  configuration specific to the target board that has the capability to setup the processor to be able to read in the next stage which is U-Boot.
    U-boot – Enables most of the specific processor functionality for the target board and end application to configure the part for booting Linux and to load the kernel image from persistent storage.
    Kernel image – Final stage of the boot process. Kernel initilization, MMU enable, Device Initilization, User Init process and finally user level applications.

    The source code for the SPL, U-Boot and Kernel can be found in the official Linux EZ Software Development Kit (EZSDK) for AM335x.

    The source code for the MLO.byteswap binary can also be found in this git repository: http://arago-project.org/git/projects/?p=u-boot-am33x.git;a=summary

    The VxWorks support team may download and inspect it in order to provide proper support for NOR flash boot.

    Best regards
    Miroslav