element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Software Application Development Booting Vxworks Kernel from QSPI
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 311 subscribers
  • Views 1126 views
  • Users 0 members are here
Related

Booting Vxworks Kernel from QSPI

Former Member
Former Member over 9 years ago

Hello everyone,

I want to boot the Vxworks kernel from QSPI flash. i.e. the initial location of the kernel should be the QSPI while starting the board instead of SD card or Ethernet connection from host. I want to know the configuration I need to do, so Vxworks boot loader can find the kernel inside the QSPI flash and then load it to RAM for execution.

Thank you.

  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 9 years ago

    Booting from QSPI or SDI is decided by position of MIO pins on the board. I used
    'Tutorial 04 FSBL and Boot from QSPI and SD Card' on this page as reference. Maybe it will help you as well.
    http://zedboard.org/support/design/4701/76

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago

    You may also find XAPP1258 useful.  There is a section in here about booting VxWorks from SD or QSPI.

    http://www.xilinx.com/support/documentation/application_notes/xapp1258-vxworks-7-bsp.pdf

    Ron

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago

    Thank you for your response. I already have looked at this tutorial but it doesn't solve my problem.

    1) I am already able to make a boot image which consists of FSBL, bitstream file and Vxworks Bootloader and boot the Vxworks through ethernet. The problem is Xilinx/Avnet documents tell you how to configure Vxworks bootloader either to load Vxworks kernel from SD card or through Ethernet from host computer.

    2)I am looking for a solution which will help me put not just the boot image but also the Vxworks kernel on the QSPI flash and how to configure Vxworks bootloader to look for the Vxworks kernel in QSPI flash not the SD card or through Ethernet.

    I hope this will give you a better idea of what I am looking for.

    Thanks,
    Ali.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago

    Thanks for you response. I have been through XAPP1258 and like I mentioned in my reply to GK above. These document tell you how to configure Vxworks bootloader either to load Vxworks kernel from SD card or through Ethernet from host computer.

    Thanks again,
    Ali.

    I am looking for a solution which will help me put not just the boot image but also the Vxworks kernel on the QSPI flash and how to configure Vxworks bootloader to look for the Vxworks kernel in QSPI flash not the SD card or through Ethernet.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to Former Member

    Hi Ali,
    I am not sure what secondary BootL you use. But this is how I do it in uboot. You can follow the tutorial to to flask BOOT.bin and kernel image files into SPI flash.
    Then in my uboot environment my variables are

    ###########################################
    bootcmd = run sfboot
    sfboot = sf probe 0 && sf read ${netstart} 0x520000 0xAE0000 && bootm ${netstart}
    netstart = 0x01000000
    ##########################################

    0x520000 is the start of mtd partition where I flashed my (kernel+dtb+rootfs) image. 0xAE0000 is the size of partition. In short, the command is loading whole partition to RAM at netstart address and then uboot starts loading kernel.
    Thus everything is inside QSPI flash.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube