9:54 a.m.
Sinha:
You can modify the device/intel/mixins/groups/kernel/project-celadon/BoardConfig.mk and
run device/intel/mixin-update.
BR/Tan Ming.
From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Tan, Ming
Sent: Tuesday, December 25, 2018 8:49 AM
To: Soham Sinha <soham1(a)bu.edu>
Cc: celadon(a)lists.01.org; Gnanasekaran, Sundar <sundar.gnanasekaran(a)intel.com>
Subject: Re: [01.org Celadon] Up Squared Target Name
Sinha:
I purpose to make the serial port does work at first. Check the pin you connected, and
in the GRUB kernel command line, add the ‘ignore_loglevel’ to make the kernel to output
more log.
How long when you wait for the ‘format data’ to complete?
In my memory, the command of ‘format data’ need about 8 minutes, ‘flashing lock’ and
‘flashing unlock’ cost almost same time.
BR/Tan Ming.
From: Soham Sinha [mailto:soham1@bu.edu]
Sent: Tuesday, December 25, 2018 7:04 AM
To: Tan, Ming <ming.tan@intel.com<mailto:ming.tan@intel.com>>
Cc: celadon@lists.01.org<mailto:celadon@lists.01.org>; Gnanasekaran, Sundar
<sundar.gnanasekaran@intel.com<mailto:sundar.gnanasekaran@intel.com>>
Subject: Re: [01.org Celadon] Up Squared Target Name
When I was "make"-ing, I passed the SERIAL_PARAMETER, but it didn't change
the boot parameters in GRUB. I had to manually change it in the GRUB menu (after mounting
the img file locally). I even tried the BoardConfig.mk as suggested by G Sundar, but when
I run mixin-update BoardConfig.mk seems to get overwritten with a default value of
"console=tty0 console=ttyS2,115200n8". However, neither ttyS0, nor ttyS1/S2 gave
me serial console output.
I disabled trusty partition in mixins.spec and recompiled the code. However, the GRUB
booting still did not work. The problem with the GRUB booting might be something to do
with the memory mapping. So I am embedding a picture of the GRUB menu entries, so that you
can have a better look.
[IMG_20181224_165515.jpg]
After this screen, when I press F10, it shows "Booting a command list", then
keyboard goes off.
The KernelFlinger approach works. Firstly, when the flashing is going on, it hangs up in
the command: "format data"
[IMG_20181224_173922.jpg]
Then I remove the "format data" command from installer.cmd in EFI shell, then
the flashing continues but halts again on "flashing lock" command:
[IMG_20181224_174912.jpg]
If I remove the "flashing lock" command from the installer.cmd, then next
restart works and opens up the GUI. As I said before I could not see any serial port logs
unfortunately.
I am uploading both the image files, so that you can have a better look: GRUB based
image<https://drive.google.com/open?id=1Lj39KlGuyH40glUZqVEi0SLDnJscOX...;,
KernelFlinger based
Zip<https://drive.google.com/open?id=1tm68SRreE1vV4f2ZwEDbzl2YS9F7tjss>;. Thanks for
your help! I really appreciate it.
Regards,
Soham Sinha
PhD Student, Department of Computer Science
Boston University
On Sun, Dec 23, 2018 at 7:50 PM Tan, Ming
<ming.tan@intel.com<mailto:ming.tan@intel.com>> wrote:
Sinha:
When you build the images, you can add the SERIAL_PARAMETER="console=tty0
console=ttyS1,115200n8" in make command option to use ttyS1 for kernel console.
There is no configuration of serial port in kernelflinger. Kernelflinger use the BIOS
boot service to output the log.
I have not tested Celadon in 32-bit, I guest need a lot of effort to enable it.
I have no idea about add the lunch target and let the GUI without Hardware
Acceleration.
BR/Tan Ming.
From: Soham Sinha [mailto:soham1@bu.edu<mailto:soham1@bu.edu>]
Sent: Monday, December 24, 2018 8:39 AM
To: Tan, Ming <ming.tan@intel.com<mailto:ming.tan@intel.com>>
Cc: celadon@lists.01.org<mailto:celadon@lists.01.org>; Li, Zhuangzhi
<zhuangzhi.li@intel.com<mailto:zhuangzhi.li@intel.com>>
Subject: Re: [01.org<http://01.org> Celadon] Up Squared Target Name
Hello Tan,
Thanks for helping!
Where do you change the console ttyS1?
For GRUB, I changed in the bootloader menuentry in linux line.
For KernelFlinger, where am I supposed to do it?
Also, is it possible to add a lunch target for the UP2 boards for Celadon? It could be
helpful.
Another question: is there any way to build Celadon for 32-bit, instead of the default 64
bit one?
Lastly, a note from my side, I can run android-x86 8.1-rc1 32-bit ISO from the android-x86
project and live-boot android on the UP Squared. It shows up the GUI. This works with
their "No Hardware Acceleration" menu entry.
Regards,
Soham Sinha
CS PhD Student
Boston University
On Sun, Dec 23, 2018, 7:27 PM Tan, Ming
<ming.tan@intel.com<mailto:ming.tan@intel.com> wrote:
Sinha:
We enabled the Celadon in UP2 board in May, and it can boot to UI.
The following need to be take care:
1. If the ttyS0 does not work, then refer to
https://up-board.org/wp-content/uploads/datasheets/UP-Square-DatasheetV0...., use the
Pin 8,9,10 in the 40Pin GP-Bus, and try to use ttyS1.
2. Disable the trusty.
Modify the device/intel/project-celadon/celadon/mixins.spec, set the trusty: false,
and in boot-arch:, set tos_partition=false.
You can also disable the trusty and try it in SKL NUC.
BR/Tan Ming.
From: Soham Sinha [mailto:soham1@bu.edu<mailto:soham1@bu.edu>]
Sent: Monday, December 24, 2018 6:38 AM
To: Tan, Ming <ming.tan@intel.com<mailto:ming.tan@intel.com>>
Cc: celadon@lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org<http://01.org> Celadon] Up Squared Target Name
Hello,
I am working with UP2 or UP Squared boards: Intel Pentium
version<https://up-board.org/upsquared/specifications/>;.
I applied the patch. Unfortunately, I could not get any output from the serial console. I
can get serial console output in other cases but not with Project Celadon images. So the
serial pins are working fine.
I tried both the GRUB and kernelflinger processes. For GRUB, I changed to
console=ttyS0,115200n8 which seems to be the required one for Up Squared board. I
didn't connect any keyboard or display. Still, I could not see any output on my client
serial output.
For the KernelFligner as well, nothing comes to the console.
Additionally, I tried the GRUB booting process on an Intel Skull
Canyon<https://www.intel.com/content/www/us/en/products/docs/boards-ki...;.
Same issue happened: when I select any of the boot options, the screen freezes, and the
keyboard stops working. I have not tried the KernelFlinger direct booting on Skull Canyon
because it seems to be directly working on the hard disk without any warning, which I
don't want, as of now.
Any clue or suggestions on how to fix this?
Regards,
Soham Sinha
PhD Student, Department of Computer Science
Boston University
On Sun, Dec 23, 2018 at 9:06 AM Tan, Ming
<ming.tan@intel.com<mailto:ming.tan@intel.com>> wrote:
Sinha:
Which type of UP board are you using? There are several type of UP board in
https://up-board.org/.
Can you mail me the serial log of kernelflinger to me?
And you can try the patch of
https://github.com/projectceladon/hardware-intel-kernelflinger/pull/5 to output more
detail kernel log. And the default serial port used by kernel is ttyS0, you need to check
the UP board use which serial port.
You can ignore the ‘Failed to get SDIO protocol’ warning and need not copy
userdata.img.
BR/Tan Ming.
From: Soham Sinha [mailto:soham1@bu.edu<mailto:soham1@bu.edu>]
Sent: Sunday, December 23, 2018 9:54 PM
To: Tan, Ming <ming.tan@intel.com<mailto:ming.tan@intel.com>>
Cc: celadon@lists.01.org<mailto:celadon@lists.01.org>
Subject: Re: [01.org<http://01.org> Celadon] Up Squared Target Name
I have built for the Celadon target but none of the booting processes works for Up
Squared. I'm trying out the 8.1 branch.
For the GRUB process, I copied over celadon.img, but once I select project Celadon from
the boot menu, nothing shows up, keyboard stops working.
For the KernelFlinger via EFI shell process, there seems to be some issue with eMMC
storage. When the flashing is going on in EFI shell, I get error message as " Failed
to get SDIO protocol". But the flashing continues and finally gets stuck on
"flashing lock". When I remove the "flashing lock" fastboot command
from installer.cmd file, flashing is completed. But then the booting hangs up in the
"Intel" logo screen and never goes to the Android logo screen. Another issue was
that I had to additionally copy userdata.img to the USB disk, which was not included in
the KernelFlinger zip files.
Regards,
Soham Sinha
CS PhD Student
Boston University
On Sun, Dec 23, 2018, 8:39 AM Tan, Ming
<ming.tan@intel.com<mailto:ming.tan@intel.com> wrote:
Sinha:
Currently Celadon has two lunch target: celadon and cel_apl.
Celadon is used for Android table device. Cel_apl is used for Android automotive
device.
You can select one as your device usage.
BR/Tan Ming.
From: Celadon
[mailto:celadon-bounces@lists.01.org<mailto:celadon-bounces@lists.01.org>] On Behalf
Of Soham Sinha
Sent: Sunday, December 23, 2018 5:28 AM
To: celadon@lists.01.org<mailto:celadon@lists.01.org>
Subject: [01.org<http://01.org> Celadon] Up Squared Target Name
Hello,
I understand that Android-IA is now merged with Project Celadon. I am wondering what the
name of the target is for previous Android-IA platforms. I want to build Project Celdaon
for an Up Squared machine. Thanks!
Regards,
Soham Sinha
PhD Student, Department of Computer Science
Boston University
