Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


Ionel last won the day on April 23

Ionel had the most liked content!

About Ionel

  • Rank
    Frequent Visitor

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. What will manage access to your SDCARD? Do you realy whant to share data via SDCARD? Why not use shared memory?
  2. @thenumberdevil In Linux interrupts are handled in kernel-space not in user-space. There is extra work to do that in user-space.
  3. @pcrack Please attach the boot log in a txt file?
  4. Ionel

    Zybo Z7-20 BOARD -PLATFORM

    If you intend to use petalinux a good start will be with this document.
  5. picocom may be a solution / or putty example: picocom -b 115200 /dev/ttyUSB0 with sudo if neccessay It is best to use linux tools for connecting to Linux target. and not to mix them up. You have a GNU/Linux instance to run petalinux, why not connect from it to the target os/board? Any way, use something that will send keystrokes to the terminal. Usually ^O is shortcut for opening files and is not sent to the target by some tools.
  6. packagegroup-core-buildessential
  7. How do you connect to the board ?
  8. Your custom linux distro made using petalinux tool does not contain a gcc. It needs to be added same as you added mc.
  9. Change the terminal emulator
  10. That is the normal and expected behavior in Linux for any tool.
  12. Most of the problems you face could have been avoided if you booted from sd card and place the uEnv.txt alongside BOOT.bin and image.ub. For debugging Linux kernel JTAG can actually create errors since is multithreading & multicore system. To pack bitstream in BOOT.BIN use petalinux-package --boot --u-boot --fpga images/linux/{filename}.bit --force --force is for overwriting BOOT.BIN file if exists. Do you understand the paradox of uEnv.txt in your context? "Run instructions in uEnv.txt before you obtain the uEnv.txt" In this case you may want to change platform-top.h to do everything inside uEnv.txt. and you won't need the uEnv.txt but you will have to recompile u-boot on any changes in u-boot environment. You end up doing more work just to start the system over JTAG. If your target is to develop fsbl or u-boot that is what you will do. But since you need the tftp to boot the system from network your bootflow adds manual labour for every boot. A normal workflow will be: 1. Do changes in vivado 2. Generate hdf that includes the bitstream 3. Import it in petalinux (petalinux-config --get-hw-description=/path/to/hdf/directory) 4. Do changes to device tree, rootfs or any other petalinux components if necessary. 5. Build and generate BOOT.BIN 6. Copy BOOT.BIN and image.ub on sd card (uEnv.txt in this case to boot image.ub from tftp thus image.ub on sd card is no longer needed) 7. Power on the board. If you change one of: fsbl, device tree or u-boot you need to regenerate the BOOT.BIN and copy it to SD card for the canges to take efect on next boot.
  13. You made some changes that affected the BOOT.BIN It can be: 1. to fsbl. 2. to u-boot 3. to device tree To fix: please try a rebuild of the entire project. If you use git to track changes check what changed.
  14. Do you use an SD card? How do you load fsbl and u-boot?
  15. That file in ./build/tmp/.. is generated by a bitbake recipe (petaliunx engine) if you don't findit in ./images/linux/ it was not prepared to be used.