Bug 8719

Where can I find a list of reference BSPs?

The machines defined in meta-yocto-bsp.

I'm still puzzled with this bug. The description is too generic to me.

Does this bug means that I need to generate bootable images for all boards mentioned here http://git.yoctoproject.org/cgit.cgi/meta-yocto/tree/README.hardware and change image instructions in that file?

(In reply to comment #3)
> Does this bug means that I need to generate bootable images for all boards
> mentioned here
> http://git.yoctoproject.org/cgit.cgi/meta-yocto/tree/README.hardware and
> change image instructions in that file?

Yes, that's what I meant.

Moving to 2.2 as I will not have time for this in 2.1 time frame.

As a first step we'll try to make wic images produced by default for reference BSPs. I'm going to start with genericx86 and genericx86_64.

Enabled wic images for genericx86* BSPs: https://lists.yoctoproject.org/pipermail/poky/2016-September/010692.html

Enabled building of wic images for Beaglebone BSP: https://lists.yoctoproject.org/pipermail/poky/2016-September/010714.html

Successfully tested on BBB(Beaglebone Black).

So far I was able to test wic images on generic x86-64(my desktop) and Beaglebone hardware. There are 2 more reference BSPs mentioned in README.hardware that I don't have:
- Freescale MPC8315E-RDB
- Ubiquiti Networks EdgeRouter Lite

Can you suggest how should I proceed with this bug further without having access to the hardware?

Well, they have both of those in London AFAIK, obviously that's still some distance away but you could get one of the folks there to help. Aside from that README.hardware and the BSP should cover the basics of how these devices should be set up to boot.

We need to update the README.hardware file to remove the older Intel hardware and include at least the standard NUC and MB hardware, not sure if we should include any other hardware

Status update.

Set of wic fixes related to this bug were accepted recently to oe-core master:

Added support for PARTUUID for MBR partitions: http://lists.openembedded.org/pipermail/openembedded-core/2016-October/127339.html

Updated kernel command line in wks files:
http://lists.openembedded.org/pipermail/openembedded-core/2016-October/127361.html
http://lists.openembedded.org/pipermail/openembedded-core/2016-October/127380.html
http://lists.openembedded.org/pipermail/openembedded-core/2016-October/127418.html


There are also some patches under review:

 Usage of GPT table in all EFI .wks files: http://lists.openembedded.org/pipermail/openembedded-core/2016-October/127419.html

 Produce EFI images for genericx86* machines: https://lists.yoctoproject.org/pipermail/poky/2016-October/010742.html

 Update for README.hardware: https://lists.yoctoproject.org/pipermail/poky/2016-October/010741.html

Updated instructions for Beaglebone: https://lists.yoctoproject.org/pipermail/poky/2016-October/010749.html

Please, review.

Edgerouter changes submitted for review
[poky] [PATCH] edgerouter.conf: produce wic images for Edgerouter
https://lists.yoctoproject.org/pipermail/poky/2016-October/010754.html

[poky] [PATCH] README.hardware: update Edgerouter section
https://lists.yoctoproject.org/pipermail/poky/2016-October/010755.html

Saul, thank you for the help!

Moving to 2.3M1 as there work for Freescale MPC8315E-RDB hardware is not done yet.

Configured wic image building for qemux86* machines: http://lists.openembedded.org/pipermail/openembedded-core/2016-November/129219.html

Status update:
 All BSPs except of Freescale MPC8315 have been successfully tested
 machine configurations have been updated to produce wic images by default for genericx86_64, genericx86, beaglebone and edgerouter machines

Freescale MPC8315 machine I've got seem to be dead. I couldn't get into u-boot prompt on serial console. The only way to get it back to live I know about is to cold flash it using CodeWarrior flasher. However, this requires to use USB TAP device similar to this one http://uk.farnell.com/freescale-semiconductor/cwh-ctp-base-he/kit-codeworrior-tap-usb-eth/dp/2279949?MER=sy-me-pd-mi-acce which I don't have.

I need a suggestion how to proceed further with this.

A bit more details about MPC 8315:

I've tried to reflash it with IC2 bootloader embedded into the device.

kermit u-boot transfers u-boot.bin successfully, but after that device u-boot failed to erase flash.
Here is what I see on the screen:

---

## DONE binary (kermit) download

Serial Download Done

Flash Init Done

detected flash



...... done

Flash not Erased

The write error has occured and flash cann't be written

---

I tried to flash recent and original u-boot.bin but the error was always the same.

I'd appreciate any help with this.

With a great help from Yi Zhao we had some progress with MPC8315. Now the process is much more simple, i.e. it doesn't require dealing with NFS root.
The work is still in progress, but almost finished. You can see details in bug 10593.

Moving to M2 as work on MPC8315 is still ongoing.

Added wks file for MPC8315: http://lists.openembedded.org/pipermail/openembedded-core/2016-December/130296.html

Added beaglebone.wks to meta-yocto-bsp/wic/ https://lists.yoctoproject.org/pipermail/poky/2016-December/010848.html

enabled producing wic images for MPC8315: https://lists.yoctoproject.org/pipermail/poky/2016-December/010847.html

Added edgerouter.wks to meta-yocto-bsp/wic/: https://lists.yoctoproject.org/pipermail/poky/2017-January/010860.html

Added flashing instructions for MPC8315E-RDB: https://lists.yoctoproject.org/pipermail/poky/2017-January/010861.html

Added genericx86.wks to meta-yocto-bsp/wic: https://lists.yoctoproject.org/pipermail/poky/2017-January/010863.html

All patches have been sent for review.

All changes have been accepted to poky master.