Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 42 subscribers
  • Views 181 views
  • Users 0 members are here
Related

Booting picozed with FreeRTOS app

Former Member

I'm trying to get a picozed to boot and run a FreeRTOS application.

I have the application running and it works, but the problem is the first stage boot loader (FSBL). It seems in order to create an fsbl, I need to use a standalone, and when I do that it seems to create an application under the standalone that starts on the ethernet.

I don't know, but was thinking that if I modified that app so that it didn't start the ethernet, my own app that is running FreeRTOS might be able to get the ethernet and all would be good.

Is there anything special I need to do in order for the FreeRTOS application to startup when the picozed boots? I don't see anything in the Run/Debug settings.

Also, this is being flashed through qspi_single, is that the correct way to do it? My understanding is that I flip both switches up so I can program it, then flip the left switch down so that it will boot from the qspi. Let me know if this is incorrect.

I'm really pushed on this project and thrown into the fire. I have worked with the Xilinx tools in the past with zynq processors, but it's never been a great experience. I like to say:

"The Xilinx SDK is the greatest set of tools on the planet...said NO programmer, EVER!"

Appreciate any insight.

Alan

  • 0

    I should add, this is using the Xilinx SDK 2017.4, which is light years ahead of the 14.4 tools I have used in the past.

     

    Also, I normally use Linux as my development host, but am using Windows this time around as that is what the company I'm working at uses...

  • 0 in reply to Former Member

    Just in case anyone is following at home...(doesn't seem the zedboard folks are), I have a booting picozed on the fmc carrier running the echo app sample. I can now integrate my changes I've made for my app, which was previously running freertos.

     

    The way I got it booting was to create a HW platform, so I now have one for the FMC Carrier and one for my Test Board, I can swap those around to use the FMC Carrier when I need, and my Test Board at work holds a picozed also.

     

    I created a standalone BSP based on that HW platform.

     

    I created a standalone app using the echo template, changed the IPs for my home LAN, and created the boot images and fsbl image.


    I flashed my picozed and whola, it boots the echo example on the new IP. Boots pretty quick.


    Alan

  • 0 in reply to Former Member

    BTW, I didn't actually need to have the app running on FreeRTOS as it turns out, I just need a booting standalone app that will allow me to talk to the device I'm working on.

     

    The FSBL can only be created with a standalone app, so that's what I'm using and it's working.

     

    Alan

  • 0

    I think I might need to go back to the FreeRTOS example on top of the Standalone FSBL, I need to understand that better.

     

    How is it possible to get the FreeRTOS app running on the Standalone FSBL? Is it? The tcp_ interface is way slower, it seems and I can get a network disconnect when trying to display a large menu over ethernet.

     

    Alan