OPTEE + Android 8

Products Support HiKey
#42

@deepakmnvl

Thanks for the information!

#43

@deepakmnvl

Diff - 5af9bdca62d686dd0554269f1ef4027e9a95b60b^! - device/linaro/hikey - Git at Google should be the right fix for the settings UI crash problem.

Thanks,
Yongqin Liu

#44

Hi,
I am not getting cmd line shell prompt in TZ log window. Should anything need to be changed ?

Used to have in AOSP7+OPTEE , where I can enter commands in TZ shell too !!!

Thanks,
Deepak

#45

There’s no cmd line shell for the secure OS. It’s not a ‘full’ OS like Linux. You can only interact the secure OS via TAs.

#46

hmm, i meant, I can give cmd like : “setprop sys.usb.configfs 1” in TZ shell AOSP7+OPTEE stack.

Isnt this possible in current stack ?

#47

Ok. It’s just the regular shell. Calling it the TZ shell is confusing.

The shell should be there. Did you try pressing enter a few times? Or you can use adb connection to the device.

#48

In any case, sys.usb.configfs should already be set to 1.

#49

shell isnt appearing for me.
Are you getting in OPTEE stack ? :open_mouth:

Yes, I am having adb connection , but I am trying to automate some tasks based on TZ logs, so , having shell on UART will be helpful

#50

Sorry, not sure what you mean by ‘getting in OPTEE stack’, but yes, I do have a shell. I think if you run adb shell, you also get into a ‘shell’ that pretty much let you do anything you can/would from a regular shell, no?

As for the regular shell, do you see boot logs on the console? If so, maybe the Tx pin on your cable or connector is bad. Maybe try another cable or computer.

#51

ooh, wait, I see a difference here

when i flash boot.img, I get minimal logs and NO console prompt
when i flash boot_fat.uefi.img , I get lot many logs and console prompt too

Also, I cannot execute regular commands like “ls” due to permissions. I get errors like this :

ls: ./init.hik[ 156.413809] type=1400 audit(162.131:112): avc: denied { getattr } for pid=2059 comm=“ls” path="/init" dev=“rootfs” ino=10378 scontext=u:r:shell:s0 tcontext=u:object_r:init_exec:s0 tclass=file permissive=0
ey.rc: Permissio[ 156.433226] type=1400 audit(162.131:113): avc: denied { getattr } for pid=2059 comm=“ls” path="/fstab.hikey" dev=“rootfs” ino=10377 scontext=u:r:shell:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=0

Do you have solution for this ?
Else , I need to dwell into selinux dir , Again !!! :disappointed:

Thanks

#52

Hrm, that’s weird. boot.img should still give you a prompt regardless.

In any case, we’re still running things as root atm, so try running su before ls. shell user doesn’t have permission to access /init and /fstab.hikey.

#53

Hi @vchong,
few questions here !!!

  1. Is hikey960+optee supported ? Any stable stack ? if currently not , any timeline for it ?

  2. hikey620 boards are hard to procure. any online source where i can buy them ?
    Strangely , I see it as discontinued in many sites and but you guys are working on it :roll_eyes:

  3. If not hikey , any other board you can suggest that have AOSP + OPTEE support and readily available. We prefer 96boards as we use a customized extension board connected to LowSpeed slot.
    Previously, we used dragon (but seems it doesnt have any TZ OS support !!!)

Thanks

#54

  1. Nothing stable. No timeline.

  2. There were several left on amazon last week.

  3. There’s TI board (https://github.com/petegriffin/misc-docs/blob/master/am57xx-android.md), but not sure how easy it is to get. There’s also Poplar board but it’s work in progress so no build instructions yet.

Dragonboard TZ OS is not available to the public atm.

#55

hi,
any help in this issue ?

Thanks