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: 
Observer deepakddn
Observer
1,534 Views
Registered: ‎05-12-2016

in zcu102 linux based elf conflicting withthe ones included in BOOT.bin

I am working on Example1 given in ug1209 (which is based on Vivado 2016.4 and Petalinux 6.4). However, I am using Vivado 2017.3 , SDK 2017.3 and Petalinux 7.3.

 

There are a few changes I observed:

 1] while creating ps_pl_linux_app.elf:

  - There is no reference for HW platform, when selecting OS as Linux as decribed in example. It ask to select processor psu_cortesA53 that I do.

  - When adding  "pthread" for libraries, I see the new  compiler is ARM v8 Linux gcc compiler

 

 2] While creating tmr_psled_r5:

 - The application ask for selecting A53 processor (Should it be A5??)

 

When running the application from SD card, I can see COM1 outputs hangs after following COM0 logs (it does not in pre-built images provided):

   COM 0 Logs:

Configuring network interfaces... [    4.825922] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Starting Dropbear SSH server: Generating key, this may take a while...

 COM 1 Logs:

  

PS LED Turned OFF
PS LED Turned ON
PS LED Turned OFF
PS LED Turned ON
PS LED Turned OFF
PS LED Turned ON

RPU in WFI mode. Press any key to repeat the sequence
PS LED Turned OFF
PS LED Turned ON

 

Another issue is that when I run ps_pl_linux_app.elf as described, I see  GPIO 360 (SW 19) does not exist in linux subsystem and so I disabled the SW 19 port in file. So, I changed switch for both switches to be SW17 (GPIO 336). However, I see that output is not as expected and I see following logs on COM 0:

root@xilinx-zcu102-2017_3:~# cp /run/media/mmcblk0p1/ps_pl_linux_app1.elf /tmp
root@xilinx-zcu102-2017_3:~# /tmp
-sh: /tmp: Is a directory
root@xilinx-zcu102-2017_3:~# /tmp/ps_pl_linux_app1.elf
Press SW17 or SW19 on the board
SW17 is PL Push Button :: SW19 is PS Push Button
----PL Button pressed, observe PL LED [0:3]----

PS Button pressed, observe PL LED [4:7]
[   46.796291] macb ff0e0000.ethernet eth0: link up (1000/Full)
[   46.801944] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   47.159702] random: crng init done

  I am not sure why I am getting this output , and also LEDs are not working with SW17 now.

 

 Thanks

0 Kudos
5 Replies
Observer deepakddn
Observer
1,507 Views
Registered: ‎05-12-2016

Re: in zcu102 linux based elf conflicting withthe ones included in BOOT.bin

In my above post, I was using wrong image to build petalinux images. However, I still see that COM1 outputs freezing around following log in COM0. COM1 output never changes after that.

Configuring network interfaces... [    4.825922] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background done.
Starting Dropbear SSH server: Generating key, this may take a while...

After copying the ps_pl_linux_app.elf now, I  can see a cleaner output. However, I still cannot see switches and LED working:

root@xilinx-zcu102-2017_3:~# cp /run/media/mmcblk0p1/ps_pl_linux_app1.elf /tmp
root@xilinx-zcu102-2017_3:~# /tmp/ps_pl_linux_app1.elf
Press SW17 or SW19 on the board

SW17 is PL Push Button :: SW19 is PS Push Button

 

The GPIOs are registered as seen in log below, but base seems different from the ones in prebuilt images

[    1.336790] raid6: .... xor() 1220 MB/s, rmw enabled
[    1.336801] raid6: using intx1 recovery algorithm
[    1.337182] GPIO IRQ not connected
[    1.337195] XGpio: /amba_pl@0/gpio@80000000: registered, base is 507
[    1.337389] GPIO IRQ not connected
[    1.337402] XGpio: /amba_pl@0/gpio@80010000: registered, base is 499
[    1.338636] SCSI subsystem initialized
[    1.338809] usbcore: registered new interface driver usbfs
[    1.338857] usbcore: registered new interface driver hub

Appreciate any help in advance.

Thanks,

 

0 Kudos
Moderator
Moderator
1,464 Views
Registered: ‎10-06-2016

Re: in zcu102 linux based elf conflicting withthe ones included in BOOT.bin

Hi @deepakddn

 

Did you take a look to the latest UG1209 document? It is based on Vivado/Petalinux 2017.2 which clearly is much more recent than the one that you are using :)

 

Please follow the newest document as that may have some changes related to software release, if still not able to make it work just post your questions again.

 

Regards,

Ibai


Ibai
Don’t forget to reply, kudo, and accept as solution.
Observer deepakddn
Observer
1,448 Views
Registered: ‎05-12-2016

Re: in zcu102 linux based elf conflicting withthe ones included in BOOT.bin

I followed the new doc, and found the ps_pl_linux_app working (can see LEDs and SW working), but tmr_psled that should output on UART1 is now not giving any output. I tried changing the memory offsets in lscripts.ld to 0x40000000, as welll as 0x70000000. Both did not seem to affect the output.

 

Thanks,

0 Kudos
Moderator
Moderator
1,430 Views
Registered: ‎10-06-2016

Re: in zcu102 linux based elf conflicting withthe ones included in BOOT.bin

Hi @deepakddn

 

Take a look to the BSP settings for the project as the stdio is selected in the GUI. You might be redirecting to somehere else rather than UART1.

 

Regards,

Ibai


Ibai
Don’t forget to reply, kudo, and accept as solution.
0 Kudos
Observer deepakddn
Observer
1,412 Views
Registered: ‎05-12-2016

Re: in zcu102 linux based elf conflicting withthe ones included in BOOT.bin

I have verified that BSP config is set for psu_uart1 for stdin and stdout.  Also, the file tmr_psled_r5.c is set for GPIO 0, and UART1. The dtsi file has uart1 status is "disaled".

 

I tried using the destination cpu for elf file as R5 lockstep as well as R5_0 while creating BOOT.bin. However, none of configurations are starting hearbeat LED and UART1 logs.

 

Thanks,

0 Kudos