Clone image from UP board A10 version to A11

AlingAling Administrator, AAEON, UP reseller Posts: 556 admin

Refer to the PCN change: https://forum.up-community.org/discussion/3601/pcn-up-board-series-pcb-emmc-change#latest

The eMMC was changed under this PCN. We notice that image across devices with different eMMC brand may brick the board. This issue seems to be caused by an issue in the eMMC controller embedded in Cherry Trail SoC. We have escalated to Intel for further analysis and resolution.

As it might take quite some time for Intel to provide a fix. The suggestion is to create a new image based on new eMMC.

In principle, we suggest you create a new image while there is PCN on the product, especially on eMMC to avoid similar problems.

The product still provides the same functionalities as it should be today, and we hope this solution could be helpful.

Comments

  • Pieter JordaanPieter Jordaan New Member Posts: 6

    @Aling said:
    Refer to the PCN change: https://forum.up-community.org/discussion/3601/pcn-up-board-series-pcb-emmc-change#latest

    The eMMC was changed under this PCN. We notice that image across devices with different eMMC brand may brick the board. This issue seems to be caused by an issue in the eMMC controller embedded in Cherry Trail SoC. We have escalated to Intel for further analysis and resolution.

    As it might take quite some time for Intel to provide a fix. The suggestion is to create a new image based on new eMMC.

    In principle, we suggest you create a new image while there is PCN on the product, especially on eMMC to avoid similar problems.

    The product still provides the same functionalities as it should be today, and we hope this solution could be helpful.

    We've been hit by this, with 15 devices stuck/bricked at the splash screen. No way to enter the BIOS. We've noticed the mmcblk0 is slightly smaller on the new revision, 12MB in fact. The pmbr is 16 MB on the new one, and 4MB on the old one, which I assume leads to a smaller data area.

    We've then shrunk our image by an arbitrary 300 MB and flashed a 16th one, with success. So it seems that if the image is too big it bricks the device. Not sure how the EMMC could prevent getting to the BIOS though?

    Is there any way to format the EMMC without reaching the BIOS? For instance could we somehow disable the EMMC (hardware or software), causing us to be able to boot to a bootable disk, then power back up the EMMC and format from within Linux? Hoping for something like this to be possible.

  • rogertsai(AAEON)rogertsai(AAEON) New Member Posts: 214 ✭✭✭

    @Pieter Jordaan

    Is there any way to format the EMMC without reaching the BIOS? For instance could we somehow disable the EMMC (hardware or software), causing us to be able to boot to a bootable disk, then power back up the EMMC and format from within Linux? Hoping for something like this to be possible.

    Unfortunately, we don't have any tools to reformat the eMMC
    It seems like the emmc has been crashed after image recovery, and stuck on splash screen (eMMC no response). I can't say for sure if the eMMC is broken, or firmware crashed during the recovery process
    Anyhow, for better troubleshooting, I would suggest you to contact your UP supplier for any RMA support

Sign In or Register to comment.