- Openamp-system-reference - lists.openampproject.org

Calling for agenda: 10/27 OpenAMP System Reference call

by Nathalie Chan King Choy

Hi all, Please let me know if you have additional agenda topics: Here's what I have so far: * Individual updates * Did anything interesting come out of OpenAMP System Reference presentation to LEDGE HPP group? * Any updates on recruiting TI or NXP to System Reference working group? * What to shoot to accomplish before next Wednesday's call? Reminder of action items from last time: * (In progress?) Tanmay: Check w/ Yocto team about "K26" vs "KV260" * Tanmay: Set autoboot to no & see if DHCP gets an IP address * (DONE) Nathalie: Find out if we document that info someplace (SOM schematic won't be published, just carrier card) * Tanmay: There is user guide on how to create boot.bin. Will find it & send out. * (DONE) Paul: Send link to wiki page Thanks & regards, Nathalie

3 years, 2 months

1
0
0 0

Changes to Zephyr SDK to run Xilinx zcu102 QEMU images

by Paul Sokolovsky

Hello, As I mentioned during last week's sync, I submitted changes to Zephyr SDK to update/extend its Xilinx QEMU coverage to allow to run end-to-end OpenAMP images (as produced by OE/PetaLinux). Associated instructions are at https://github.com/pfalcon/openamp-system-reference/wiki/RunningXilinxOEWit… . The changes will go into the next Zephyr SDK release. -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

3 years, 2 months

1
0
0 0

Xilinx BOOT.BIN with bif file Generation documents

by Tanmay Shah

Hi Bill, Following documents / User Guide can help to understand how BOOT.BIN is generated. 1. Petalinux Tools Userguide: https://www.xilinx.com/content/dam/xilinx/support/documentation/sw_manuals/… * Page – 31 explains how to generat BOOT.BIN using petalinux (petalinux-package tool) * Internally it should be using bootgen utility 2. Bootgen userguide : https://www.xilinx.com/content/dam/xilinx/support/documentation/sw_manuals/… * This user guide explains whole bif (boot image format) file format (Page – 45) * It also explains how to use bootgen command. i. In general I use something like following to generat BOOT.BIN: bootgen -arch <platform name> -image boot.bif -w -o BOOT.BIN Platform name could be: zynq, zynqmp or versal We mention all the images’ path in bif file, i.e. fsbl, ATF, u-boot etc.. and bootgen can combine them all in one BOOT.BIN file and we can use that BOOT.BIN to boot to u-boot. In Yocto this is taken care by Vitis xsct tool. So we don’t have to generate it manually. Thanks, Tanmay Shah tanmay.shah(a)xilinx.com<mailto:tanmay.shah@xilinx.com> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

3 years, 2 months

1
0
0 0

Xilinx build: Requirement for power-of-2 SD card image size

by Paul Sokolovsky

Hello, Looking thru notes from the last meeting, I see that Bill noted a need to manually resize a Xilinx SD card image after the build as "pain point". I looked into it, and found a workaround on how to build an image of proper size right away: --- a/meta-xilinx-bsp/classes/image-types-xilinx-qemu.bbclass +++ b/meta-xilinx-bsp/classes/image-types-xilinx-qemu.bbclass @@ -6,5 +6,5 @@ # 512K). CONVERSIONTYPES_append = " qemu-sd" -CONVERSION_CMD_qemu-sd = "cp ${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type} ${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type}.qemu-sd; truncate -s %512K ${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type}.qemu-sd" +CONVERSION_CMD_qemu-sd = "cp ${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type} ${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type}.qemu-sd; truncate -s %256M ${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.${type}.qemu-sd" CONVERSION_DEPENDS_qemu-sd = "coreutils-native" Interesting, that comment on that file says: # Define the 'qemu-sd' conversion type # # This conversion type pads any image to the 512K boundary to ensure that the # image file can be used directly with QEMU's SD emulation which requires the # block device to match that of valid SD card sizes (which are multiples of # 512K). As can be seen, the care was taken to pad the SD card image already, but seems that QEMU requirements got changed after that. And my change is indeed just a workaround, as it makes the image be padded to 256MB, which works as intended up to 512MB of the image size (and not practical for small images either). A quick googling up led me to https://support.xilinx.com/s/article/76596 which says: > A check has been introduced in QEMU to see if image size is power of > 2. So, I assume it's a recent addition to Xilinx QEMU, though I didn't check the sources. -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

3 years, 2 months

3
3
0 0

Cross-linked Google Docs from Github Wiki

by Paul Sokolovsky

Hello, Coming back from vacation, I find myself in having a bit of trouble getting back to various previous instructions/docs which were posted. We seem to have 2 disjoint documentation repositories - one at Github wiki, https://github.com/OpenAMP/openamp-system-reference/wiki , one at Google Drive. So, I took care to cross-link gdrive folders/docs from the main wiki. I'm not sure if the split is intentional, e.g. if Google Drive contains information which shouldn't be public. If so, please redact my changes as needed. Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

3 years, 2 months

3
2
0 0

Calling for agenda: 9/29 OpenAMP System Reference call

by Nathalie Chan King Choy

Hi all, Hopefully everyone received the updated calendar invitation, pushing out by 1hr to avoid conflict with the Zephyr TSC weekly. Please let me know if you have additional agenda topics. Here's what I've got so far: * Individual updates * If Bill has a chance to look at ST instructions, perhaps more in-depth discussion here. * Any discussion points from Bill's notes on Tanmay's build steps (no changes required)? * <Does Etsam have proposal for what to work on & dependencies?> * What to shoot to accomplish before next Wednesday's call? Just in case your calendar invitation is missing, you can use this link on 9/29 at 9am Pacific Time: Join Zoom Meeting<https://xilinx.zoom.us/j/95281364886?pwd=U2dBN3RORmVyU3owb1lzd3BIcUREdz09&f…> Thanks & regards, Nathalie

3 years, 3 months

1
0
0 0

2021-09-24 - OpenAMP System Reference notes and action items

by Nathalie Chan King Choy

Hi all, Here are the notes from today: https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref… Here is the link to the recording: https://xilinx.zoom.us/rec/share/IBTK9JjWIj4Y0T62iuMM1i7FaMzwiJRtJbocF9fZTa… Passcode: 3STWD!Z4 Action item for all: * All: Please review & tweak the checklist before we turn it into a 2-D table: https://docs.google.com/document/d/1Y3fpQV8A9CQD1ye5YYX4Gyi80f1VTHo892zJv64… Thanks & talk to you on Wednesday next week, Nathalie

3 years, 3 months

1
0
0 0

Mailing list subscription test

by arnaud pouliquen

Hello, Sorry for the pollution, just a test to check if I'm now able to receive mail from the mailing list with my st.com email Regards, Arnaud

3 years, 3 months

1
0
0 0

Calling for agenda: 9/24 OpenAMP System Reference weekly

by Nathalie Chan King Choy

Hi all, This week we keep the Friday slot, then move to the new day/time next week. Please let me know your agenda items. Here's what I collected so far: * Individual updates * Since Bill will be looking at ST instructions, perhaps more in-depth discussion here. * Any discussion points from Bill's notes on Tanmay's build steps (no changes required)? * <Does Etsam have proposal for what to work on & dependencies?> * What to shoot to accomplish before next Wednesday's call? Just in case your calendar invitation is missing, you can use this link on Friday 9/24: Join Zoom Meeting<https://xilinx.zoom.us/j/94831165744?pwd=UzVRYmZVenhCekwyMlZPMFhGV3NiUT09&f…> Thanks & regards, Nathalie

3 years, 3 months

1
0
0 0

FW: OpenAMP High-level plan for Xilinx Software Stack

by Tanmay Shah

Finally to correct mailing list Email ID. Thanks, Tanmay Shah tanmay.shah(a)xilinx.com<mailto:tanmay.shah@xilinx.com> From: Tanmay Shah <tanmays(a)xilinx.com> Date: Friday, September 10, 2021 at 8:10 AM To: Openamp-system-reference <openamp-system-reference-bounces(a)lists.openampproject.org> Cc: Nathalie Chan King Choy <nathalie(a)xilinx.com> Subject: FW: OpenAMP High-level plan for Xilinx Software Stack Forward again. Thanks, Tanmay Shah tanmay.shah(a)xilinx.com<mailto:tanmay.shah@xilinx.com> From: Tanmay Shah <tanmays(a)xilinx.com> Date: Friday, September 3, 2021 at 3:29 PM To: Openamp-system-reference <openamp-system-reference-bounces(a)lists.openampproject.org> Cc: Arun Balaji Kannan <arunbala(a)xilinx.com> Subject: OpenAMP High-level plan for Xilinx Software Stack Hello All, Following is proposal of high-level plan with respect to end to end example development. 1. QEMU & initial doc – Mid Sept. 2. Userspace & kernel space demos – Sept end 3. Hardware demo – End - Oct. 4. Decoupling flow (Without using Xilinx tools) – End-Nov 5. Advanced app – End-Jan 6. Completely upstream flow – (Based on When Xilinx driver is merged in upstream kernel) Thanks, Tanmay Shah tanmay.shah(a)xilinx.com<mailto:tanmay.shah@xilinx.com> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

3 years, 3 months

1
0
0 0

2024

2023

2022

2021

Openamp-system-reference