Hello,
I am working with UP2 or UP Squared boards: Intel Pentium version.

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. 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> 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]
Sent: Sunday, December 23, 2018 9:54 PM
To: Tan, Ming <ming.tan@intel.com>
Cc: celadon@lists.01.org
Subject: Re: [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 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] On Behalf Of Soham Sinha
Sent: Sunday, December 23, 2018 5:28 AM
To: celadon@lists.01.org
Subject: [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