bare metal app
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: bare metal app
I've adapted the instructions from this article to Red Pitaya.
I now have zynq_remoteproc loading app_cpu1.elf and starting CPU1.
You can find my instructions at the following location:
https://github.com/pavel-demin/red-pita ... metal_test
I now have zynq_remoteproc loading app_cpu1.elf and starting CPU1.
You can find my instructions at the following location:
https://github.com/pavel-demin/red-pita ... metal_test
-
- Posts: 23
- Joined: Mon Jun 15, 2015 8:02 pm
Re: bare metal app
Really good work.
Will it also work with make NAME=red_pitaya_0_92 all ?
Did you figure out why linux starts with both cores? I try to update to kernel 4.0.
Will it also work with make NAME=red_pitaya_0_92 all ?
Did you figure out why linux starts with both cores? I try to update to kernel 4.0.
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: bare metal app
It should.Mike1010 wrote: Will it also work with make NAME=red_pitaya_0_92 all ?
No. The zynq_remoteproc driver stops and starts CPU cores when needed.Mike1010 wrote: Did you figure out why linux starts with both cores? I try to update to kernel 4.0.
-
- Posts: 23
- Joined: Mon Jun 15, 2015 8:02 pm
Re: bare metal app
ok.
The structs in file app_cpu1.c resource_table, fw_resource_type, fw_rsc_carveout, rproc_resource and the ams_vectors.S, boot.S, xtime_1.c patch file are all for the remoteproc driver?
i will try to see if changing to linux kernel 4.0 helps.
what will happen if cpu1_app.elf should be started on core1 but its blocked by linux (without your remoteproc approach)...it will not start and return no error?
The structs in file app_cpu1.c resource_table, fw_resource_type, fw_rsc_carveout, rproc_resource and the ams_vectors.S, boot.S, xtime_1.c patch file are all for the remoteproc driver?
i will try to see if changing to linux kernel 4.0 helps.
what will happen if cpu1_app.elf should be started on core1 but its blocked by linux (without your remoteproc approach)...it will not start and return no error?
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: bare metal app
Have you read this article that you and I referenced several times? It contains all the answers. I've even seen your comments at the end of this articleMike1010 wrote: The structs in file app_cpu1.c resource_table, fw_resource_type, fw_rsc_carveout, rproc_resource and the ams_vectors.S, boot.S, xtime_1.c patch file are all for the remoteproc driver?
The answer is "yes" for resource_table, fw_resource_type, fw_rsc_carveout, rproc_resource.
The answer is "no" for ams_vectors.S, boot.S, xtime_1.c patches. They are essential for app_cpu1.elf to run even without zynq_remoteproc driver. They can be found in both XAPP1078 and XAPP1079.
I don't know.Mike1010 wrote:what will happen if cpu1_app.elf should be started on core1 but its blocked by linux (without your remoteproc approach)...it will not start and return no error?
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: bare metal app
I've just replaced all the steps that required the SDK GUI with a couple of scripts. Now, all the steps can be done from the command line. I've updated the instructions accordingly.
-
- Posts: 23
- Joined: Mon Jun 15, 2015 8:02 pm
Re: bare metal app
Works great.
Just a note, what about the following warning?
Just a note, what about the following warning?
Code: Select all
root@red-pitaya:/home# tar --directory=/lib/modules/3.18.0-xilinx/kernel/drivers -zxf drivers.tgz
root@red-pitaya:/home# depmod
depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.builtin: No such file or directory
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: bare metal app
I don't think that these warnings are critical. modules.builtin and modules.order can be copied fromMike1010 wrote: Just a note, what about the following warning?Code: Select all
root@red-pitaya:/home# tar --directory=/lib/modules/3.18.0-xilinx/kernel/drivers -zxf drivers.tgz root@red-pitaya:/home# depmod depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/3.18.0-xilinx/modules.builtin: No such file or directory
Code: Select all
tmp/linux-xlnx-xilinx-v2015.1/modules.order
tmp/linux-xlnx-xilinx-v2015.1/modules.builtin
https://www.kernel.org/doc/Documentatio ... kbuild.txt
The following looks interesting:
I'll try to make zynq_remoteproc, remoteproc, virtio and virtio_ring as builtin and then install only modules.builtin and modules.order.modules.builtin
--------------------------------------------------
This file lists all modules that are built into the kernel. This is used
by modprobe to not fail when trying to load something builtin.
-
- Posts: 799
- Joined: Sat May 23, 2015 5:22 pm
Re: bare metal app
I tried but it didn't work. I've just added instructions on how to install the modules.builtin and modules.order files.pavel wrote:I'll try to make zynq_remoteproc, remoteproc, virtio and virtio_ring as builtin and then install only modules.builtin and modules.order.
-
- Posts: 54
- Joined: Wed Mar 11, 2015 3:07 pm
Re: bare metal app
hi pavel,
nice work. i found a bug in your makefile, https://github.com/pavel-demin/red-pita ... 1/Makefile:
should be:
are there other compilers available rather than arm-xilinx-eabi-gcc?
what does not work?
nice work. i found a bug in your makefile, https://github.com/pavel-demin/red-pita ... 1/Makefile:
Code: Select all
@$(CC) $(LDFLAGS) $(LIBRARIES) -o $@ $^
Code: Select all
@$(CC) $(LDFLAGS) -o $@ $^ $(LIBRARIES)
what does not work?
Last edited by Arnold on Wed Jun 24, 2015 10:04 am, edited 1 time in total.
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie
Who is online
Users browsing this forum: No registered users and 84 guests