Other Parts Discussed in Thread: SYSBIOS
Hi,
While my own application build successfully with some changes in linker but when I tried to run it, the application stuck along with the Linux Kernel.
Linux log where it got stuck -->
/*******************************************
U-Boot SPL 2020.01-dirty (May 15 2022 - 12:47:56 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.1.1--v2021.01a (Terrific Lla')
Reading on-board EEPROM at 0x50 failed -1
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default envt
Starting ATF on ARM64 core...
NOTICE: BL31: v2.4(release):07.03.00.005-dirty
NOTICE: BL31: Built : 00:15:40, Apr 10 2021
********************************************/
In a scenario where we aren't using Linux SPL-Boot the application boots and works fine but while with SPL-Boot the BIOS_Start() function doesn't let the application run its course.
Function related to sysbios lead to kernel stuck situation.
Here, without using sysbios function would interrupt the concurrency, since there won't be task formation, we want among the tasks.
Can you specify how this should be resolved ??
Does removing Sysbios functions make the it a non-RTOS application running along Linux ??
Regards,
Tanvi