element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • 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
MiniZed Hardware Design Minized Petalinux 2020 - WiFi Shell Script
  • 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 Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 324 subscribers
  • Views 1038 views
  • Users 0 members are here
  • minized petalinux
  • avnet
  • petalinux2020
Related

Minized Petalinux 2020 - WiFi Shell Script

apadana1984
apadana1984 over 4 years ago

Hello,

 

I am building Petalinux 2020.1 for my Minized Board. I downloaded the Avnet BSP package. I noticed that the default Shell script for enabling the WiFi module has an issue:

 

#Mount the eMMC

echo "Mount the eMMC."

mount /dev/mmcblk1p1 /mnt

 

When I boot my Petalinux, there is not such "mmcblk1p1". There is "mmcblk0p1". What is the best way to correct this file? I changed it and re-built my Petalinux, however, the shell script in the image file didn't change!!! Am I missing something?

 

Also, I changed my "wpa_supplicant.conf" file to include my WiFi user ID&PASSWD, however, the file doesn't change in the linux image file.

 

I appreciate if someone can look into this problem.

 

Thank you

  • Sign in to reply
  • Cancel

Top Replies

  • narrucmot
    narrucmot over 4 years ago +1 suggested
    Hi Iman, That shell script (wifi.sh?) has been used for years, so I am surprised that it is breaking now. I will look into this. The reason why the script reverts to its original state on a reboot is because…
Parents
  • narrucmot
    0 narrucmot over 4 years ago

    Hi Iman,

     

    That shell script (wifi.sh?) has been used for years, so I am surprised that it is breaking now.  I will look into this.

     

    The reason why the script reverts to its original state on a reboot is because the MiniZed, by default, boots a RAMdisk root filesystem.  This means the entire filesystem exists in RAM while the system is booted and is thus volatile.  Changes and edits to files are not persistent on a reboot.  That is why the wpa_supplicant.conf file, once edited with your WLAN SSID and password information, is meant to be stored on the FAT partition of the eMMC (mmcblk<0|1>p1) memory.

     

    The MiniZed can be configured to boot the Linux kernel from QSPI and mount a persistent filesystem on a EXT4 partition of the eMMC.  I believe there are shell scripts provided in the BSP that will program the QSPI and eMMC for this boot method.

     

    --Tom

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • apadana1984
    0 apadana1984 over 4 years ago in reply to narrucmot

    Thank you Tom. By non-updating scripts, I meant the scripts in "rootfs.wic" file created in the host Linux machine. There are two directories in which we can find "rootfs.wic":

     

    1. <project-home>/images/linux/
    2. <project-home>/pre-built/linux/images

     

    The first one updates once we build the Petalinux project. But the second one doesn't update. Maybe its name "pre-built" implies that.(?!)

     

    Iman

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • apadana1984
    0 apadana1984 over 4 years ago in reply to narrucmot

    Thank you Tom. By non-updating scripts, I meant the scripts in "rootfs.wic" file created in the host Linux machine. There are two directories in which we can find "rootfs.wic":

     

    1. <project-home>/images/linux/
    2. <project-home>/pre-built/linux/images

     

    The first one updates once we build the Petalinux project. But the second one doesn't update. Maybe its name "pre-built" implies that.(?!)

     

    Iman

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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