SK-AM62: Facing Error while running FreeRTOS example while booting in Android

Hi Yash, 

Can you specify which m4f core you are talking about ?

There are three m4f cores as shown in the attachment below.

Regards,

Vaibhav

BLAZAR_Cortex_M4F_1 

Vaibhav is there any progress on it. If yes please let me know

Hi Yash,

The android sdk team will get back to you on your issue.

Regards,

Vaibhav

Hi Yash,

Can you provide complete step you do or which docs you use ?
 i will try to reproduce in my side .

in parallel i possible to have some issue link to security because android avec some restriction apply with selinux.
so you can try yo move in permissive and with this step: 

interrupt uboot boot and in uboot console do this command : 

setenv bootargs " androidboot.selinux=permissive "; saveenv;reset;

Hey Guillaume,

Thanks for your input. I'll try changing the u-boot variables.

The steps I followed are - 

1. Since I was successfully able to run FreeRTOS with linux by following the steps giving in MCU+ SDK User Manual. I ran the Hello World Example using CCS while A53 was booted with Linux. 

2. Now I wanted to do the same with Android. So, in the similar way I did all the cable connections and after the android successfully booted in A53 Cortex. I went to target configuration in CCS and selected my board ( as mentioned in MCU+ SDK User Manual ). After the debugging got over, I got the list of all available cores. Then I tried to connect to the BLAZAR M4F Cortex 1 but it failed to connect. It threw up the below error - 

Error connecting to the target:
(Error -1274 @ 0x0)
Error encountered during connect sequence. The specific reason is unknown but may be the result of trying to access a Core or logic that is inaccessible due to a lack of Power, Clocks, or Authentication (i.e. Security is preventing).
If blocked by security, and if supported, access may be allowed after following the Authentication process.
(Emulation package 9.11.0.00128)

3. The steps in the MCU+ SDK are for Linux only, there it was mentioned the SOC should be initialized and there were 2 ways of doing it, one using the python script the provided and second by running linux. So following the same I first tried doing SOC initialisation using the python script and then booted android and then after the successful android boot tried connecting to the M4 Core as mentioned above but the same error came up.

Please let me know if you need any other input. 

i will try to reproduce today your issue.

perhaps it's becasue we don't have in filesystem firmare for remoteproc driver m4f and r5 so you can try to put it in filesystem.

do this from your PC when android was booted: 

adb root
adb remount
adb push <path_to_m4f_firmawre> /vendor/firmware/ 
adb push <path_to_r5_firmawre> /vendor/firmware/ 

Thanks a lot Guillaume,

Will try this and let you know if I am able to get the M4 running up.

Regards,

Yash Teckchandani