Search the Community

Showing results for tags 'boot'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments and the WaveForms software
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Hi everyone, I bought a PmodESP32 evaluation board to test the ESP32 module. In my project I would like to use classic bluetooth (no low energy). When I power up the system and do a scan with a smartphone, the ESP32 module does not appear. If I try to use the AT commands (AT + BTINIT ...) the module replies with an error message. I'm pretty sure the system firmware needs to be updated, so i tried to do a firmware upload but without success. I used various software (Arduino, ESP DOWNLOAD TOOL V3.8.5) but during the procedure it seems that the module is not recognized.
  2. Hi, I'm working on ZYBO SoC. I want to boot it from QSPI flash but it fails anyhow. I have tried two methods using Vivado and IMPACT tool. 1. After successful implementation I created .bit and .bin files for a simple led_blinky project. Than I added "Configuration Memory Device" and selected Spansion s25fl128s 3.3v flash. I loaded the .bin file and then Erased, Verify and Programmed the flash step by step by checking the checkbox. The problem is with verify step. It fails every time. even then if I program it ignoring the failed verify step, it obliviously doesn't boots the pr
  3. Hello, I am using Vivado 2018.2 i downloaded "Zybo-Z7-20-Pcam-5C-2018.2-*.zip" demo project in original project "part" option is choosen then I created a new vivado project i choose "board" option and i created same block design with "Zybo-Z7-20-Pcam-5C-2018.2-*.zip" demo project. I inserted same IP blocks and made connections. I did synthesis and implementation succesfully but when i exported to SDK and i tried to boot from SD card (i used hello world template) i did not see anything on terminal but when i am trying to export original project to SDK not which i create, then i can see he
  4. Hello, i have been searching for a ready to use image to boot form a zybo. where i can make a bootable sdcard just like this e.g.: dd bs=4M if=/path/to/zybo.iso of=/dev/sdx I tried building it with the peta linux guide. This is old and deprecated. Peta linux is missing from the Xilinx website if you dig a little bit deeper you get to the download site for this peta linux. I couldn't find anything there. Isn't there some prebuild image for this hardware somewhere ? Thank you very much.
  5. Hi, I'm trying to Booting My C++ Application from SD Card, I do the following actions: 1.start Vivado software. 2. New Project. 3. Select Zybo from Board lists. 4. Create Block Design. 5. Add Ip 6. Add Zynq7 Processing System. 7. Run Block Automation 8. Route M_AXI_GP0_ACLK pin to FCLK_CLK0 pin. 9. Validate Design (no error). 10. create wrapper 11. Generate Bit stream 12. Export> Export hardware (include bitstream). 13.launch SDK. 14. Create new application (c++). 15. Write my code #include<stdio.
  6. Recently I had to make a standalone Zynq project that had multiple .ELF files all residing on an SD card. The board had to somehow know, while being powered off, which .ELF file to boot from. So how to do this? The answer is in the FSBL file. Currently, in Vivado's 2014.2 SDK, the FSBL can handle multiple "partitions" (that's how any Second Stage BootLoader is called, in our case the .ELF files) by executing the first one, when done returning to the FSBL that handoffs control to the second one and so on. But there is another way with the so called hooks: FsblHookBeforeBitstreamDload, FsblHoo