-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PL memory blocks doesnot work #21
Comments
Hi Muhammed, Which of the demos are you trying to launch? If it is the zynq_demo this blog by Rick Wertenbroek contains a script with commands on how to create the hardware dtb: generate_qemu_device_tree_zynq7.sh using petalinux commands. For the ZynqMP/Versal demos the hardware cosim dts to use when launching QEMU are found in the qemu-devicetrees repository (meanning that you don't need to build one by your own). My command lines for launching the zynq_demo are found below (where I renamed the petalinux built system.dtb using the commands from the script, and containing remote-port connections, to system-cosim.dtb):
Best regards, |
Hi Francis, Is it ok to try the petalinux flow command ? petalinux-boot --qemu --kernel --qemu-args " -hw-dtb ./qemu_cosim/qemu_hw_system.dtb -machine-path ./qemu_cosim -icount 1 -sync-quantum 10000" Here this dtb was created by Ricks script . |
Hi again Muhammed, The answers is yes to both questions, you need to use zynq-pl-remoteport.dtsi (this file contains the remote-port descriptions that will make QEMU create connections to SystemC), and it is ok to run it through the petalinux command as you mention above. From the Linux command line you can try below that will hit the debugdev and output a trace print.
Best regards, |
I tried to implement the whole tutorial with following steps. So far I was been able to connect the petalinux qemu with system c socket and I can boot the os in linux.
But I couldnot read the values of the IPs that was included in the hardware design by calling devmem command.
Could you guide me on emulating PL side ?
This was my pl.dtsi contents of the petalinux project : This memory addresses is giving wrong values in emulation.
/*
*/
/ {
amba_pl: amba_pl {
#address-cells = <1>;
#size-cells = <1>;
compatible = "simple-bus";
ranges ;
apb_wrapper_policy_s_0: apb_wrapper_policy_server@43c00000 {
compatible = "xlnx,apb-wrapper-policy-server-1.0";
reg = <0x43c00000 0x10000>;
};
apb_wrapper_puf_0: apb_wrapper_puf@43c10000 {
compatible = "xlnx,apb-wrapper-puf-1.0";
reg = <0x43c10000 0x10000>;
};
apb_wrapper_rsa_0: apb_wrapper_rsa@43c20000 {
compatible = "xlnx,apb-wrapper-rsa-1.0";
reg = <0x43c20000 0x10000>;
};
apb_wrapper_trng_0: apb_wrapper_trng@43c30000 {
compatible = "xlnx,apb-wrapper-trng-1.0";
reg = <0x43c30000 0x10000>;
};
};
};
My question is if export the a soc design with several IP block and create a custom petalinux project, can I read the values of this PL side ?
The text was updated successfully, but these errors were encountered: