HI Bill, This is my first day back in the office since the 12/19 call, and I'm digging myself out from under a mountain of email.

I'm sending the build instructions to the list in a separate email.

Further replies inline:

-----Original Message----- From: William Mills wmills@ti.com Sent: Friday, December 27, 2019 3:34 PM To: Ed T. Mooring emooring@xilinx.com; openamp- rp@lists.openampproject.org Subject: Re: [Openamp-rp] QEMU Docker Container README

Hi Ed,

On the 12/19 call you said you had build instructions for the R5 that you had sent to the LITE group. You took an action item to post them here as well. Can you do that please? It would be very helpful.

More comments below...

On 11/25/19 8:47 PM, Ed Mooring via Openamp-rp wrote:

...

Here is the README for the Docker Container discussed in today's call: # Running the container:

docker run -it xilinx-qemu

You had previously said to use the image named: edmooring/qemu:xilinx-qemu

That's an error in my instructions. I'm guessing it didn't get caught because the other folks all did a "docker pull" on the right image name first.

I tried running as you had it above (just xilinx-qemu) and it did not find the image. The old name still works but has not been updated in 8 weeks.

Am I missing something? Have you published a new docker image somewhere I can't find?

I put edmooring/qemu:xilinx-qemu2 up about a month ago. It takes a URL for an SD image file as an argument and uses that to boot. This is what the build instructions I sent are bout.

...

This boots a Linux image (with ramdisk) and a device tree. The image contains the OpenAMP demo firmware images and examples.

Alternatively,

docker run -it -v <path_to_tftpboot_directory>:/tftpboot xilinx-qemu

adds <path_to_tftpboot_directory> on the host system as /tftpboot inside the container, allowing a user to fetch arbitrary files, including Linux executables and firmware images, from within the container.

# Running the OpenAMP echo test example

• Log in to the emulated Linux as root (password is also "root").
• Set up the R5 firmware: echo image_echo_test

/sys/class/remoteproc/remoteproc0/firmware

• Start the R5: echo start >/sys/class/remoteproc/remoteproc0/state
• Run the example: echo_test

Thanks for this. I have tested it myself and added it to the wiki.

...

# Random notes:

The version of QEMU that this uses is built from the xilinx-v2019.1 tag on GitHub for Debian Stretch. Debian Stretch was chosen for the base of this container because Linaro uses it extensively and this way the executables are compatible across the various Linaro containers.

Thanks, Bill

Regards, Ed M