topic Re: Read verification error in Serial Flash in i.MX Processors

Read verification error in Serial Flash

peteramond — Thu, 22 Jun 2017 07:37:16 GMT

Hi All,

This is regarding iMX6Q, SST26VF032B Serial Flash base custom board design and following error message shows on console (Red highlighted in log file) while doing the run upgradeu.

Total of 0 byte(s) were the same
Read verification error

In order to configure the SPI Flash and RAM I have done all the changes related to DDR calibration values in .cfg file and SPI flash configurations in spi param.c file.

{"SST26VF032B", 0xbf2642, 0x0, 64 * 1024, 64, RD_NORM, SECT_4K},

Could you please tell me the reason for this issue ? Any idea regarding this ?

Console log file --------

U-Boot 2016.03-20600-g0dbffd3-dirty (Jun 21 2017 - 13:29:09 +0100) base custom board design

CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: Nitrogen6_max
I2C: ready
DRAM: 2 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
SF: Detected SST26VF032B with page size 256 Bytes, erase size 4 KiB, total 4 MiB
*** Warning - bad CRC, using default environment

Display: hdmi:1280x720M@60 (1280x720)
In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Error: FEC address not set.

Hit any key to stop autoboot: 0
=> run upgradeu
AHCI 0000.0000 1 slots 1 ports ? Gbps 0x0 impl SATA mode
flags:
No port device detected!
** Bad device size - sata 0 **
switch to partitions #0, OK
mmc0 is current device
1808 bytes read in 37 ms (46.9 KiB/s)
## Executing script at 10008000
check U-Boot
490496 bytes read in 159 ms (2.9 MiB/s)
read 77c00 bytes from SD card
SF: Detected SST26VF032B with page size 256 Bytes, erase size 4 KiB, total 4 MiB
probed SPI ROM
device 0 offset 0x400, size 0x77c00
SF: 490496 bytes @ 0x400 Read: OK
byte at 0x12000000 (0xd1) != byte at 0x12400000 (0xff)
Total of 0 byte(s) were the same
Need U-Boot upgrade
Program in 5 seconds
5
4
3
2
1
erasing
SF: 786432 bytes @ 0x0 Erased: OK
programming
device 0 offset 0x400, size 0x77c00
SF: 490496 bytes @ 0x400 Written: OK
verifying
device 0 offset 0x400, size 0x77c00
SF: 490496 bytes @ 0x400 Read: OK
byte at 0x12000000 (0xd1) != byte at 0x12400000 (0xff)
Total of 0 byte(s) were the same
Read verification error
timeout irqstat=10000
timeout irqstat=10000
switch to partitions #0, OK
mmc1(part 0) is current device
** No partition table - mmc 1 **
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1: USB EHCI 1.00
scanning bus 1 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
scanning usb for ethernet devices... 0 Ethernet Device(s) found

USB device 0: unknown device
** Bad device usb 0 **

Regards,

Peter.

Re: Read verification error in Serial Flash

igorpadykov — Thu, 22 Jun 2017 23:12:40 GMT

Hi Peter

upgradeu was developed by BD and one can look at its sources:

https://boundarydevices.com/switching-u-boot-versions-on-i-mx6/
https://boundarydevices.com/compiling-latest-u-boot-for-i-mx6-2015-edition/

seems data is not written correctly to flash.

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Read verification error in Serial Flash

peteramond — Sat, 24 Jun 2017 06:10:18 GMT

Hi igorpadykov,

Now the custom boot from flash correctly and when it start the kernel shows the following error messages.

I have done the changes to all the imx6qdl.dtsi, imx6qd.dtsi and etc files and compiled and generated the dtb file as well. Could you please tell me the reason for following error messages.

----------- trying to load /initrd.img
6556084 bytes read in 637 ms (9.8 MiB/s)
5791064 bytes read in 663 ms (8.3 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x585d58 ]
## Flattened Device Tree blob at 13000000
Booting using the fdt blob at 0x13000000
reserving fdt memory region: addr=13000000 size=b000
Using Device Tree in place at 13000000, end 1300dfff

Starting kernel ...

imx6q-pinctrl 20e0000.iomuxc: Invalid fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/audmuxgrp
imx6q-pinctrl 20e0000.iomuxc: Invalid fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/hoggrp
imx6q-pinctrl 20e0000.iomuxc: Invalid fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/i2c1-sgtl5000grp
imx6q-pinctrl 20e0000.iomuxc: Invalid fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/i2c2muxgrp
imx6q-pinctrl 20e0000.iomuxc: Invalid fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/i2c3muxgrp
imx6q-pinctrl 20e0000.iomuxc: no fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/i2c3-ov5640grp
imx6q-pinctrl 20e0000.iomuxc: Invalid fsl,pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/iomuxc-imx6q-nitrogen6-maxgrp/reg-wlan-engrp
i2c-mux-gpio i2cmux@2: Missing mux-gpios property in the DT.
i2c-mux-gpio i2cmux@3: Missing mux-gpios property in the DT.
ldb 2000000.aips-bus:ldb@020e0008: failed to find valid LVDS channel
m25p80 spi0.0: unrecognized JEDEC id bytes: bf, 26, 42
imx-sgtl5000 sound: ASoC: CODEC DAI sgtl5000 not registered
imx-sgtl5000 sound: snd_soc_register_card failed (-517)

Regards,

Peter.