Open alberanid opened 5 years ago
@alberanid, We've had the same issue with an imx6ull and nand storage as well. Were you able to resolve this issue?
@jmistr01 nope, sorry.
On top of this (but probably unrelated) we are facing a reliability issue on i.MX6ULL on NAND which may or may not be related to what kobs-ng writes on it (especially in regards of BCH code). More info here, since you may also be affected, even if you use a different kind of NAND:
I've seen your issue #23 and I'd double check if in your case is ok to have BCHType set to 0, since from what I understand it means no BCH error correction for you, leaving you exposed to bitflips.
@jmistr01 please ignore the part on BCHType, since it's ok to be 0; the important parameter is BCH Strength, which is 8 for you (should be ok on a small NAND, I guess)
Hi We are using a IMX8DXP based board and i am facing the same issue of finger print mismatch when i run kobs-ng update. Have you been able to resolve the above issue? Do you have any workaround or solution.
Thanks V.Muthusubramanian
@vmuthusu no, and we no longer need it so we stopped investigating, sorry.
NXP confirmed that kobs-ng does not fully support newer bootroms. Therefore, it can write the images correctly, but it can't read them back properly. For more details, please refer to this thread. I developed a dirty hack to fix this issue for to the i.MX6SoloX's bootrom.
By the way, I still have not understood if there is an official kobs-ng version supporting all the bootrom versions out there.
@am-dev-75 Hi, Would you be willing to share that patch (or "dirty hack" :) ) ?
a workaround to dump boot structure and update the firmware 2 only. Refer to https://github.com/allenxh/imx-kobs/tree/partial_update
These changes won't merge to mainline code.
Hi, We get an error using the "dump", "imgverify" and "extract" commands (latest version from this repository) on an imx6ull.
We succesfully flashed u-boot with this command:
kobs-ng init -x -v --chip_0_device_path=/dev/mtd0 u-boot.imx
Now we'd like to dump the loader to verify its integrity (we are investigating some cases of NAND corruption).
The error running the "dump" command:
Same error also adding the
-x --chip_0_device_path=/dev/mtd0
arguments.Any help will be greatly appreciated.