For “Can I just disable them in device/intel/project-celadon/cel_apl/device.mk ?”, GFX team can’t answer this as it related to whole system integration I think.
For APL NUC 4K support, we didn’t find 4K EPIC. And APL NUC hardware EDS shows HDIM only support max resolution 4K 3840x2160 30fps, and we also known that 4K also met some flicker issues due to display buffer side limitation when enabling some GFX feature, e.g. RBC. APL IVI may can boot to 4K 3840x2160 60fps, but we don’t know if there are some other potential issue.
For different result of APL IVI and APL tablet of 4K 3840x2160 60fps, I got info that we haven’t verified APL tablet for long time, there should has some diffs, but not sure if we need continue investigate it as no 4k EPIC found.
Above are all I know, so possible way is: we start to verify 4K 3840x2160 30fps(but not sure it is make sense to use 30 fps for 4k, or force using 1080P 60 fps for big resolution) for APL if we need support 4K, and figure out if we need limit the max resolution to 4K 3840x2160 30fps in somewhere, e.g. some config files/vbt.
Best regards,
Yugang
From: Dominik Louven [mailto:dlouven@videro.com]
Sent: Thursday, May 9, 2019 11:58 AM
To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build
Hello everyone,
Any news on this ?
Best regards,
Dominik Louven
On 6. May 2019, at 12:12, Dominik Louven <dlouven(a)videro.com<mailto:dlouven@videro.com>> wrote:
Hi Swaroop,
Thank you in advance. To be a little more specific. I would like to exclude all car components from the cel_apl build.
Can I just disable them in device/intel/project-celadon/cel_apl/device.mk ?
Please let me know if you find a way to exclude the car components from the compilation , because my NUC is not embedded in a car =)
Best regards,
Dominik Louven
On 6. May 2019, at 12:09, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote:
Hello Dominik
Please give me some time , I will check and let you know after taking a clean tablet build from GitHub
Regards
Swaroop
From: Dominik Louven [mailto:dlouven@videro.com]
Sent: Monday, May 6, 2019 3:26 PM
To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org<http://01.org> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build
Hello Swaroop,
It works fine now, I can boot into OS with celadon_apl-userdebug.
Is it possible to disable the car launcher and car applications in the build ?
Best regards,
Dominik Louven
On 3. May 2019, at 12:24, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote:
Hello Dominik
Celadon is for tablet and cel-apl is for APL NUC IVI
Regards
Swaroop
From: Dominik Louven [mailto:dlouven@videro.com]
Sent: Friday, May 3, 2019 3:08 PM
To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build
Hello Swaroop,
I used :
lunch celadon-userdebug
Maybe that’s the issue here. I will try again with your steps.
What’s the different between the celadon and the cel-apl build ?
Best regards,
Dominik Louven
On 3. May 2019, at 11:35, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote:
Hello Dominic
I used a local build based on WW13
BIOS VERSION --> AYAPLCEL.86A.0059.2018.1226.1422
We used below steps to compile
• source build/envsetup.sh
• lunch cel-apl-userdebug
• make SPARSE_IMG=true flashfiles -j4
Regards
Swaroop
From: Dominik Louven [mailto:dlouven@videro.com]
Sent: Friday, May 3, 2019 3:02 PM
To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build
Hello Swaroop,
That is weird. Did you use the same manifest ww201913 ?
What BIOS version is your NUC running on and do I have set specific settings in the BIOS ?
Did you compile the OS with different steps ?
Best regards,
Dominik Louven
On 3. May 2019, at 11:29, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote:
Hello Dominik,
When I connect my NUC6CAYH (APL) to an 4K Display (View Sonic)
There was no issue for us in booting to home screen
Regards
Swaroop
From: Dominik Louven [mailto:dlouven@videro.com]
Sent: Friday, May 3, 2019 2:42 PM
To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build
Hello Swaroop,
Thanks a lot.
If you need any more information please let me know.
Best regards,
Dominik Louven
On 3. May 2019, at 11:08, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote:
Hello Dominik
We are checking at our end , Will update shortly
Regards
Swaroop
From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Dominik Louven
Sent: Friday, May 3, 2019 1:49 PM
To: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build
Hello everybody,
I have checked out the latest stable branch ww201913.xml .
When I connect my NUC6CAYH (APL) to an 4K Display (resolution 3840x2160) I am unable to boot into the launcher.
The NUC hangs in android boot screen.
What can I do ?
Please find logs below :
logcat https://pastebin.com/d8eGtPha
dumpsys https://pastebin.com/UjrxC5PW
bugreport https://drive.google.com/open?id=1oy9uQqqMpG_95Vsm4sUpH6pRjqnscPhN
I am running the latest BIOS on my NUC and the os was compiled using :
source build/envsetup.sh
lunch celadon-userdebug
make SPARSE_IMG=true flashfiles -j4
Best regards,
Dominik Louven
--
Celadon mailing list
Celadon(a)lists.01.org<mailto:Celadon@lists.01.org>
https://lists.01.org/mailman/listinfo/celadon

Great, looking forward to hearing from you :)
I have attached a picture of the popup.
Regards
Christoph
On 12.10.2019 02:41, Tan, Ming wrote:
> Christoph:
> We will try to check the trusty support in NUC8i5BNK.
>
> Can you share with me the picture of ' popup after android starts that tells me an internal error occurred and I should contact the manufacturer ' ?
>
> Thank you.
> Tan Ming.
>
> -----Original Message-----
> From: Christoph Kaser <lucene_list(a)iconparc.de>
> Sent: Friday, October 11, 2019 9:46 PM
> To: Tan, Ming <ming.tan(a)intel.com>
> Subject: Re: [01.org Celadon] Re: Support for NUC8i5BNK
>
> Hello Ming,
>
> Unfortunately, I do not have access to a USB 232 converter at the moment. I will try to get one.
>
> I tried to use Celadon Q, but there was the same problem: After installation, the system does not boot. On Q, the last message in the log is "Jump to Android Linux Kernel now".
>
> However, I managed to get Celadon with Android 9 running: I compiled a version without trusty by following https://01.org/projectceladon/documentation/tutorials/security/trusty-ena....
>
> This version runs on the NUC8. There is however a popup after android starts that tells me an internal error occurred and I should contact the manufacturer.
> So I guess the problem is somewhere in trusty or the TEE.
>
> Best regards
> Christoph
>
> On 10.10.2019 03:26, Tan, Ming wrote:
>> Christoph:
>> The red error message has not impact for boot to UI. We already change the log level in new version.
>> If you can build the image by self, you can build a userdebug image and add the patch https://github.com/projectceladon/hardware-intel-kernelflinger/pull/5 to check the kernel log?
>> You can refer to https://01.org/projectceladon/documentation/blogs/uart#enable-the-serial-... to use a USB RS232 convertor to get a USB serial port. Note: Use a FTDI chip based USB RS232 convertor.
>>
>> And can you try the Celadon Q? Simple use the newest version of Celadon?
>>
>> BR/Tan Ming.
>>
>>
>> -----Original Message-----
>> From: Christoph Kaser <lucene_list(a)iconparc.de>
>> Sent: Wednesday, October 9, 2019 3:30 PM
>> To: celadon(a)lists.01.org
>> Subject: [01.org Celadon] Re: Support for NUC8i5BNK
>>
>> Hello Ming,
>>
>> Thank you for your reply.
>> The BIOS version is BECFL357.86A.0074.2019.0916.1548, which should be the newest one available for this board (NUC8BEB).
>> I am using a Kingston A1000 M.2-SSD with a size of 240 GB.
>>
>> After the first boot after the installation, there are the following messages in red (see attached images 1st_boot_*.jpg):
>>
>> Failed to read counter for simulate: Aborted
>> key is not programmed. use the first derived key.: Aborted
>> Init RPMB key sucessfully
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>> [... something that scrolls by to quickly to read, but contains "invalid vbmeta header" ...]
>> with result
>> ERROR_INVALID_METADATA
>> - setting unbootable.
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>>
>> After the second boot, there are the following messages (see attached images 2nd_boot_*.jpg):
>>
>> Failed to read counter for simulate: Aborted
>> key is not programmed. use the first derived key.: Aborted
>> Init RPMB key sucessfully
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>>
>> After the third boot, I get (see attached image 3rd_boot_01.jpg):
>>
>> BOOTLOADER ERROR CODE 01
>>
>> Your device has failed verification.
>> It is corrupt. It can't be trusted
>> and will not boot.
>>
>> Please contact customer support
>> from your device's manufacturer.
>>
>> And on the left, in red:
>>
>> Init RPMB key sucessfully
>> Failed to read RollbackIndex_0000 EFI variable: Not Found
>> No bootable slots found.
>> Failed to get avb slot a/b flow result for boot: Invalid
>> Parameter
>>
>> After a while, the image of a broken android is shown with the messages (see attached image 3rd_boot_02.jpg):
>>
>> BOOTLOADER ERROR CODE 07
>>
>> WARNING:
>> No valid boot image found.
>>
>> (etc.)
>>
>> And the red messages:
>> XDCI is disabled. please enable it in BIOS: Unsupported
>> Can't run self implemented USB device mode protocol: Unsupported
>> Make sure xDCI is enabled in BIOS
>> ADB is listening on TCP 172.16.0.165:5555
>>
>> I hope the mailing list will allow the attachments.
>>
>> Best regards
>> Christoph
>>
>> On 09.10.2019 03:58, Tan, Ming wrote:
>>> Christoph:
>>> For
>>> https://media.githubusercontent.com/media/projectceladon/celadon-bina
>>> r y/master/ww201851/cel_apl-flashfiles.zip,
>>> what is the last picture when boot failed?
>>> What BIOS version of your NUC8i5BNK?
>>> What storage are you using?
>>>
>>> BR/Tan Ming.
>>>
>>> -----Original Message-----
>>> From: lucene_list(a)iconparc.de <lucene_list(a)iconparc.de>
>>> Sent: Tuesday, October 8, 2019 11:50 PM
>>> To: celadon(a)lists.01.org
>>> Subject: [01.org Celadon] Support for NUC8i5BNK
>>>
>>> Hello everyone,
>>>
>>> I tried to install Celadon on a NUC8i5BNK, but it fails to boot.
>>> I tried both a prebuilt celadon image (from
>>> https://media.githubusercontent.com/media/projectceladon/celadon-bina
>>> r
>>> y/master/ww201851/cel_apl-flashfiles.zip)
>>> and building my own (from the celadon/p/mr0/master branch).
>>>
>>> Installation worked fine, but when booting from the disk it fails and
>>> eventually displays "Your device is corrupt. It cannot be trusted and
>>> will not boot"
>>>
>>> Should Celadon work on this device? Is there something I can do to
>>> make it work, such as disabling verified boot?
>>>
>>> Regards
>>> Christoph
>>> --
>>> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an
>>> email to celadon-leave(a)lists.01.org
>>> --
>>> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an
>>> email to celadon-leave(a)lists.01.org
>> --
>> Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an
>> email to celadon-leave(a)lists.01.org
>

Hello everyone,
I am running Celadon on an Intel NUC attached to a no-name display (via HDMI).
Unfortunately, this display seems to report the supported resolutions in the wrong order, so every OS selects 1920x1080 as default resolution, even though the display supports 3840x2160.
When running another OS, I can change the resolution in the settings and it works. But on Celadon, I did not find a way to specify the preferred display resolution (not even in the source build). Is there a way to select the resolution?
Best regards
Christoph

Hello everyone,
I tried to install Celadon on a NUC8i5BNK, but it fails to boot.
I tried both a prebuilt celadon image (from https://media.githubusercontent.com/media/projectceladon/celadon-binary/m...) and building my own (from the celadon/p/mr0/master branch).
Installation worked fine, but when booting from the disk it fails and eventually displays "Your device is corrupt. It cannot be trusted and will not boot"
Should Celadon work on this device? Is there something I can do to make it work, such as disabling verified boot?
Regards
Christoph