ManiS

Facing issues with dpmutil integration with petalinux 2023. We have gone through Eclypse-PMCU-Specification-Public pdf. As per our understanding we can check VADJs status and override values with I2C also using configuration registers. Same functionality as dpmutil/decutil. Is this understanding is correct?

Hi , can you please give a reference for petalinux example, how to use the source code and run it on Eclypse Z7 ? The source code is shared here are older versions, are related to BareMetal? and not a petalinux use case ? GitHub - Digilent/dpmutil: Digilent Platform Management Utility Eclypse-Z7-SW/src/calibration_reader/src/main.c at b42fb15a8ab4c52a38db2c15918cd7263e84f65e · Digilent/Eclypse-Z7-SW · GitHub

Hi , Can you please give us a reference for petalinux example, how to use the source code and run it ?

any clues or idea team ? is there anything to be done for allocating memory for kernel or set values for kernelLoadAddr , dtbLoadAddr? Any memory setting needs to be done for eclypse Z7 board as shown below picture? in System-user.dtsi i have put the following setenv bootargs console=ttyPS0,115200 earlyprintk root=/dev/mmcblk0p2 rw rootwait/;load mmc 0 ${kernel_load_address} zImage/;setenv bitstream_image system_wrapper.bit.bin/;load mmc 0 ${loadbit_addr} ${bitstream_image} && fpga loadb 0 ${loadbit_addr} ${filesize}/;load mmc 0 ${devicetree_load_address} ${devicetree_image}/;bootz ${kernel_load_address} - ${devicetree_load_address}

Hi , We are getting this error while running userwaveapp application on Z7, what is the configuration we are missing ? anything to be given in bootargs or system-user.dtsi for Z7 ? 4003c010 Address is related to a fpga reg for gpio ... fpga_rev7:/usr/bin$ sudo su fpga_rev7:/usr/bin# fpga_rev7:/usr/bin# userwaveapp ********************************* Opening Driver Device File Opened...!!! Occurrences replaced, and data stored in the output text file suc8<--- cut here --- cessfully. Unable to handle kernel paging request at virtual address 4003c010 [4003c010] *pgd=00000000 Internal error: Oops - BUG: 5 [#1] PREEMPT SMP ARM Modules linked in: gpiomodule(O) uio_pdrv_genirq CPU: 1 PID: 585 Comm: userwaveapp Tainted: G O 6.1.5-xilinx-v2023.1 #1 Hardware name: Xilinx Zynq Platform PC is at etx_ioctl+0x1bc/0x358 [gpiomodule] LR is at 0x40000000 pc : [<bf01430c>] lr : [<40000000>] psr: 600f0013 sp : f0c55ca0 ip : 0000001c fp : 004422d8 r10: c1a313c0 r9 : 00000003 r8 : c11c8180 r7 : 80044d01 r6 : 00440018 r5 : bf016000 r4 : 00440018 r3 : 4003c010 r2 : 00000000 r1 : bf0160f4 r0 : 00000000 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none Control: 18c5387d Table: 01eac04a DAC: 00000051 Register r0 information: NULL pointer Register r1 information: 4-page vmalloc region starting at 0xbf014000 allocated at load_module+0x9fc/0x1748 Register r2 information: NULL pointer Register r3 information: non-paged memory Register r4 information: non-paged memory Register r5 information: 4-page vmalloc region starting at 0xbf014000 allocated at load_module+0x9fc/0x1748 Register r6 information: non-paged memory Register r7 information: non-paged memory Register r8 information: slab task_struct start c11c8180 pointer offset 0 Register r9 information: non-paged memory Register r10 information: slab filp start c1a313c0 pointer offset 0 Register r11 information: non-paged memory Register r12 information: non-paged memory Process userwaveapp (pid: 585, stack limit = 0x265e9ecc) Stack: (0xf0c55ca0 to 0xf0c56000) 5ca0: 00000008 c022abd4 00000000 00000000 00000000 00000000 00000000 00000000 5cc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5ce0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5d00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5d20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5d40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5d60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5d80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5da0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5dc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5de0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5e00: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5e20: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5e40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5e60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5e80: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5ea0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5ec0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5ee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 5f00: 00000000 31f6c4ec c1a50110 c1a313c0 00440018 80044d01 c11c8180 c020803c 5f20: c1a50110 c0208b44 00000000 00000000 c1a300c0 00000000 00000000 00000000 5f40: 00000000 00000000 00000000 00004004 00000000 00000000 f0c55f6c 31f6c4ec 5f60: c1a300c0 00441190 c1a300c0 00000000 c1a300c0 00000000 00000000 31f6c4ec 5f80: c01002c4 00440018 00442198 00420e48 00000036 c01002c4 c11c8180 00000036 5fa0: 004422d8 c0100060 00440018 00442198 00000003 80044d01 00440018 bef6b500 5fc0: 00440018 00442198 00420e48 00000036 00000001 00000003 bef6b550 004422d8 5fe0: 00000036 bef6b4e8 b6e56d25 b6dce576 600f0030 00000003 00000000 00000000 etx_ioctl [gpiomodule] from vfs_ioctl+0x20/0x38 vfs_ioctl from sys_ioctl+0x298/0x95c sys_ioctl from ret_fast_syscall+0x0/0x54 Exception stack(0xf0c55fa8 to 0xf0c55ff0) 5fa0: 00440018 00442198 00000003 80044d01 00440018 bef6b500 5fc0: 00440018 00442198 00420e48 00000036 00000001 00000003 bef6b550 004422d8 5fe0: 00000036 bef6b4e8 b6e56d25 b6dce576 Code: e59d2008 e583200c e59f5170 e59530f8 (e5933000) ---[ end trace 0000000000000000 ]--- Device File Closed...!!! Segmentation fault fpga_rev7:/usr/bin# Regards, Mani

Thanks Lonel

How to transfer files to Z7 board on network via tftp/sftp? what configurations have to be done on petalinux to enable remote file transfer to Z7 board from a remote ubuntu pc. Any reference to the steps which have to be followed?

can we follow a single file boot procedure like this. This command petalinux-package --wic generates petalinux-sdimage.wic file and its used in the following command to flash sdcard. Is this step ok for flashing sdcard and booting petalinux on Z7? Sudo dd if=petalinux-sdimage.wic of=/dev/sd<X> conv=fsync

Hi Arthur, We built the petalinux image for Z7 and we are not finding decutil/dpmutil utility, when we try to run it on shell. Can you please let us know how to add this tool in our build , dpmutil is the latest version ? how to add it in our image.

how to add decutil command support in petalinux build.

From the link https://digilent.com/reference/programmable-logic/eclypse-z7/reference-manual#microsd_boot_mode Are there any steps for booting petalinux image via SD card on Eclypse Z7

Thanks Lonel

Any suggestions on this issue? anything to do with sda clk for axi_iic_0?

We have created a new qspi IP on AXI, is there any documents to refer on how to add and link our developed driver code to our IP on axi bus .?

Thanks Lonel, Following are the contents of our hw design captured in the files "pl.dtsi" and "system-conf.dtsi" , Seems matching with the link description, But not sure what is missing for not detecting axi_i2c bus on qemu, Anything wrong with these 2 file contents ? somthing like m24C80@50 is missing for axi i2c, no device added yet could be the reason for issue ? Is XSA file is a issue here ? In pl.dtsi <petalinux project directory>/components/plnx_workspace/device-tree/device-tree/pl.dtsi axi_iic_0: i2c@40020000 { #address-cells = <1>; #size-cells = <0>; clock-names = "s_axi_aclk"; clocks = <&clkc 15>; compatible = "xlnx,axi-iic-2.1", "xlnx,xps-iic-2.00.a"; interrupt-names = "iic2intc_irpt"; interrupt-parent = <&intc>; interrupts = <0 30 4>; reg = <0x40020000 0x10000>; }; In <petalinux project directory>/project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi /include/ "system-conf.dtsi" / { }; &axi_iic_0{ clock-frequency = <400000>; status = "okay"; }; Is clock frequency ok? changed it to 100000, then too same issue. When we do dtc -I fs /sys/firmware/devicetree/base/ amba_pl { compatible = "simple-bus"; ranges; #address-cells = <0x01>; #size-cells = <0x01>; phandle = <0x36>; i2c@40020000 { compatible = "xlnx,axi-iic-2.1\0xlnx,xps-iic-2.00.a"; clocks = <0x01 0x0f>; clock-names = "s_axi_aclk"; status = "okay"; interrupt-parent = <0x04>; #address-cells = <0x01>; interrupts = <0x00 0x1e 0x04>; #size-cells = <0x00>; phandle = <0x38>; reg = <0x40020000 0x10000>; clock-frequency = <0x61a80>; interrupt-names = "iic2intc_irpt"; }; followed online link also related to it, also not helping MicroZed Chronicles: PetaLinux I2C in the PS and AXI IIC (adiuvoengineering.com)