Actions
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 268 subscribers
  • Views 867 views
  • Users 0 members are here
Related

Enabling WiFi

jacobb

is there a good tutorial for builindg petalinux starting from an empty block design, with working WiFi and bluetooth?

 

A lot of the reference material is for Vivado 2017.2, and I have Vivado 2018.2 installed

  • 0

    Hello Jacob,

    My suggestions would be for you to follow the Integrating Sensors on MiniZed with PetaLinux (2017.1 and 2017.4) Speedway located here.

    http://zedboard.org/support/trainings-and-videos

    It shows what your looking for.c However it uses either Vivado 2017.1 or 2017.4.

    Thanks,

    Josh

  • 0 in reply to jafoste4

    Thanks for the help, reading through those documents, I figured out how to use the tcl scripts to build the base project for the minized.

     

    I also found another forum post http://zedboard.org/content/adding-wi-fi-and-bluetooth-connectivity-zedboard-using-murata-1dx-pmod

    I was able to follow it to enable the kernel with what I think are the correct kernel mods to enable wifi and bluetooth.  However, in the 2017.2 bsp petalinux project, there are a lot of recipes for and shell scripts for the wifi and bluetooth.  I haven't read through the document too closely, but is there a way to get those recipes into a petalinux 2018.2 project?  Are they really necessary?

  • 0

    Hi Jacob,

    Try taking a look at our GitHub for latest versions of what is available for this design. We may have a 2018.2 version.

    https://github.com/Avnet

    If you want to access Wifi/Bluetooh I would suggest keeping them.

    I would also suggest you take a look at the Petalinux BSPs we have for MiniZed.

    http://zedboard.org/support/design/18891/146

    These projects  should already have the wifi/bluetooth files installed.

    --Josh

  • 0

    Thank you for help so far, I appreciate it.

     

    so, using github.com/avnet/hdl, I was able to build the hardware Vivado project in 2018.2.

     

    I then used the petalinux-create command to exapnd the bsp archive in the 2017.4 lab's folder, I get a warning, but I am able to run the command.

    Next, I use petalinux-config in the project directory using the hdf file from the 2018.2 project.  This runs succesfully and I am able to configure the project.

     

    Finally, whenever I try to run other commands (i.e petalinux-build, petalinux-config -c kernel), I get the same warnings and errors and the command fails.  Is there any way to do this in 2018.2, or would it be easier to roll back to 2017.4?

     

    The warnings and errors I get are as follows

    jacob@Doriath:~/Documents/lab_bsp/minized-sensor-fusion$ petalinux-config -c kernel
    [INFO] generating Kconfig for project
                                                                                    
    [INFO] sourcing bitbake
    [INFO] generating plnxtool conf
    [INFO] generating meta-plnx-generated layer
    [INFO] generating machine configuration
    [INFO] configuring: kernel
    [INFO] generating kernel configuration files
    [INFO] bitbake virtual/kernel -c menuconfig
    Loading cache: 100% |############################################| Time: 0:00:00
    Loaded 3428 entries from dependency cache.
    Parsing recipes: 100% |##########################################| Time: 0:00:04
    Parsing of 2557 .bb files complete (2522 cached, 35 parsed). 3430 targets, 127 skipped, 0 masked, 0 errors.
    WARNING: No recipes available for:
      /home/jacob/Documents/lab_bsp/minized-sensor-fusion/project-spec/meta-plnx-generated/recipes-bsp/device-tree/device-tree-generation_%.bbappend
      /home/jacob/Documents/lab_bsp/minized-sensor-fusion/project-spec/meta-user/recipes-bsp/device-tree/device-tree-generation_%.bbappend
      /home/jacob/Documents/lab_bsp/minized-sensor-fusion/project-spec/meta-user/recipes-connectivity/bluez5/bluez5_5.41.bbappend
      /home/jacob/Documents/lab_bsp/minized-sensor-fusion/project-spec/meta-user/recipes-multimedia/pulseaudio/pulseaudio_9.0.bbappend
    NOTE: Resolving any missing task queue dependencies
    ERROR: Nothing RPROVIDES 'iperf' (but /home/jacob/Documents/lab_bsp/minized-sensor-fusion/project-spec/meta-plnx-generated/recipes-core/images/petalinux-user-image.bb RDEPENDS on or otherwise requires it)
    NOTE: Runtime target 'iperf' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['iperf']
    NOTE: Runtime target 'device-tree' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['device-tree', 'virtual/kernel', 'petalinux-user-image', 'iperf']
    NOTE: Runtime target 'device-tree-dev' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['device-tree-dev', 'virtual/kernel', 'petalinux-user-image', 'iperf']
    ERROR: Required build target 'virtual/kernel' has no buildable providers.
    Missing or unbuildable dependency chain was: ['virtual/kernel', 'petalinux-user-image', 'iperf']
     
    Summary: There was 1 WARNING message shown.
    Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
    ERROR: bitbake failed to cleansstate kernel
    ERROR: Failed to config kernel.
     
    I tried a apt-get install of iperf, but that didn't resolve the issue.
  • 0

    I would probably suggest rollng back to the 2017.4 release and starting with the BSP. Until we relase the 2018.2 BSP it will be quite difficult to support you.

     

    --Josh

  • 0 in reply to jafoste4

    That's what I ended up doing.  I have both versions installed now lol.  I'm still waiting on my minized board.  Avnet says they are in stock, but the shipping date keeps slipping, any idea when it will ship?

  • 0 in reply to jafoste4

    I should add that I ordered the board on 7/25/18 and the available to ship date on avnet keeps changing to a later date