i.MX ProcessorsのトピックRe: IMX6 Sabrelite u-boot problem

IMX6 Sabrelite u-boot problem

nilayjain — Wed, 21 Dec 2016 12:08:55 GMT

Hi All,

I am facing some problem with imx6q sabrelite u-boot.It constantly shows error raise: Signal # 8 caught.

U-Boot 2016.03 (Dec 21 2016 - 14:54:21 +0530)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: SABRE Lite
I2C:   ready
DRAM: 1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2 MiB
raise: Signal # 8 caught
raise: Signal # 8 caught
raise: Signal # 8 caught
raise: Signal # 8 caught
raise: Signal # 8 caught

...

I think this problem is because of some incorrect boot argument.Kindly suggest how to reset boot args saved in SPI.

Thanks

Re: IMX6 Sabrelite u-boot problem

gary_bisson — Wed, 21 Dec 2016 12:54:23 GMT

Hi,

Can you access the U-Boot prompt?

If so, please enter:

=> env default -a

=> saveenv

Did this error occur after a U-Boot upgrade?

Regards,

Gary

Re: IMX6 Sabrelite u-boot problem

nilayjain — Wed, 21 Dec 2016 13:00:01 GMT

Hi,

I am not able to access uboot prompt.

This error started after I updated boot args.

Re: IMX6 Sabrelite u-boot problem

gary_bisson — Wed, 21 Dec 2016 15:03:25 GMT

Hi,

In that case, I suggest you re-build a custom U-Boot that doesn't read the environment from SPI NOR:

u-boot-imx6/boundary.h at boundary-v2016.03 · boundarydevices/u-boot-imx6 · GitHub

Then I would use that procedure to boot this binary:

Unbricking a Nitrogen6X or Sabre Lite i.MX6 board - Boundary Devices

Then you should get U-Boot prompt again.

Hope this helps.

Regards,

Gary

Re: IMX6 Sabrelite u-boot problem

nilayjain — Thu, 22 Dec 2016 06:56:51 GMT

Hi,

I tried a custom u-boot with CONFIG_ENV_IS_IN_MMC macro.

Now I am able to access u-boot prompt,but while saving new boot args it gives a error.

Saving Environment to MMC...
MMC: no card present
!MMC init failed

Re: IMX6 Sabrelite u-boot problem

gary_bisson — Thu, 22 Dec 2016 09:51:55 GMT

Hi,

Yes it is normal since you set env to mmc in this U-Boot configuration.

Instead, you need to enter the following commands:

=> sf probe

=> sf erase 0xc0000 0x2000

Regards,

Gary