imx8mm: Reset cause: POR - Unable to program an image

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8mm: Reset cause: POR - Unable to program an image

140 Views
gilmotta
Contributor I

Hello, Please help me!

I used to be able to program an image by stopping the uboot then :

1. typing ums mmc 0

2. connect the board to Ubuntu and typing ddrescue -D --force image_name.img /dev/sbX

The latest batch of imx8mm boards that I received are failing with the above procedure within 1 minute into the ddrescue or 'dd'

The SOM resets itself with 

Reset cause: POR

I'm wondering if this is the watchdog. I am wondering if my environment is slow for the latest uboot. I tried 2 different laptops, 2 different eval boards and 5 different SOMs from the same batch and they all fail at the same point.

I don't know how to trouble shoot the root cause of the reset. All I have is the output from the uboot.

 

U-Boot 2020.10-52351-g1d495e1c1d (Jan 05 2021 - 09:36:34 -0800), Build: jenkins-uboot_v2020.10-30

 

CPU:   i.MX8MMQ rev1.0 at 1200 MHz

Reset cause: POR

Model: Boundary Devices i.MX8MMini Nitrogen8MM Som

Board: nitrogen8mm_som

       Watchdog enabled

DRAM:  2 GiB

MMC:   FSL_SDHC: 0, FSL_SDHC: 1

Loading Environment from MMC...

OK

In:    serial

Out:   serial

Err:   serial

 

 BuildInfo:

  - ATF 63a678c

 

auto-detected panel ltk080a60a004t

Display: mipi:ltk080a60a004t (1200x1920)

Net:   AR8035 at 4

FEC [PRIME], usb_ether

Hit any key to stop autoboot:  0

=> ums mmc 0

UMS: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x1d34000 /EP2/out FAIL info=40000080 pg0=b7f68380 "Synchronous Abort" handler, esr 0x96000147

elr: 0000000040202718 lr : 0000000040245d20 (reloc)

elr: 00000000bff21718 lr : 00000000bff64d20

x0 : 0000000000108000 x1 : 00000000bffc0300

x2 : 0000000000000040 x3 : 000000000000003f

x4 : 0000000000000000 x5 : 0000000000000000

x6 : 00000000b7f4e640 x7 : 0000000000004000

x8 : 00000000b7f908c0 x9 : 0000000000000008

x10: 000000000000000d x11: 0000000000000006

x12: 000000000001869f x13: 000000000000000c

x14: 0000000000000006 x15: 00000000ffffffff

x16: 0000000000002080 x17: 00000000000041a0

x18: 00000000b7f1ede0 x19: 00000000bffc6000

x20: 00000000bffc6c20 x21: 0000000000000000

x22: 00000000bffc6bd8 x23: 0000000000000002

x24: 00000000b7f4ea70 x25: 00000000bffc6c20

x26: 0000000000010004 x27: 00000000bffc6bd8

x28: 00000000bffc0318 x29: 00000000b7f17a90

 

Code: d2800082 9ac32042 d1000443 8a230000 (d5087620) Resetting CPU ...

 

resetting ...

 

U-Boot SPL 2020.10-52351-g1d495e1c1d (Jan 05 2021 - 09:36:34 -0800) config to do 3000 1d training.

config to do 3000 2d training.

config to do 400 1d training.

config to do 100 1d training.

Normal Boot

Trying to boot from MMC1

NOTICE:  BL31: v2.2(release):rel_imx_5.4.47_2.2.0-11-g63a678c3f

NOTICE:  BL31: Built : 15:04:40, Jan  4 2021

 

 

U-Boot 2020.10-52351-g1d495e1c1d (Jan 05 2021 - 09:36:34 -0800), Build: jenkins-uboot_v2020.10-30

 

CPU:   i.MX8MMQ rev1.0 at 1200 MHz

Reset cause: POR

Model: Boundary Devices i.MX8MMini Nitrogen8MM Som

Board: nitrogen8mm_som

       Watchdog enabled

DRAM:  2 GiB

MMC:   FSL_SDHC: 0, FSL_SDHC: 1

Loading Environment from MMC...

OK

In:    serial

Out:   serial

Err:   serial

 

 BuildInfo:

  - ATF 63a678c

 

auto-detected panel ltk080a60a004t

Display: mipi:ltk080a60a004t (1200x1920)

Net:   AR8035 at 4

FEC [PRIME], usb_ether

Hit any key to stop autoboot:  0

 

0 Kudos
1 Reply

136 Views
igorpadykov
NXP TechSupport
NXP TechSupport

Hi gilmotta

 

may be recommended to upgrade/rebuild both uboot/linux to latest versions using

boundary devices (vendor of Nitrogen8MM Som boards) blogs:

https://boundarydevices.com/blog/

https://boundarydevices.com/yocto-release-for-i-mx-8mm/

 

Best regards
igor

0 Kudos