imx6ull start kernel fail from op-tee

kk163 — Wed, 15 Dec 2021 03:33:43 GMT

Because the zImage size has increased, the FAT partition has been enlarged, so addr has been adjusted,

tee_addr=0x8b000000

fdt_addr=0x8a000000

Cause the kernel to fail to start ，if setenv tee =no kermel start succesfully

## Booting kernel from Legacy Image at 8b000000 ...
Image Name:
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1057044 Bytes = 1 MiB
Load Address: 84000000
Entry Point: 84000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 8a000000
Booting using the fdt blob at 0x8a000000
Loading Kernel Image
Using Device Tree in place at 8a000000, end 8a00bb93
Modify /soc/bus@2200000/epdc@228c000 disabled

why Load Address & Entry Point are still the original default value 84000000, instead of 8b000000. How to modify it?

Re: imx6ull start kernel fail from op-tee

kk163 — Wed, 15 Dec 2021 07:08:25 GMT

@Yuri ,please help! thank you!

Re: imx6ull start kernel fail from op-tee

Yuri — Fri, 17 Dec 2021 08:34:51 GMT

@kk163
Hello,

Have You used recommendations of Chapter 5 (Configuring OP-TEE) in i.MX Porting Guide?

https://www.nxp.com/docs/en/user-guide/IMX_PORTING_GUIDE.pdf

Regards,
Yuri.

Re: imx6ull start kernel fail from op-tee

kk163 — Tue, 04 Jan 2022 03:03:29 GMT

hi yuri
According to IMX_PORTING_GUIDE.pdf, I finally found the location of the modification, modified the entry point address and solved the problem!! thank you!!

git\core\arch\arm\plat-imx\conf.mk
# put optee at DDR base address + 64MB for AARCH32
#CFG_TZDRAM_START ?= ($(CFG_DRAM_BASE) + 0x04000000)
CFG_TZDRAM_START ?= ($(CFG_DRAM_BASE) + 0x0B000000)

However, if the reboot command is issued after modifying this entry point address , will the reboot fail? Why is this?

root@imx6ull14x14evk:~# reboot
root@imx6ull14x14evk:~# [ OK ] Removed slice system-modprobe.slice.
[ OK ] Stopped target Multi-User System.
[ OK ] Stopped target Login Prompts.
[ OK ] Stopped target Network.
[ OK ] Stopped target Host and Network Name Lookups.
[ OK ] Stopped target Remote File Systems.
[ OK ] Stopped target RPC Port Mapper.
[ OK ] Stopped target Sound Card.
[ OK ] Stopped target System Time Synchronized.
[ OK ] Stopped target System Time Set.
[ OK ] Stopped target Timers.
[ OK ] Stopped Daily Cleanup of Temporary Directories.
[ OK ] Stopped target Hardware activated USB gadget.
Stopping Save/Restore Sound Card State...
Stopping Avahi mDNS/DNS-SD Stack...
Stopping Kernel Logging Service...
Mar 24 10:27:55 imx6ull14x14evk syslog.info syslogd exiting
Stopping System Logging Service...
Stopping D-Bus System Message Bus...
Stopping Getty on tty1...
Stopping Telephony service...
Stopping Serial Getty on ttymxc0...
Stopping Network Service...
Stopping Load/Save Random Seed...
Stopping TEE Supplicant...
[ OK ] Stopped Network Service.
[ OK ] Stopped Avahi mDNS/DNS-SD Stack.
[ OK ] Stopped Kernel Logging Service.
[ OK ] Stopped System Logging Service.
[ OK ] Stopped D-Bus System Message Bus.
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped Telephony service.
[ OK ] Stopped Serial Getty on ttymxc0.
[ OK ] Stopped TEE Supplicant.
[ OK ] Stopped Save/Restore Sound Card State.
[ OK ] Stopped Load/Save Random Seed.
[ OK ] Removed slice system-getty.slice.
[ OK ] Removed slice system-serial\x2dgetty.slice.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Paths.
[ OK ] Stopped Dispatch Password …ts to Console Directory Watch.
[ OK ] Stopped Forward Password R…uests to Wall Directory Watch.
[ OK ] Stopped target Slices.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Sockets.
[ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
[ OK ] Closed Syslog Socket.
Stopping Load/Save Screen …backlight:backlight-display...
[ OK ] Stopped Apply Kernel Variables.
[ OK ] Stopped Update is Completed.
[ OK ] Stopped Rebuild Dynamic Linker Cache.
[ OK ] Stopped Rebuild Journal Catalog.
[ OK ] Stopped Create Volatile Files and Directories.
[ OK ] Stopped target Local File Systems.
Unmounting Temporary Directory (/tmp)...
Unmounting /var/volatile...
[ OK ] Stopped Load/Save Screen B…f backlight:backlight-display.
[ OK ] Unmounted Temporary Directory (/tmp).
[ OK ] Unmounted /var/volatile.
[ OK ] Removed slice system-systemd\x2dbacklight.slice.
[ OK ] Stopped target Local File Systems (Pre).
[ OK ] Stopped target Swap.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Create System Users.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 170.998048] watchdog: watchdog0: watchdog did not stop!
[ 171.033471] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 171.042851] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 171.067166] systemd-journald[117]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 171.093893] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 171.115632] systemd-shutdown[1]: Using hardware watchdog 'imx2+ watchdog', version 0, device /dev/watchdog
[ 171.131600] systemd-shutdown[1]: Unmounting file systems.
[ 171.141514] [198]: Remounting '/' read-only in with options '(null)'.
[ 171.149145] systemd-shutdown[1]: All filesystems unmounted.
[ 171.155328] systemd-shutdown[1]: Deactivating swaps.
[ 171.160880] systemd-shutdown[1]: All swaps deactivated.
[ 171.166155] systemd-shutdown[1]: Detaching loop devices.
[ 171.181098] systemd-shutdown[1]: All loop devices detached.
[ 171.186728] systemd-shutdown[1]: Stopping MD devices.
[ 171.192847] systemd-shutdown[1]: All MD devices stopped.
[ 171.198212] systemd-shutdown[1]: Detaching DM devices.
[ 171.204392] systemd-shutdown[1]: All DM devices detached.
[ 171.209848] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[ 171.224121] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 171.233279] systemd-shutdown[1]: Rebooting.
[ 171.263646] ci_hdrc ci_hdrc.1: remove, state 4
[ 171.268130] usb usb1: USB disconnect, device number 1
[ 171.274449] ci_hdrc ci_hdrc.1: USB bus 1 deregistered
[ 171.297357] imx2-wdt 20bc000.watchdog: Device shutdown: Expect reboot!
[ 171.304882] reboot: Restarting system
[ 172.309040] Reboot failed -- System halted

CFG_TZDRAM_START ?= ($(CFG_DRAM_BASE) + 0x04000000)
reboot is ok!!

CFG_TZDRAM_START ?= ($(CFG_DRAM_BASE) + 0x0B000000)

reboot failed!!

Re: imx6ull start kernel fail from op-tee

Yuri — Wed, 05 Jan 2022 08:18:49 GMT

@kk163
Hello,

usually it is recommended to provide total system Power On Reset if system should be
reboot - in order to avoid iMX boot issues, when power is not removed from all board
components.

Is it implemented on Your board?

Regards,
Yuri.

Re: imx6ull start kernel fail from op-tee

kk163 — Wed, 05 Jan 2022 08:49:13 GMT

Yes, it was implemented on the imx6ullevk board. The customer raised this question and wanted to know what caused the reboot fail after CFG_TZDRAM_START ?= ($(CFG_DRAM_BASE) + 0x0B000000) ?

thanks!

i.MX ProcessorsのトピックRe: imx6ull start kernel fail from op-tee

imx6ull start kernel fail from op-tee

Re: imx6ull start kernel fail from op-tee

Re: imx6ull start kernel fail from op-tee

Re: imx6ull start kernel fail from op-tee

Re: imx6ull start kernel fail from op-tee

Re: imx6ull start kernel fail from op-tee