software-dl.ti.com/.../demo_mode_switch_top.html

Known Issues

1. When switching from MCU ONLY mode back to ACTIVE mode, currently loading of firmares on the MAIN domain cores is not supported.

Does the article mean that the main domain system cannot be started? For example, Linux kernel, etc. Only mcu mode is incomplete. Is there any solution on how to solve this problem?

We must check with the dev team and get back on this. Since it is the holiday season, please expect a delay till the new year.

Thanks.

When I tried to run the only mcu demo following the documentation, I encountered three errors.I tried fixing the errors myself but it didn't resolve all the errors

1、/home/edward/workspace/TDA4/ipc/ti-processor-sdk-rtos-j721e-evm-09_02_00_05/pdk_jacinto_09_02_00_30/packages/ti/build/makerules/common.mk:365: *** gcc-arm compiler not found. Please refer user guide to download the same. Stop.
fix:
common.mk 265line
else
#$(error gcc-arm compiler not found. Please refer user guide to download the same)
SBL_OBJ_COPY?=aarch64-linux-gnu-objcopy #add it
endif

2、boot.c:967:46: error: incompatible function pointer types passing 'void (*)(void)' to parameter of type 'TaskP_Fxn' (aka 'void (*)(void *, void *)') [-Werror,-Wincompatible-function-pointer-types]
bistTask = TaskP_create(&bist_TaskFxn, &bistParams);
fix:
int bist.c
void bist_TaskFxn(SemaphoreP_Handle bistSemHandle, void* arg2) //add it void* arg2
{

}

int bist.h
void bist_TaskFxn(void); --> void bist_TaskFxn(void*, void*);

3、make[2]: *** No rule to make target 'mcu_only_app.c', needed by '/home/edward/workspace/TDA4/ipc/ti-processor-sdk-rtos-j721e-evm-09_02_00_05/mcusw/binary/can_boot_app_mcu_rtos/obj/j721e_evm/mcu1_0/release/mcu_only_app.oer5f'. Stop.
make[2]: *** Waiting for unfinished jobs....

I cannot find mcu_only_app.c file in RTOS SDK!

Is the only mcu not maintained for a long time?

Hi Wang Tao

   what application will you want?

    please refer to following e2e case about low power mode:

     (+) J721EXSOMXEVM: PDK Low Power Manager Demo Linux Boot Errors - Processors forum - Processors - TI E2E support forums

Regards

   Semon

I want to use lpm(only mcu) demo.I use SDK-RTOS-J721E-EVM-09_02_00_05.I refer to the following documents:

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_mode_switch_top.html

1、Is there any problem with LPM version 09_02_00_05?Because I see that the link you sent is PDK 10.00_00.

2、Because you fixed some bugs in lpm in PDK10_00_00, I may start verification using version 10.0 next.

3、“currently loading of firmares on the MAIN domain cores is not supported“. May I ask when we plan to support this?

I use PDK10, 

make -s -j can_boot_app_mcu_rtos BOARD=j721e_evm SOC=j721e BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos

 I encountered some errors,

As mentioned above the three compilation issues.

This is the fourth compilation problem

boot.c:930:30: error: too few arguments to function call, expected 2, have 1
 SBL_ospiInit(&boardHandle);

It's obviously some grammatical issues，Why does the SDK have so many compilation issues?Please tell me how to solve these problems one by one

Can you tell us why are building can_boot_app_mcu_rtos for lpm?

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_mode_switch_top.html

The link says it needs to be built like this：

Build Instructions

This application is part of Boot App and is disabled by default and requires to be enabled.

Enabling the application

• In file (MCUSW Install Dir)/mcuss_demos/boot_app_mcu_rtos/makefile
• The MCUONLYFUNC controls enabling/disabling of this application
• Set MCUONLYFUNC to enabled i.e. MCUONLYFUNC ?= enabled

Building

Follow the instructions specified in Boot App - Build Instructions

Hi,

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1427180/j721exsomxevm-pdk-low-power-manager-demo-linux-boot-errors/5487056#5487056

I have got MCU_ONLY mode working on 10.0 SDK. Can you try the above link?

- Keerthy

Thank you, I am reading these articles

1.

cd $SDK_Linux
make linux-dtbs -j8

2..

/constructappimageshlos.sh Generating atf_optee image

aarch64-linux-gnu-ld: cannot find base-board.dtb: No such file or directory
aarch64-linux-gnu-ld: cannot find base-board.dtb: No such file or directory

What is the reason for this?

You need to copy the k3-j721e-common-proc-board.dtb as base-board.dtb.

- Keerthy

constructappimageshlos.sh say:# base-board.dtb (k3-j72*-common-proc-board.dtb), and Image files

fix:

cp k3-j721e-common-proc-board.dtb base-board.dtb

Compiling again can pass.


but，I encountered a new problem。
when I don't use k3-j721e-common-proc-board.patch。

Linux can start normally. But after Linux starts, the uart of R5 will be garbled.as follows：

Loading BootImage
BootImage completed, status = 0
Sciclient_procBootReleaseProcessor, ProcId 0x20...
Sleeping for 20 seconds after the last stage
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒


then， I use k3-j721e-common-proc-board.patch,
Linux cannot start normall.The log stays here

[ 13.279134] j721e-pcie 2910000.pcie: MEM 0x0018011000..0x001fffffff -> 0x0018011000
[ 13.299245] j721e-pcie 2910000.pcie: IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[ 13.308378] platform 2920000.pcie: deferred probe pending
[ 13.314393] platform 2900000.pcie: deferred probe pending
[ 13.319982] platform 2910000.pcie: deferred probe pending

The R5 core still has the same phenomenon, garbled characters appear.

My questions are as follows:

1.
cp k3-j721e-common-proc-board.dtb base-board.dtb。Is this the correct solution?

2.

k3-j721e-common-proc-board.patch：

Does it mean to use the SD card rootfs partition as the file system?

3、

How to solve the problem that Linux cannot start and R5 uart is garbled

Wang Tao said:

cp k3-j721e-common-proc-board.dtb base-board.dtb。Is this the correct solution?

This is the k3-j721e-common-proc-board.dtb that you generated after applying the 

k3-j721e-common-proc-board.patch right?

Wang Tao said:

Does it mean to use the SD card rootfs partition as the file system?

Correct.

Wang Tao said:

How to solve the problem that Linux cannot start and R5 uart is garbled

Even after applying the

k3-j721e-common-proc-board.patch?

 &mcu_uart0 {
- status = "okay";
+ status = "disabled";
 pinctrl-names = "default";
 pinctrl-0 = <&mcu_uart0_pins_default>;

The above should help with MCU UART issue. Just double check with k3-j721e-common-proc-board.dtb is being used.

- Keerthy

It's a problem with my operation. Everything is working fine now, thanks. 
I would like to know when suspend to ram is planned to be supported?