Help! Restoring Android image on imx6 SABRE SD card

[floriang]

Hello,

I have an imx6 SABRE SD board that I use currently to start some embedded development.

In order to try the manufacturing tools, I used the images provided by freescale to re-flash the SD card in order to restore the initial board images, and now my board freezes at random during startup.

Sometimes I am able to go up to the OS.

But sometimes it freezes before.

• Here is the error message I get from the debug port when the board is freezed:

------------[ cut here ]------------

WARNING: at arch/arm/plat-mxc/clock.c:63 __clk_disable+0x7c/0xac()

clock enable/disable mismatch! clk  pll2_pfd_400M

Modules linked in:

[<c004c634>] (unwind_backtrace+0x0/0xfc) from [<c007a568>] (warn_slowpath_common+0x4c/0x64)

[<c007a568>] (warn_slowpath_common+0x4c/0x64) from [<c007a614>] (warn_slowpath_fmt+0x30/0x40)

[<c007a614>] (warn_slowpath_fmt+0x30/0x40) from [<c0066ca4>] (__clk_disable+0x7c/0xac)

[<c0066ca4>] (__clk_disable+0x7c/0xac) from [<c0066e00>] (clk_disable+0x44/0x8c)

[<c0066e00>] (clk_disable+0x44/0x8c) from [<c03ad77c>] (plt_clk_ctrl+0x18/0x34)

[<c03ad77c>] (plt_clk_ctrl+0x18/0x34) from [<c03a8598>] (sdhci_clk_worker+0x2c/0x30)

[<c03a8598>] (sdhci_clk_worker+0x2c/0x30) from [<c008ea28>] (process_one_work+0x114/0x3d8)

[<c008ea28>] (process_one_work+0x114/0x3d8) from [<c008f05c>] (worker_thread+0x174/0x448)

[<c008f05c>] (worker_thread+0x174/0x448) from [<c00950f4>] (kthread+0x84/0x8c)

[<c00950f4>] (kthread+0x84/0x8c) from [<c00460b4>] (kernel_thread_exit+0x0/0x8)

---[ end trace 66724168d5f17857 ]---

clock enable/disable mismatch! clk  pll2_pfd_400Mbinder: release 2460:2460 transaction 6178 out, still active

• For restoring the images I am using:
  IMX_6DQ_MFG_TOOL : Tool and documentation for downloading OS images to the i.MX 6Quad and i.MX6Dual. (for the manufacturing tools)
  IMX6_R13.41_ANDROID_DEMO_IMAGE : i.MX 6Quad, i.MX 6Dual, and i.MX 6DualLite Android 13.4.1 BSP Binary Demo Files. (for the android image)

• Then I took boot.img, recovery.img, system.img from the folder:
  image_imx-android-13.4.1_6qsabresd\sabresd_6dq\SD
  copied it to
  {Mfgtools-Rel-4.0.0_130424_MX6Q_UPDATER}\Profiles\MX6Q Linux Update\OS Firmware\files\android
  Copied u-boot-6q.bin to {Mfgtools-Rel-4.0.0_130424_MX6Q_UPDATER}\Profiles\MX6Q Linux Update\OS Firmware\files\android
  And renamed u-boot-6q.bin to u-boot.bin

• And modified ucl2.xml to add the following LIST element to write the android files to the SD card.
  I created this element by copying the contents for eMMC, and replacing the /dev/mmcblk0 by /dev/mmcblk1 (since the "Sabre-SD" LIST element that is using the sd card writes to /dev/mmcblk1)

• After all that the update is successful and I can startup, but the board freezes at random with the error I told in the beginning
  It was working well before I overwrited the images, so is there something wrong in my steps or settings? Or is the image broken?

I join the ucl2.xml file and my cfg.ini file if it can help to spot the issue

Original Attachment has been moved to: ucl2.xml.zip

Original Attachment has been moved to: cfg.ini.zip

[harald_krapfenb]

Good!

[harald_krapfenb]

Hello,

Do you have an SD card reader on your PC? And Linux installed?

Then it would be quiet easier to re-create the SD card...

Regards,

Harald Krapfenbauer

[floriang]

Hi Harald, thank you for your reply.

I have ubuntu installed in a VM on my PC.

How can I do to recreate the SD card?

[harald_krapfenb · Accepted solution]

Hi Florian,

I'm seeing that it's even simpler...please download either

IMX6_DQ_SDB_SD_DEMO_IMAGE

or

IMX6_DQ_SDP_SD_DEMO_IMAGE

from Freescale website (depending on what you have - Smart Devices BOARD or Smart Devices PLATFORM).

This is a Windows .exe that writes the image to any drive of your computer. Select the one of your SD card. (Double-check!)

This will restore the original image of SABRE SD.

Regards,

Harald

[floriang]

It worked! Thank you very much!

[floriang]

Oh I have a very good feeling about this solution. I didn't know this download contained these images (though the explanation is quite clear, and actually it was too clear so I thought it was something else...)

Thanks for the hint I'll give it a try and post the result.