# Issue with Not Starting PYNQ Linux boot process

**URL:** <https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655>\
**Category:** Support\
**Created:** [October 31, 2024, 12:49am UTC](https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655 "2024-10-31T00:49:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sclee](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@sclee](https://discuss.pynq.io/u/sclee)\
**Post date:** [October 31, 2024, 12:49am UTC](https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655/1 "2024-10-31T00:49:58Z")

</div>

Hello,

I am trying to make a PYNQ image for my custom board (board name: RRAR), which uses Zynq MPSoC ZU5CG as the main FPGA.  
Linux Machine and tool versions I used are Ubuntu 20.04 , Xilinx Vitis, petalinux version 2022.1

I followed the build steps on the ‘Retargeting to a Different Board’ page in the PYNQ document site.

Here is my brief steps to make sd image,

1. get PYNQ

2. Make a custom board folder (‘RRAR’) below ‘boards’  
cd boards  
mkdir RRAR

3. Delete unnecessary board folder under ‘boards’  
rm -rf Pynq-Z1 Pynq-Z2 ZCU104

4. Copy my bitstream file to ‘boards/base’  
Copy my XSA file to ‘boards/RRAR/petalinux\_bsp/hardware\_project’

5. Download prebuilt rootfs and sdist file and copy them to sdbuild/prebuilt folder  
cp -rf /home/download/prebuilt/\* sdbuild/prebuilt

6. Tool seutp  
source ~/petalinux/2022.1/setting.sh  
source ~/Xilinx/Vitis/2022.1/setting64.sh

7. cd sdbuild/  
make

…

After the build process is completed, I can find the ‘RRAR-3.0.1.img’ file is generated below ‘sdbuild/output’ folder and size is about 9.8 GBytes.  
I have flashed the image to an SD card, and tried to boot my custom board.  
But after the linux booting sequence, it stops to promt without the next PYNQ Linux boot process starting ‘Welcome to PynqLinux, based on Ubuntu 22.04!’.

I made the ZCU102 PYNQ image using the same steps explained above, and the PYNQ Linux works well on the ZCU102 board.

I attached two boot log files, one is the ZCU102 and the other is my custom RRAR board.

My Questions is

1. Why does not the RRAR image proceed to PYNQ linux bootup process? Do I miss something in building SD image?

2. In the RRAR Uboot stage, there is no ethernet found messages like,  
_ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr -1, interface rgmii-id No ethernet found._

Any comments and suggestions will be appreciated , and thank you in advance.

– Sangcheol

[rrar–pynq boot.txt](https://discuss.pynq.io/uploads/short-url/jiNMCILtXI9BQaNUv36OIhpUlFJ.txt) (26.5 KB)  
[zcu102–pynq boot.txt](https://discuss.pynq.io/uploads/short-url/dY0muhdW8x0NlLYVCfFv7kAn265.txt) (42.6 KB)

---

<div class="post-metadata">

**Author:** ![sclee](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@sclee](https://discuss.pynq.io/u/sclee)\
**Post date:** [October 31, 2024, 1:10am UTC](https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655/2 "2024-10-31T01:10:28Z")

</div>

Addition to build step 4,

I made a RRAR.spec file ‘boards/RRAR’ folder  
My RRAR.spec file is as shown below

…

ARCH\_RRAR := aarch64  
BSP\_RRAR :=  
BITSTREAM\_RRAR := base/base.bit  
FPGA\_MANAGER\_RRAR := 1

STAGE4\_PACKAGES\_RRAR := xrt pynq ethernet sensorconf boot\_leds pynq\_peripherals

---

<div class="post-metadata">

**Author:** ![sclee](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@sclee](https://discuss.pynq.io/u/sclee)\
**Post date:** [November 5, 2024, 12:32am UTC](https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655/3 "2024-11-05T00:32:51Z")

</div>

After I added a gem3 node in system-user.dtsi file and put the file to the foldes,

PYNQ/boards//petalinux\_bsp/meta-user/recipes-bsp/device-tree/files  
PYNQ/boards//petalinux\_bsp/meta-user/recipes-bsp/uboot-device-tree/files

and then make again image,  
Now ‘No ethernet found’ message in U-boot has been resolved.

However, the boot process still stops linux kernel stage, not go to PynqLinux.  
What should I do more to bring up PynqLinux?

– Sangcheol

…

/include/ “system-conf.dtsi”  
/ {  
};  
&gem3 {  
status = “okay”;  
phy-handle = \<&phy0\>;  
phy-mode = “rgmii-id”;

```
phy0: ethernet-phy@c {
	#phy-cells = <1>;
	reg = <0xc>;
	device_type="ethernet-phy";
	ti,rx-internal-delay = <0x8>;
	ti,tx-internal-delay = <0xa>;
	ti,fifo-depth = <0x1>;
	ti,dp83867-rxctrl-strap-quirk;
};

```

};

---

<div class="post-metadata">

**Author:** ![sclee](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@sclee](https://discuss.pynq.io/u/sclee)\
**Post date:** [November 6, 2024, 8:35am UTC](https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655/4 "2024-11-06T08:35:07Z")

</div>

The issue solved.  
My board has an eMMC & SD on the ZynqMP, the eMMC appears as /dev/mmcblk0 device and a SD Card reader appearing as /dev/mmcblk1.  
It seems the PYNQ looks for a rootfs on mmcblk0 as default.

After some modifications explained in the folIowing link, the issue has been solved.  
The PYNQ linux works well.

– Sangcheol

> [@Cannot make Pynq boot from SD1 (kernel looks in mmcblk0 for rootfs)](https://discuss.pynq.io/t/cannot-make-pynq-boot-from-sd1-kernel-looks-in-mmcblk0-for-rootfs/4759):
>
> I’m bringing Pynq for a custom board, almost there, I just have a problem that the kernel doesn’t seem to look for the rootfs in the right place. This board has an eMMC in sd\_0 and the SD card in sd\_1. I included the following boot args in system-user.dtsi: chosen{ bootargs = "earlycon clk\_ignore\_unused console=ttyPS0,115200 root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait"; }; And I put that file in: \<my board repo\> / \<my board folder\> / petalinux\_bsp/meta-user/recipes-bsp/device-tree/…

> [@Custom board: Rootfs on /dev/mmcblk1p2 not found](https://discuss.pynq.io/t/custom-board-rootfs-on-dev-mmcblk1p2-not-found/1248):
>
> Hi, I was able to complete a custom build for an UltraZedEV board. The board in question has an eMMC on the SOM that appears as /dev/mmcblk0 device and a SD Card reader appearing as /dev/mmcblk1 (with p0 and p1 partitions on the card) While running the build, the kernel loads and finds the devicetree, but I get a kernel panic error, indicating rootFS cannot be found at /dev/mmcblk0 In order to circumvent the problem I tried to reconfigure the devicetree config (system-user.dtsi) as following…

---

<div class="post-metadata">

**Author:** ![marioruiz](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/marioruiz/32/2177_2.png) [@marioruiz](https://discuss.pynq.io/u/marioruiz)\
**Post date:** [November 7, 2024, 4:33pm UTC](https://discuss.pynq.io/t/issue-with-not-starting-pynq-linux-boot-process/7655/5 "2024-11-07T16:33:53Z")

</div>


