UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Adventurer
Adventurer
662 Views
Registered: ‎11-05-2018

Petalinux Ethernet Issue

Hi,

I have using an RFSOC part, and having the following issue.

I use Netboot in uboot to load Petalinux generated images from tftp server, and this works fine. In my Ethernet settings during petalinux-config, I have set my static IP address as 192.168.1.10 and TFTP server address as 192.168.1.2 - and the image is downloaded over the Ethernet just fine.

BUT, when the linux image is loaded, I see a message saying ETHO not found, and then when I login as root, and type ifconfig, I don't see anything ethernet devices. So I am confused why Ethernet is working correctly for loading image, but not once the image is loaded.

20 Replies
Moderator
Moderator
650 Views
Registered: ‎09-12-2007

Re: Petalinux Ethernet Issue

The u-boot ethernet driver and linux macb driver are different. However, if it works in u-boot. It should work in linux, as the devicetree is the same.

Can you hare the deivcetree?

0 Kudos
Adventurer
Adventurer
627 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Stephen,

I have pasted contents of System-conf.dtsi and system-top.dts. Let me know if you see something of interest.

 

System-conf.dtsi

/*
* CAUTION: This file is automatically generated by PetaLinux SDK.
* DO NOT modify this file
*/


/ {
chosen {
bootargs = "earlycon clk_ignore_unused";
stdout-path = "serial0:115200n8";
};
};

&gem3 {
local-mac-address = [00 0a 35 00 1e 53];
};

&qspi {
#address-cells = <1>;
#size-cells = <0>;
flash0: flash@0 {
compatible = "n25q512a","micron,m25p80";
reg = <0x0>;
#address-cells = <1>;
#size-cells = <1>;
spi-max-frequency = <108000000>;
/delete-node/ partition@qspi-fsbl-uboot;
/delete-node/ partition@qspi-linux;
/delete-node/ partition@qspi-device-tree;
/delete-node/ partition@qspi-rootfs;
/delete-node/ partition@qspi-bitstream;
partition@0x00000000 {
label = "boot";
reg = <0x00000000 0x00100000>;
};
partition@0x00100000 {
label = "bootenv";
reg = <0x00100000 0x00040000>;
}
partition@0x00140000 {
label = "kernel";
reg = <0x00140000 0x01600000>;
};
};
};

 

System-top.dts

/*
* CAUTION: This file is automatically generated by Xilinx.
* Version:
* Today is: Fri Nov 8 11:53:16 2019
*/


/dts-v1/;
/include/ "zynqmp.dtsi"
/include/ "zynqmp-clk-ccf.dtsi"
/include/ "zcu111-reva.dtsi"
/include/ "pl.dtsi"
/include/ "pcw.dtsi"
/ {
chosen {
bootargs = "earlycon clk_ignore_unused";
stdout-path = "serial0:115200n8";
};
aliases {
ethernet0 = &gem3;
i2c0 = &i2c0;
i2c1 = &i2c1;
serial0 = &uart0;
serial1 = &uart1;
spi0 = &qspi;
};
memory {
device_type = "memory";
reg = <0x0 0x0 0x0 0x7ff00000>, <0x00000008 0x00000000 0x0 0x80000000>;
};
};
#include "system-user.dtsi"

0 Kudos
Adventurer
Adventurer
623 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Stephen,

 

Contents of system-user.dtsi (under /project-spec/meta-user/recipes-bsp/device-tree/files)

 

/*
* CAUTION: This file is automatically generated by Xilinx.
* Version:
* Today is: Fri Nov 8 11:53:16 2019
*/


/dts-v1/;
/include/ "zynqmp.dtsi"
/include/ "zynqmp-clk-ccf.dtsi"
/include/ "zcu111-reva.dtsi"
/include/ "pl.dtsi"
/include/ "pcw.dtsi"
/ {
chosen {
bootargs = "earlycon clk_ignore_unused";
stdout-path = "serial0:115200n8";
};
aliases {
ethernet0 = &gem3;
i2c0 = &i2c0;
i2c1 = &i2c1;
serial0 = &uart0;
serial1 = &uart1;
spi0 = &qspi;
};
memory {
device_type = "memory";
reg = <0x0 0x0 0x0 0x7ff00000>, <0x00000008 0x00000000 0x0 0x80000000>;
};
};
#include "system-user.dtsi"

0 Kudos
Adventurer
Adventurer
554 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

I have tried to change the GEM3 settings esp phy number and register setting, but to no avail. I have tried to do that by modifying the system-user.dtsi. I noticed that Uboot config pointed to zcu_102revA.dtsi, so I tried copying gem3 settings from that file, but results don't change. Uboot always works, and kernel always complains that could not find Eth0. 

I was convinced it was a device tree issue, especially related to PHY addressing, but now I am not sure. Anything else that would expalin this behavior?

0 Kudos
Moderator
Moderator
501 Views
Registered: ‎09-12-2007

Re: Petalinux Ethernet Issue

This looks fine, the GEM nodes will be taken from the zcu111-reva.dtsi

https://github.com/Xilinx/device-tree-xlnx/blob/master/device_tree/data/kernel_dtsi/2019.2/BOARD/zcu111-reva.dtsi

 

What do you see when you do a ifconfig?

0 Kudos
Adventurer
Adventurer
486 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

I only see 'lo'. During boot-up, I see a message saying "could not find eth0'.

I have modified the GEM nodes by changing reg/phy addr, etc, but the same result - UBOOT always works (and actually shows different PHY Address in the log message/console), and linux always fails to find eth0.

Is there a definitive place to compare differences between Uboot and Linux in the built image, which could provide some clues?

0 Kudos
Moderator
Moderator
484 Views
Registered: ‎09-12-2007

Re: Petalinux Ethernet Issue

can you try ifconfig up eth0?

 

0 Kudos
Adventurer
Adventurer
475 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

I get a message saying bad address eth0.

 

>> ifconfig up eth0

ifconfig : bad address eth0

0 Kudos
462 Views
Registered: ‎07-23-2019

Re: Petalinux Ethernet Issue

 

you should use 

ifconfig eth0 up

or

ifup eth0

But what about?

ifconfig -a

0 Kudos
Moderator
Moderator
455 Views
Registered: ‎09-12-2007

Re: Petalinux Ethernet Issue

Also, can you send the boot log?

0 Kudos
Adventurer
Adventurer
418 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Ifconfig -a:

 

root@Petalinux-2018:~# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%4882584/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ifup eth0
Cannot find device "eth0"
Cannot find device "eth0"
Cannot find device "eth0"

 

0 Kudos
Adventurer
Adventurer
414 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Hi Stephen,

 

Boot log is below.

Mon Dec 9 18:22:01 2019: Starting internet superserver: inetd.
Mon Dec 9 18:22:01 2019: Configuring packages on first boot....
Mon Dec 9 18:22:01 2019: (This may take several minutes. Please do not power oMon Dec 9 18:22:01 2019: Running postinst /etc/rpm-postinsts/100-sysvinit-inittMon Dec 9 18:22:01 2019: update-rc.d: /etc/init.d/run-postinsts exists during rMon Dec 9 18:22:01 2019: Removing any system startup links for run-postinsts .Mon Dec 9 18:22:01 2019: /etc/rcS.d/S99run-postinsts
Mon Dec 9 18:22:01 2019: INIT: Entering runlevel: 5
Mon Dec 9 18:22:01 2019: Configuring network interfaces... Cannot find device "Mon Dec 9 18:22:01 2019: Cannot find device "eth0"
Mon Dec 9 18:22:01 2019: Cannot find device "eth0"
Mon Dec 9 18:22:01 2019: Starting Dropbear SSH server: Generating key, this mayMon Dec 9 18:22:04 2019: Public key portion is:
Mon Dec 9 18:22:04 2019: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCf/1ZTfmIZibcUEzMon Dec 9 18:22:04 2019: Fingerprint: md5 2a:b9:32:b0:50:14:73:19:f0:c9:61:df:fMon Dec 9 18:22:04 2019: dropbear.
Mon Dec 9 18:22:04 2019: Starting syslogd/klogd: done

 

As you can see above (in red) eth0 is not found.  When I look for messages related to ethernet in dmesg, I see the following.

dmesg | grep eth
[ 0.000000] psci: probing for conduit method from DT.
[ 5.519795] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 5.550204] usbcore: registered new interface driver cdc_ether

I think after the macb line, if things go well, the ethernet driver should be downloaded, and then the device would "appear" in the kernel space. Somehow, the driver is not being downloaded, and I don't know if the "not enabling partial store and forward" message has any clue.

Your help is much much appreciated.

 

 

0 Kudos
Adventurer
Adventurer
410 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Stephen,

One more log information. When I do:

dmesg | grep 'macb\|phy'
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] arch_timer: cp15 timer(s) running at 50.00MHz (phys).
[ 5.497700] libphy: Fixed MDIO Bus: probed
[ 5.519795] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 5.527034] libphy: MACB_mii_bus: probed

 

I think what I should see in that grep is (based on other forum threads). Notice how the steps in red which indicate driver being loaded, are not happening in my case. It seems like that is the root cause (kernel not wanting to download driver for ethernet)

"[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] arch_timer: cp15 timer(s) running at 99.99MHz (phys).
[ 1.773889] libphy: Fixed MDIO Bus: probed
[ 1.778017] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 1.778391] libphy: MACB_mii_bus: probed
[ 1.781754] macb ff0e0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xff0e0000 irq 31 (00:0a:35:00:22:01)
[ 1.781773] TI DP83867 ff0e0000.ethernet-ffffffff:0c: attached PHY driver [TI DP83867] (mii_bus:phy_addr=ff0e0000.ethernet-ffffffff:0c, irq=POLL)
[ 3.621175] xilinx-psgtr fd400000.zynqmp_phy: Lane:1 type:8 protocol:4 pll_locked:yes"

 

 

 

 

 

0 Kudos
Adventurer
Adventurer
341 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Stephen,

Sorry for the multiple posts (am quite desperate to get past this issue). 

I am not sure if this is relevant, but I see the following message at start of boot:

Net: ZYNQ GEM: ff0e0000, phyaddr 15, interface rgmii-id
i2c_mux_set: could not set mux: id: 5 chip: 74 channel: 1
I2C EEPROM MAC address read failed

I would imagine that if the MAC address is not read from the EEPROM, either a random MAC address will be used, or the local-mac-address assigned in the .dtsi files will take effect, but neither seems to be happening. When I look at examine the local-mac-address field/parameter on the RFSOC at /proc/device-tree/amba/ethernet@ff0e0000, I see a gibberish-y value (@5S@), instead of local-mac-address = [00 0a 35 00 22 05] which is the .dtsi.

Is it possible that lack of a coherent MAC address is preventing the macb/Cadence driver from being installed properly?

Chintan

 

0 Kudos
Moderator
Moderator
331 Views
Registered: ‎09-12-2007

Re: Petalinux Ethernet Issue

If the MAC isnt found then the MAC address is set randomly. However, it might be causing an issue.

Can you try the prebuilt images in the ZCU111 BSP:

https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-design-tools.html

Just download and unzip, and use the images in the pre-built folder

 

Your PHY is getting detected, so no issue here. The MACB driver doesnt use the DT for the PHY address, it will search 0 to 31 and if it finds a none ffff

result, it deems this to be the PHY.

 

0 Kudos
Adventurer
Adventurer
314 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Stephen,

 I downloaded the zcu111 BSP, and copied the pre-build images from there. However, since my hardware is not the zcu111 eval kit, I get an error at uboot. If I bypass that by copying uboot from my project, the system hangs during linux boot-up. So, I can't try and use the pre-built images as is. 

Any other experiments you can suggest to figure out why the macb driver is seemingly not OK.

Thanks

CHintan

 

 

0 Kudos
Adventurer
Adventurer
243 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Update:

I tried to use an existing BSP for same board (different FPGA bit file), and then updated petalinux-config --get-hw-description. With this new petalinux build, kernel crashes (but macb driver does load). Any clues what the kernel crash is due to?

 

 

[ 6.984427] macb ff0d0000.ethernet: failed to add to PM domain pd-eth2: -1
[ 6.993938] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 7.001184] libphy: MACB_mii_bus: probed
[ 7.082225] macb ff0e0000.ethernet eth0: Cadence GEM rev 0x50070106 at 0xf0000 irq 31 (00:0a:35:00:22:04)
[ 7.091855] Marvell 88E1510 ff0e0000.ethernet-ffffffff:01: attached PHY drr [Marvell 88E1510] (mii_bus:phy_addr=ff0e0000.ethernet-ffffffff:01, irq=POLL
[ 7.106581] usbcore: registered new interface driver asix
[ 7.111835] usbcore: registered new interface driver ax88179_178a
[ 7.117875] usbcore: registered new interface driver cdc_ether
[ 7.123669] usbcore: registered new interface driver net1080
[ 7.129294] usbcore: registered new interface driver cdc_subset
[ 7.135173] usbcore: registered new interface driver zaurus
[ 7.140719] usbcore: registered new interface driver cdc_ncm
[ 7.147274] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[ 7.155652] zynqmp_gpd_attach_dev error -13, node 22
[ 7.160443] dwc3-of-simple ff9d0000.usb0: failed to add to PM domain pd-us -13
[ 7.167977] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 7.174367] ehci-pci: EHCI PCI platform driver
[ 7.179121] usbcore: registered new interface driver uas
[ 7.184281] usbcore: registered new interface driver usb-storage
[ 7.191368] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as 0
[ 7.198473] i2c /dev entries driver
[ 7.202635] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 33
[ 7.209571] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 34
[ 7.215565] IR NEC protocol handler initialized
[ 7.219915] IR RC5(x/sz) protocol handler initialized
[ 7.224930] IR RC6 protocol handler initialized
[ 7.229427] IR JVC protocol handler initialized
[ 7.233926] IR Sony protocol handler initialized
[ 7.238509] IR SANYO protocol handler initialized
[ 7.243182] IR Sharp protocol handler initialized
[ 7.247852] IR MCE Keyboard/mouse protocol handler initialized
[ 7.253646] IR XMP protocol handler initialized
[ 7.259074] usbcore: registered new interface driver uvcvideo
[ 7.264635] USB Video Class driver (1.1.1)
[ 7.270430] Bluetooth: HCI UART driver ver 2.3
[ 7.274705] Bluetooth: HCI UART protocol H4 registered
[ 7.279800] Bluetooth: HCI UART protocol BCSP registered
[ 7.285094] Bluetooth: HCI UART protocol LL registered
[ 7.290180] Bluetooth: HCI UART protocol ATH3K registered
[ 7.295542] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 7.301813] Bluetooth: HCI UART protocol Intel registered
[ 7.307133] Bluetooth: HCI UART protocol QCA registered
[ 7.312351] usbcore: registered new interface driver bcm203x
[ 7.317972] usbcore: registered new interface driver bpa10x
[ 7.323502] usbcore: registered new interface driver bfusb
[ 7.328954] usbcore: registered new interface driver btusb
[ 7.334381] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 7.340036] usbcore: registered new interface driver ath3k
[ 7.345572] EDAC MC: ECC not enabled
[ 7.349180] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac contler zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[ 7.361591] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 12000KHz
[ 7.368808] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for q 1200000000 (-34)
[ 7.377575] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency chan to: 1199999 KHz
[ 7.385941] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for q 1200000000 (-34)
[ 7.395032] sdhci: Secure Digital Host Controller Interface driver
[ 7.401030] sdhci: Copyright(c) Pierre Ossman
[ 7.405351] sdhci-pltfm: SDHCI platform and OF driver helper
[ 7.411141] zynqmp_gpd_attach_dev error -13, node 39
[ 7.415928] sdhci-arasan ff160000.sdhci: failed to add to PM domain pd-sd013
[ 7.423266] zynqmp_gpd_attach_dev error -13, node 40
[ 7.428124] sdhci-arasan ff170000.sdhci: failed to add to PM domain pd-sd113
[ 7.436602] ledtrig-cpu: registered to indicate activity on CPUs
[ 7.442556] usbcore: registered new interface driver usbhid
[ 7.447965] usbhid: USB HID core driver
[ 7.451898] Synchronous External Abort: synchronous external abort (0x96000) at 0xffffff800af30200
[ 7.460940] Internal error: : 96000010 [#1] SMP
[ 7.465430] Modules linked in:
[ 7.468461] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0 #1
[ 7.474340] Hardware name: xlnx,zynqmp (DT)
[ 7.478492] task: ffffffc87b848d00 task.stack: ffffff8008038000
[ 7.484382] PC is at clk_wzrd_probe+0x14c/0x568
[ 7.488873] LR is at clk_wzrd_probe+0x134/0x568
[ 7.493371] pc : [<ffffff8008779db4>] lr : [<ffffff8008779d9c>] pstate: 80145
[ 7.500723] sp : ffffff800803bbf0
[ 7.504009] x29: ffffff800803bbf0 x28: ffffff8008d763c8
[ 7.509285] x27: 0000000000000007 x26: ffffff8008e31000
[ 7.514563] x25: ffffff8008d10474 x24: ffffffc87ffe86a0
[ 7.519839] x23: ffffffc87bbcb000 x22: ffffffc87bbcb010
[ 7.525114] x21: ffffffc87a93a980 x20: 0000000000000000
[ 7.530392] x19: ffffffc87ae4d618 x18: 0000000000000001
[ 7.535667] x17: 0000000000000001 x16: 0000000000000019
[ 7.540945] x15: ffffffffffffffff x14: ffffffffffffffff
[ 7.546220] x13: 0000000000000010 x12: 0101010101010101
[ 7.551499] x11: 0000000000000028 x10: 0101010101010101
[ 7.556774] x9 : 0000000000000000 x8 : ffffffc87a93aa00
[ 7.562052] x7 : 0000000000000000 x6 : 000000000000003f
[ 7.567327] x5 : 0000000000000000 x4 : 0000000000000000
[ 7.572605] x3 : ffffffc87b848d00 x2 : 0000000000000000
[ 7.577880] x1 : ffffff800af30200 x0 : 0000000007735940
[ 7.583159] Process swapper/0 (pid: 1, stack limit = 0xffffff8008038000)
[ 7.589816] Call trace:
[ 7.592242] Exception stack(0xffffff800803bab0 to 0xffffff800803bbf0)
[ 7.598642] baa0: 0000000007735940 fffff0af30200
[ 7.606427] bac0: 0000000000000000 ffffffc87b848d00 0000000000000000 0000000000000
[ 7.614212] bae0: 000000000000003f 0000000000000000 ffffffc87a93aa00 0000000000000
[ 7.621997] bb00: 0101010101010101 0000000000000028 0101010101010101 0000000000010
[ 7.629782] bb20: ffffffffffffffff ffffffffffffffff 0000000000000019 0000000000001
[ 7.637567] bb40: 0000000000000001 ffffffc87ae4d618 0000000000000000 fffff7a93a980
[ 7.645353] bb60: ffffffc87bbcb010 ffffffc87bbcb000 ffffffc87ffe86a0 fffff08d10474
[ 7.653138] bb80: ffffff8008e31000 0000000000000007 ffffff8008d763c8 fffff0803bbf0
[ 7.660923] bba0: ffffff8008779d9c ffffff800803bbf0 ffffff8008779db4 0000080000145
[ 7.668709] bbc0: ffffff800803bbe0 ffffff80084b1d34 ffffffffffffffff 0000000000000
[ 7.676493] bbe0: ffffff800803bbf0 ffffff8008779db4
[ 7.681337] [<ffffff8008779db4>] clk_wzrd_probe+0x14c/0x568
[ 7.686875] [<ffffff800856b6a0>] platform_drv_probe+0x58/0xb8
[ 7.692581] [<ffffff8008569a8c>] driver_probe_device+0x22c/0x2d8
[ 7.698551] [<ffffff8008569bf4>] __driver_attach+0xbc/0xc0
[ 7.704001] [<ffffff8008567bcc>] bus_for_each_dev+0x4c/0x98
[ 7.709536] [<ffffff8008569388>] driver_attach+0x20/0x28
[ 7.714811] [<ffffff8008568ed8>] bus_add_driver+0x1b8/0x228
[ 7.720349] [<ffffff800856a5a0>] driver_register+0x60/0xf8
[ 7.725798] [<ffffff800856b5f0>] __platform_driver_register+0x40/0x48
[ 7.732200] [<ffffff8008d3d700>] clk_wzrd_driver_init+0x18/0x20
[ 7.738081] [<ffffff8008083980>] do_one_initcall+0x38/0x128
[ 7.743617] [<ffffff8008d10cc4>] kernel_init_freeable+0x138/0x1d8
[ 7.749671] [<ffffff80089fe3e0>] kernel_init+0x10/0x100
[ 7.754862] [<ffffff8008084a90>] ret_from_fork+0x10/0x18
[ 7.760139] Code: eb01001f 54001508 f9401661 91080021 (b9400021)
[ 7.766194] ---[ end trace 59ecab20103ab5d7 ]---
[ 7.770789] Kernel panic - not syncing: Attempted to kill init! exitcode=000000b
[ 7.770789]
[ 7.779861] Kernel Offset: disabled
[ 7.783318] CPU features: 0x002004
[ 7.786691] Memory Limit: none
[ 7.789722] ---[ end Kernel panic - not syncing: Attempted to kill init! ecode=0x0000000b
[ 7.789722]

0 Kudos
Adventurer
Adventurer
158 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Stephen,

Any thoughts on this?

0 Kudos
133 Views
Registered: ‎07-23-2019

Re: Petalinux Ethernet Issue

 

If you configure Petalinux from a BSP you can only (succesfully) load it in the board for what that BSP is, is that the case?

 

0 Kudos
Adventurer
Adventurer
115 Views
Registered: ‎11-05-2018

Re: Petalinux Ethernet Issue

Sort of, but not quite. Here is the synopsis of my problem. I have a custom board using RFSOC, with two Petalinux images.

 

Petalinux image 1: It was created using ZC111 bsp as template, and then def-hw-config for the PL image in question. With this image, kernel loads fine, but Eth0 does not come up (though Ethernet port works for TFTP boot). GbE is configured via GEM3 on the ARM using off-chip PHY chip. Curiously enough, looking at boot log when kernel comes up, it seems that the macb driver (Ethernet driver) does not really get loaded. It does not seem to be device tree issue based on lots and lots of experiments focussing on that.

 

Petalinux image 2: It was created using the BSP template given by the vendor who made the board, but for a hardware configuration diffferent from the one we use (its confusing since our use-case of the board has a different rear-transistion module and PL is used differently from the vendor released BSP.) Having said that the board is the same, and the GEM3 controller is also being activated in vendor PL. WIth this image, Ethernet comes up (looking at log message), but kernel crashes (fatal crash). 

The actual kernel and uboot is the same for both images, and as are the config files (rootfs and config). The device trees also seem the same (as far as I can see). but i haven't bee able to figure out the reason for either the kernel crash in image 2 or ethernet not coming up image 1. Ideally, I just want to learn and apply the setting in image/project 2 that makes ethernet work to project 1.

I am new to Embedded (traditional FPGA guy), so tottering from one post/article to another and one experiment to another. Any insights from the seasoned folks would be invaluable.

0 Kudos