01-03-2019 05:53 AM
We want to boot r5 after uboot or linux started,but we failed with calling XPm_InitXilpm.
We use mpsoc's a53 and r5. Running uboot in a53 and load bitstream in uboot. Copy r5 core0's image to 0x78000000 in ddr. Then a53 tell r5 core1 to power up rr core0 via shared memory. R5 core1 call XPm_InitXilpm to powerup r5 core0,but fails, r5 just print R"PU0: XPm_RequestWakeUp(7, 78000001, 2, 0, 0)".
What's the reason that fails bootup r5 core0? and how to achive this goal?
01-08-2019 01:38 AM - edited 01-08-2019 02:04 AM
Address 0xffd8xxxx is writable , and as soon as I read (like 0xffd80118) mpsoc restarts.
Though it's wo, but read will cause reset?
01-08-2019 10:26 AM
Did you take a look at Xilinx OpenAMP solution? I suggest to find an example that fits your needs on Xilinx wiki or Xilinx docs and start from there.
01-10-2019 10:46 AM
If you want to load the R5 application from BOOT.bin then it's a matter of formatting the .bif properly and FSBL will take care of the loading.
If you want to load the R5 application after Linux start execution, Xilinx strongly recommend to use out tested solution (openAMP).
01-11-2019 01:02 AM
so ther is no way to boot r5 after fsbl (like in uboot ,in linux )without openamp ?
And what commands can start r5?
01-16-2019 03:38 PM
Is possible but you are going to re-invent the wheel. I still think you should be using openAMP but maybe somebody else in the community might be able to help you.