cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Adventurer
Adventurer
1,278 Views
Registered: ‎05-24-2018

OpenAMP on ZU+

Jump to solution

How to let quad-core A53 run independently and R5 run RTOS using OpenAMP on ZU+?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
1,360 Views
Registered: ‎05-10-2017

Looks like there is a mistake in the user guide. This is documented correctly in the wiki.

http://www.wiki.xilinx.com/OpenAMP+2017.3

 

Please use these commands below

 

ZynqMP> mmcinfo && fatload mmc 0 ${netstart} ${kernel_img} &&  fatload mmc 0 0x14000000 openamp.dtb
Device: sdhci@ff170000
...
reading image.ub
31514140 bytes read in 2063 ms (14.6 MiB/s)
reading openamp.dtb
38320 bytes read in 18 ms (2 MiB/s)
ZynqMP> bootm $netstart $netstart 0x14000000

 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

0 Kudos
3 Replies
Highlighted
Moderator
Moderator
1,241 Views
Registered: ‎05-10-2017

Please take a look at the examples provided in the OpenAMP wiki http://www.wiki.xilinx.com/OpenAMP+2018.1 and in the OpenAMP user guide http://www.wiki.xilinx.com/OpenAMP+2018.1

 

The examples have linux running on A53 cores and R5 remote (can be configured for either baremetal or freertos applications)

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Highlighted
Adventurer
Adventurer
1,210 Views
Registered: ‎05-24-2018

I created  a petalinux's project using xilinx-zcu102-2017.3.bsp and copy those 3 files(BOOT.BIN image.ub openamp.dtb) to my sd card from /pre-built/linux/imagesaccording to UG1186. Then u-boot, after "ZynqMP> bootm $netstart - $netstart 0x14000000", it shows 

[    4.940253] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6

[    4.947672] Please append a correct "root=" boot option; here are the available partitions:

[    4.955997] 0100           65536 ram0

[    4.955999]  (driver?)

[    4.962065] 0101           65536 ram1

[    4.962066]  (driver?)

[    4.968137] 0102           65536 ram2

[    4.968139]  (driver?)

[    4.974217] 0103           65536 ram3

[    4.974219]  (driver?)

[    4.980294] 0104           65536 ram4

[    4.980295]  (driver?)

[    4.986371] 0105           65536 ram5

[    4.986372]  (driver?)

[    4.992447] 0106           65536 ram6

[    4.992448]  (driver?)

[    4.998524] 0107           65536 ram7

[    4.998525]  (driver?)

[    5.004600] 0108           65536 ram8

[    5.004602]  (driver?)

[    5.010673] 0109           65536 ram9

[    5.010675]  (driver?)

[    5.016754] 010a           65536 ram10

[    5.016756]  (driver?)

[    5.022913] 010b           65536 ram11

[    5.022915]  (driver?)

[    5.029081] 010c           65536 ram12

[    5.029082]  (driver?)

[    5.035240] 010d           65536 ram13

[    5.035242]  (driver?)

[    5.041407] 010e           65536 ram14

[    5.041409]  (driver?)

[    5.047567] 010f           65536 ram15

[    5.047568]  (driver?)

[    5.053738] 1f00           30720 mtdblock0

[    5.053740]  (driver?)

[    5.060241] 1f01             256 mtdblock1

[    5.060243]  (driver?)

[    5.066752] 1f02           36864 mtdblock2

[    5.066754]  (driver?)

[    5.073266] 1f03           63232 mtdblock3

[    5.073268]  (driver?)

[    5.079773] b300        15558144 mmcblk0

[    5.079775]  driver: mmcblk

[    5.086548]   b301          512000 mmcblk0p1 91141cd5-01

[    5.086550]

[    5.093319]   b302        15045120 mmcblk0p2 91141cd5-02

[    5.093320]

[    5.100086] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

[    5.108337] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.14.0-xilinx-v2018.2 #1

[    5.115539] Hardware name: ZynqMP ZCU102 Rev1.0 (DT)

[    5.120485] Call trace:

[    5.122923] [<ffffff8008088c58>] dump_backtrace+0x0/0x368

[    5.128301] [<ffffff8008088fd4>] show_stack+0x14/0x20

[    5.133336] [<ffffff8008a13b78>] dump_stack+0x9c/0xbc

[    5.138371] [<ffffff800809bdc0>] panic+0x11c/0x274

[    5.143146] [<ffffff8008d61124>] mount_block_root+0x1a8/0x27c

[    5.148874] [<ffffff8008d61430>] mount_root+0x11c/0x134

[    5.154082] [<ffffff8008d615b4>] prepare_namespace+0x16c/0x1b4

[    5.159899] [<ffffff8008d60d44>] kernel_init_freeable+0x1b8/0x1d8

[    5.165976] [<ffffff8008a25ee0>] kernel_init+0x10/0x100

[    5.171183] [<ffffff8008084a90>] ret_from_fork+0x10/0x18

[    5.176478] SMP: stopping secondary CPUs

[    5.180384] Kernel Offset: disabled

[    5.183855] CPU features: 0x002004

[    5.187240] Memory Limit: none

[    5.190282] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

0 Kudos
Highlighted
Moderator
Moderator
1,361 Views
Registered: ‎05-10-2017

Looks like there is a mistake in the user guide. This is documented correctly in the wiki.

http://www.wiki.xilinx.com/OpenAMP+2017.3

 

Please use these commands below

 

ZynqMP> mmcinfo && fatload mmc 0 ${netstart} ${kernel_img} &&  fatload mmc 0 0x14000000 openamp.dtb
Device: sdhci@ff170000
...
reading image.ub
31514140 bytes read in 2063 ms (14.6 MiB/s)
reading openamp.dtb
38320 bytes read in 18 ms (2 MiB/s)
ZynqMP> bootm $netstart $netstart 0x14000000

 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

0 Kudos