December 2021 - Celadon

by jan.janson＠congatec.com

Hello, shortly: I am running now celadon caas on Elkhart Lake (bare metal). I run yocto-iotg r68 kernel (intel linux 5.4) because fits the EHL platform best. More recent kernels are better but unsupported by android 12. So what I did/have: 1) Android patches applied (aosp S patches), Trusty and selinux are disabled in mixin.spec, USE_TPM false on bootloader. 2) Kernel configuration: platform kernel with SELINUX disabled (CONFIG_SECURITY_SELINUX_DISABLE=y), CONFIG_STM disabled, LZ4 compression disabled (using CONFIG_KERNEL_GZIP) The result is: I have system installed on SATA. The kernel is booting, but end in some "it does not fit" troubles. The log attached, init blames on missing paths, db not found, modules not found. --- log: part1 (installation + 1st boot): https://pastebin.com/VC8RsgVU part2 (1st boot): https://pastebin.com/xddBBrct part3(1st boot): https://pastebin.com/tfDxRtgn part4(2nd boot): https://pastebin.com/i0wiz6t9 I assume it is normal when you use own kernel, some configuration does not fit. It could be very helpful to get some hint if anyone knows such state / has experience. I will dive deeper but now I am flooded by kernel error messages. I it hard to see the reason behind it. I bet it is some missing kernel configuration (attached to this post). --- .config https://pastebin.com/Xk2wDmsi Best Regards, Jan

4 months, 4 weeks

2
3
0 / 0

kernel configuration fragments

by jan.janson＠congatec.com

Hello, how can I modify the kernel configuration ? I need modify the kernel configuration for our custom Elkhart Lake product. Currently, I am using CIV_00.21.03.41_A12 with lts2019-chromium kernel. I need something like the kernel configuration fragments in : device/intel/project-celadon/caas/config-lts/lts2019-chromium/debug_diffconfig . The only place where I see kernel configuration mentioned is the menuconfig target in device/intel/mixins/groups/kernel/AndroidBoard.mk : menuconfig xconfig gconfig: $(CHECK_CONFIG_LOG) $(hide) xterm -e $(KERNEL_MAKE_CMD) $(KERNEL_MAKE_OPTIONS) $@ Unfortunately, it does not seem as functional. For example : a) the xterm command is blocked by android build environment build/soong/ui/build/paths/config.go (so seems as dropped). b) And when I enable it, then the command executed in xterm fails : --- console output --- make: Entering directory '/home/honza/civ/kernel/lts2019-cromium.original' make[1]: Entering directory '/home/honza/civ/out/target/product/caas/obj/kernel' GEN Makefile scripts/kconfig/conf --olddefconfig Kconfig # # No change to .config # make[1]: Leaving direcotry '/home/honza/civ/out/target/product/caas/obj/kernel' make: Leaving directory '/home/honza/civ/kernel/lts2019-cromium.original' --- console output end --- --- xterm output --- xterm: Can't execvp PATH=/home/honza/civ/prebuilts/build-tools/linux-x86/bin:/home/honza/civ/prebuilts/clang/host/linux-x86/clang-r416183b1/bin:/home/honza/civ/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.17-4.8/x86_64-linux/bin:/home/honza/civ/prebuilts/build-tools/path/linux-x86:/home/honza/civ/out/.path: No such file or directory --- xterm output end --- How were the kernel configuration fragments (debug_diffconfig) done ? Best Regards, Jan Janson

5 months

2
4
0 / 0

Re: Bare Metal Celadon

by Ji, Zhenlong Z

Hi, Can you make a build with trusty and tpm disabled and have a try? With the latest code, you can set the value of trusty and tpm both to false in the mixins.spec file. From: Jan Kehren <jan.kehren(a)emteria.com<mailto:jan.kehren@emteria.com>> Sent: Tuesday, December 21, 2021 4:45 PM To: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: [01.org Celadon] Bare Metal Celadon Hello, we have some technical issues getting Project Celadon run bare metal. * Currently CiV usb-live boot, takes 5-6 minutes to boot. Is it common or is it due to bad configuration on our side? * When trying to install it natively, we followed the description from https://docs.01.org/celadon/tutorials/boot-civ-bare-metal.html until the interaction with the UEFI shell. As our device doesn't have a built-in UEFI, our developers downloaded and created efi/boot/Bootx64.efi on the USB storage drive. This causes the shell to startup and the script installer --batch installer.cmd started with following error messages. Is there documentation for how to fix it? - Call Tpm2GetCapability failed: Not Found - Get TPM cap permanent failed: Not Found - Check TPM cap for lockoutAuthSet failed: Not Found - failed to get random: Not Found - build PCR policy failed: Not Found - name or value too long for variable 'board' - Fastboot library initialization failed: Buffer Too Small - Failed to initialize Installer for fastboot transport layer: Not Ready - Failed to initialize transport layer: Not Ready Best regards, -- M. Sc. Jan Kehren Group Leader Embedded Android Development [cid:image002.png@01D7F800.C06B39A0] Phone: +49 241 80 211<callto:+49%20(2938)%209763907>73 E-mail: jan.kehren(a)emteria.com<mailto:jan.kehren@emteria.com> Web: https://emteria.com emteria GmbH Ahornstr. 55 52074 Aachen Germany Geschäftsführer: Dr. Igor Kalkov - USt-Nr.: DE313720332 - Amtsgericht Aachen - HRB 21466

5 months

1
1
0 / 0

Bare Metal Celadon

by Jan Kehren

Hello, we have some technical issues getting Project Celadon run bare metal. * Currently CiV usb-live boot, takes 5-6 minutes to boot. Is it common or is it due to bad configuration on our side? * When trying to install it natively, we followed the description from https://docs.01.org/celadon/tutorials/boot-civ-bare-metal.html until the interaction with the UEFI shell. As our device doesn't have a built-in UEFI, our developers downloaded and created efi/boot/Bootx64.efi on the USB storage drive. This causes the shell to startup and the script installer --batch installer.cmd started with following error messages. Is there documentation for how to fix it? - Call Tpm2GetCapability failed: Not Found - Get TPM cap permanent failed: Not Found - Check TPM cap for lockoutAuthSet failed: Not Found - failed to get random: Not Found - build PCR policy failed: Not Found - name or value too long for variable 'board' - Fastboot library initialization failed: Buffer Too Small - Failed to initialize Installer for fastboot transport layer: Not Ready - Failed to initialize transport layer: Not Ready Best regards, -- M. Sc. Jan Kehren Group Leader Embedded Android Development [cid:image001.png@01D7F64F.59AE8DA0] Phone: +49 241 80 211<callto:+49%20(2938)%209763907>73 E-mail: jan.kehren(a)emteria.com<mailto:jan.kehren@emteria.com> Web: https://emteria.com emteria GmbH Ahornstr. 55 52074 Aachen Germany Geschäftsführer: Dr. Igor Kalkov - USt-Nr.: DE313720332 - Amtsgericht Aachen - HRB 21466

5 months

1
0
0 / 0

Android 12 caas

by fguy2002＠yandex.ru

Thanks for your work on this project. I am collecting celadon for my tablet on cpu intel core m3 6Y30. I compiled version 12 of caas-userdebug with some of my patches for peripherals (wifi, touchscreen, etc.) as a disk image for direct booting from an external usb (to m.2 sata) ssd. Of the problems I noticed, I can note stuttering when playing video. I also had to turn off the wifi display in the overlay, and the not working gallery in aosp was not even surprised - the patch for 11 android is well known - I hope it will work at 12. I noticed that the development of celadon has shifted towards running on a virtual machine in Linux, which is just as interesting, but in a more convenient form than now, when it is necessary to carry out a lot of actions to configure the OS and components. Unfortunately, another version 11 stopped loading into VMware under windows - it was convenient for quick debugging and checking celadon assemblies with minimal overhead. I also understand that the formation of a common image with a large set of partitions meets the requirements of Google, but this form requires a dedicated disk to run, which is not always convenient for users to boot. For celadon 9, I still managed to boot from the system.img, vendor.img, ramdisk.img, kernel and data.img files from the windows partition with ntfs via refind. As the experience of the android x86 project shows, this option is still possible for newer versions of android. If you implemented this loading method, it would be convenient for many users.

5 months

4
8
0 / 0

The Celadon A12 not boot on Elkhart Lake platform

by rickchu＠flytech.com.tw

I have download Celadon A12 BSP (CIV_00.21.03.41_A12.xml), and can create caas.img & caas-flashfiles-eng.zip no problem. But when I test both live boot and flash install in Elkhart platform, it always stop on loader stage. The screen shows its untrusty seeds hardware, and then refused to jump to next step. The same image can boot to Android desktop on Skylake platform, have any thing that I need to modify for Celadon Android can running on Elkhart Lake platform? Rick

5 months, 1 week

2
2
0 / 0

Re: Ask about an Android startup error

by Huang, Yang

Hi It’s a strange error. This folder should have been created by init process. Do you have full logs? From: Shen, LinX <linx.shen(a)intel.com<mailto:linx.shen@intel.com>> Sent: Thursday, December 2, 2021 10:04 AM To: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Cc: Yuan, Hang <hang.yuan(a)intel.com<mailto:hang.yuan@intel.com>>; Ding, Zhuocheng <zhuocheng.ding(a)intel.com<mailto:zhuocheng.ding@intel.com>> Subject: [01.org Celadon] Ask about an Android startup error Hi, I am using Celadon compiled Android image to develop drivers in QEMU. But I’m having some problems launching the Android image and need your help. Here are my steps on env setup: 1. Using the setup_host.sh to setup the overall environment. 2. Using the build.sh to compile kernel and install on my dev machine. 3. Reboot dev machine and change kernel to 5.4.12-cvhb 4. Patch the enable-android.patch to qemu source 5. Compile qemu and install it. 6. Run the qemu with android image through start_civ.sh After the steps below, the word “Android” will appear in the QEMU interface, but will remain stuck in the interface. Through civ_serial.log, I found that the log output repeatedly error “/data/misc/credstore: No such file or directory”. My dev machine is Intel NUC8BEB It would be appreciated if you could spare some time to help out. Best Regards, Shen Lin

5 months, 3 weeks

2
1
0 / 0

Ask about an Android startup error

by Shen, LinX

Hi, I am using Celadon compiled Android image to develop drivers in QEMU. But I'm having some problems launching the Android image and need your help. Here are my steps on env setup: 1. Using the setup_host.sh to setup the overall environment. 2. Using the build.sh to compile kernel and install on my dev machine. 3. Reboot dev machine and change kernel to 5.4.12-cvhb 4. Patch the enable-android.patch to qemu source 5. Compile qemu and install it. 6. Run the qemu with android image through start_civ.sh After the steps below, the word "Android" will appear in the QEMU interface, but will remain stuck in the interface. Through civ_serial.log, I found that the log output repeatedly error "/data/misc/credstore: No such file or directory". My dev machine is Intel NUC8BEB It would be appreciated if you could spare some time to help out. Best Regards, Shen Lin

5 months, 3 weeks

1
0
0 / 0

2022

2021

2020

2019

2018

Celadon December 2021