Loading a new yocto image to Intel Fri2 board

Loading a new yocto image to Intel Fri2 board

[Insop Song]

Hi,

I have a question on loading a new yocto image to Intel Fri2 board.

1. Board: Intel Fri2
--------------------------

2. Image: self built sato image with meta-fri2
--------------------------
I've followed an instruction from
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README
so do dd image of my sato image to usb as described
- "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf"

3. Sympton: stuck during boot and no ttyusb access
--------------------------
And connect it to the host USB port.
Then I can see the new grub menu that has "boot" and "install", so
selected "boot"

However, booting was stuck at around this line,
- "0000:03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart"

And I am not able to get the ttyUSB console working either.

4. Others: official sato image for Fri2 is not working either
--------------------------
Also just to make sure I "dd" the image from the official hdd img, but
the result is the same as my own image.

Anyone has tried the same? please let me know.

Thank you very much,

Insop

Re: Loading a new yocto image to Intel Fri2 board

[Insop Song]

Adding Scott, as I've followed the same procedure as described in
"Hands-on Intro Lab on Barcelona 2012" by Scott.



On Sun, Mar 10, 2013 at 4:16 AM, Insop Song <insop.song@gmail.com> wrote:
> Hi,
>
> I have a question on loading a new yocto image to Intel Fri2 board.
>
> 1. Board: Intel Fri2
> --------------------------
>
> 2. Image: self built sato image with meta-fri2
> --------------------------
> I've followed an instruction from
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README
> so do dd image of my sato image to usb as described
> - "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf"
>
> 3. Sympton: stuck during boot and no ttyusb access
> --------------------------
> And connect it to the host USB port.
> Then I can see the new grub menu that has "boot" and "install", so
> selected "boot"
>
> However, booting was stuck at around this line,
> - "0000:03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart"
>
> And I am not able to get the ttyUSB console working either.
>
> 4. Others: official sato image for Fri2 is not working either
> --------------------------
> Also just to make sure I "dd" the image from the official hdd img, but
> the result is the same as my own image.
>
> Anyone has tried the same? please let me know.
>
> Thank you very much,
>
> Insop

Re: Loading a new yocto image to Intel Fri2 board

[Darren Hart]

On 03/10/2013 04:16 AM, Insop Song wrote:
> Hi,
> 
> I have a question on loading a new yocto image to Intel Fri2 board.
> 
> 1. Board: Intel Fri2
> --------------------------
> 
> 2. Image: self built sato image with meta-fri2
> --------------------------
> I've followed an instruction from
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README
> so do dd image of my sato image to usb as described
> - "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf"


Assuming you have the Intel provided UEFI fastboot firmware, I would
suggest using scripts/contrib/mkefidisk.sh rather than dd'ing the
hddimg. The hddimg is not in a format that is well supported by EFI.

mkefidisk.sh partitions the target device and creates a proper EFI
partition and a root partition.


> 
> 3. Sympton: stuck during boot and no ttyusb access
> --------------------------
> And connect it to the host USB port.
> Then I can see the new grub menu that has "boot" and "install", so
> selected "boot"
> 
> However, booting was stuck at around this line,
> - "0000:03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart"
> 
> And I am not able to get the ttyUSB console working either.


You don't see GRUB over the serial port? Do you see the UEFI shell on
the serial port. Does the ttyUSB* device appear on your host machine?
Are you configured at 115200 8n1?


> 4. Others: official sato image for Fri2 is not working either
> --------------------------
> Also just to make sure I "dd" the image from the official hdd img, but
> the result is the same as my own image.
> 
> Anyone has tried the same? please let me know.


Try mkefidisk.sh and let us know the result.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

Re: Loading a new yocto image to Intel Fri2 board

[Insop Song]

Hi Darren,

mkefidisk.sh works, thank you.

What I found was, USB still doesn't work even with mkefidisk.sh.
So I used micro sd card instead.

I will use sd card for now, so it should be fine for now.

Regards,

Insop

On Wed, Mar 13, 2013 at 10:03 AM, Darren Hart <dvhart@linux.intel.com> wrote:
> On 03/10/2013 04:16 AM, Insop Song wrote:
>> Hi,
>>
>> I have a question on loading a new yocto image to Intel Fri2 board.
>>
>> 1. Board: Intel Fri2
>> --------------------------
>>
>> 2. Image: self built sato image with meta-fri2
>> --------------------------
>> I've followed an instruction from
>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/meta-fri2/README
>> so do dd image of my sato image to usb as described
>> - "dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf"
>
>
> Assuming you have the Intel provided UEFI fastboot firmware, I would
> suggest using scripts/contrib/mkefidisk.sh rather than dd'ing the
> hddimg. The hddimg is not in a format that is well supported by EFI.
>
> mkefidisk.sh partitions the target device and creates a proper EFI
> partition and a root partition.
>
>
>>
>> 3. Sympton: stuck during boot and no ttyusb access
>> --------------------------
>> And connect it to the host USB port.
>> Then I can see the new grub menu that has "boot" and "install", so
>> selected "boot"
>>
>> However, booting was stuck at around this line,
>> - "0000:03:0a.2: ttyPCH1 at I/O 0x2050 (irq = 41) is a pch_uart"
>>
>> And I am not able to get the ttyUSB console working either.
>
>
> You don't see GRUB over the serial port? Do you see the UEFI shell on
> the serial port. Does the ttyUSB* device appear on your host machine?
> Are you configured at 115200 8n1?
>
>
>> 4. Others: official sato image for Fri2 is not working either
>> --------------------------
>> Also just to make sure I "dd" the image from the official hdd img, but
>> the result is the same as my own image.
>>
>> Anyone has tried the same? please let me know.
>
>
> Try mkefidisk.sh and let us know the result.
>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Technical Lead - Linux Kernel

Re: Loading a new yocto image to Intel Fri2 board

[Darren Hart]

On 03/14/2013 12:56 PM, Insop Song wrote:
> Hi Darren,
> 
> mkefidisk.sh works, thank you.
> 
> What I found was, USB still doesn't work even with mkefidisk.sh.
> So I used micro sd card instead.

Aha, yes. You will need to add "rootwait" to your kernel command line
for reliable booting over usb. There is no way I see to determine if USB
is being used (/dev/sda could just as easily be SATA). Perhaps mkefidisk
should just use rootwait by default. Patches accepted.


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

Re: Loading a new yocto image to Intel Fri2 board

[Insop Song]

On Thu, Mar 14, 2013 at 1:15 PM, Darren Hart <dvhart@linux.intel.com> wrote:
> On 03/14/2013 12:56 PM, Insop Song wrote:
>> Hi Darren,
>>
>> mkefidisk.sh works, thank you.
>>
>> What I found was, USB still doesn't work even with mkefidisk.sh.
>> So I used micro sd card instead.
>
> Aha, yes. You will need to add "rootwait" to your kernel command line
> for reliable booting over usb. There is no way I see to determine if USB
> is being used (/dev/sda could just as easily be SATA). Perhaps mkefidisk
> should just use rootwait by default. Patches accepted.
>


"rootwait" was there.

1. when I run "sudo ~/bin/mkefidisk.sh /dev/sda
core-image-sato-sdk-fri2-20130309091839.hddimg /dev/mmcblk0"
but "root=" was set to mmcblk0.
So I changed "root=" manually to sda2, usb is booted as well.

yes, I should have put the last parameter to be "/dev/sda" instead..

2. so when I run "sudo ~/bin/mkefidisk.sh /dev/sda
core-image-sato-sdk-fri2-20130309091839.hddimg /dev/sda"
USB is also working fine.



Thank you very much for the help, now I can use fri2 to test "meta-realtime"

Insop

Re: Loading a new yocto image to Intel Fri2 board

[Darren Hart]

On 03/15/2013 02:26 AM, Insop Song wrote:
> On Thu, Mar 14, 2013 at 1:15 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>> On 03/14/2013 12:56 PM, Insop Song wrote:
>>> Hi Darren,
>>>
>>> mkefidisk.sh works, thank you.
>>>
>>> What I found was, USB still doesn't work even with mkefidisk.sh.
>>> So I used micro sd card instead.
>>
>> Aha, yes. You will need to add "rootwait" to your kernel command line
>> for reliable booting over usb. There is no way I see to determine if USB
>> is being used (/dev/sda could just as easily be SATA). Perhaps mkefidisk
>> should just use rootwait by default. Patches accepted.
>>
> 
> 
> "rootwait" was there.
> 
> 1. when I run "sudo ~/bin/mkefidisk.sh /dev/sda
> core-image-sato-sdk-fri2-20130309091839.hddimg /dev/mmcblk0"
> but "root=" was set to mmcblk0.
> So I changed "root=" manually to sda2, usb is booted as well.
> 
> yes, I should have put the last parameter to be "/dev/sda" instead..


This also explains why rootwait was there. The script tests for mmcblk0
and sets rootwait if so (if I remember correctly).


> 2. so when I run "sudo ~/bin/mkefidisk.sh /dev/sda
> core-image-sato-sdk-fri2-20130309091839.hddimg /dev/sda"
> USB is also working fine.


Check this image, I think you'll find that rootwait is missing for this
image.


> Thank you very much for the help, now I can use fri2 to test "meta-realtime"
> 
> Insop
> 

Great.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

Re: Loading a new yocto image to Intel Fri2 board

[Insop Song]

On Fri, Mar 15, 2013 at 8:58 AM, Darren Hart <dvhart@linux.intel.com> wrote:
>
> Check this image, I think you'll find that rootwait is missing for this
> image.
>

yes, no rootwait for "sda" type generation.

Regards,

Insop