[nitrogen6x-uc18] Need update uboot env and then can enter to core image (bad CRC)

Bug #1853395 reported by Betty Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Fisterra project
In Progress
Critical
ethan.hsieh
Hwe-fisterra
New
Undecided
Shrirang Bagul
Nitrogen6x-uc18
In Progress
Critical
ethan.hsieh

Bug Description

Image: nitrogen6x-uc-2019-11-13-123.img
CID: 201908-27262

Description:
Need update uboot env and then can enter to core image

The logs when can't enter to core image:
U-Boot 2018.07-rc3+dfsg1-0ubuntu3~18.04.1~hwe6 (Aug 16 2019 - 03:37:12 +0000)

CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: Nitrogen6X
I2C: ready
DRAM: 2 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

Failed (-5)
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Failed (-5)
auto-detected panel HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net: using phy at 6
FEC [PRIME], usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
0 bytes read in 8 ms (0 Bytes/s)
## Executing script at 12000000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
** Unable to read file / **
MMC: no card present
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part
No port device detected!

Device 0: Model: Firm: Ser#:
            Type: Hard Disk
            Capacity: not available
... is now current device
timeout exit!
timeout exit!
timeout exit!

Update uboot env by following command can enter to core image:
$ fatload mmc 0:1 0x13000000 uboot.env;env import 0x13000000;env save;reset

Related branches

Betty Lin (bettyl)
Changed in fisterra:
assignee: nobody → ethan.hsieh (ethan.hsieh)
Revision history for this message
ethan.hsieh (ethan.hsieh) wrote :

Next action: Try latest U-Boot. If the issue is still reproducible, file a public bug

Changed in fisterra:
status: New → Confirmed
status: Confirmed → In Progress
Revision history for this message
ethan.hsieh (ethan.hsieh) wrote :

The patch[1] in bionic u-boot enables SYS_REDUNDAND_ENVIRONMENT.
But, we still need following two patches[2].

commit a09fea1d28fe3c69a64bee092f5a764274d26ca2
Author: Tom Rini <email address hidden>
Date: Mon Nov 18 20:02:10 2019 -0500
    env: Finish migration of common ENV options

commit cb6617a77f81df47b72cc4115faf7bd5b1f7cfeb
Author: Tom Rini <email address hidden>
Date: Sun Nov 10 11:28:03 2019 -0500
    defconfigs: Migrate CONFIG_SYS_REDUNDAND_ENVIRONMENT

---
[1] Enable Ubuntu support for the Nitrogen6x board (LP: #1838064), https://git.launchpad.net/ubuntu/+source/u-boot/commit/?h=ubuntu/cosmic-proposed&id=555d5d9b8513e278548c9a892fda793e52e8bfe3
[2] git://git.denx.de/u-boot.git
[3] https://git.launchpad.net/ubuntu/+source/u-boot/

summary: [nitrogen6x-uc18] Need update uboot env and then can enter to core image
+ (bad CRC)
description: updated
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.