Hi, using imx7d 512M V1.1D : we have been using kernel 5.4.193 (from git … toradex_5.4-2.3.x-imx …) for some time and applied patches from kernel.org up to 5.4.199 then building and updating with ubiupdatevol /dev/ubi0_0 zImage. After ubiupdate ubinfo looks correct.
Problem is now that when updating with patches above 200 the following error at boot:
ubi0 error: scan_peb: bad sequence number xxxxxx in PEB 4, expected yyyyy
uboot enviroment is default from toradex easy installer
mtdparts:
4: ubi size 0x1fc00000 offset 0x00400000
We have tried different solutions from the community and general googling for hints.
(installing the zImage and dtb from easy installer produces same error)
What patches are you trying to apply? How many? Have you tried to narrow down if one or more patches specifically are causing the issue? Also, which OS are you using?
And here i must apologize for a bit of confusion.
The first problem that we have with the 5.4.202 build is UBIFS error (ubi0:3 pid 1): ubifs_recover_master_node: failed to recover master node
And then a kernel panic for the missing rootfs
The 202 patch has a small change to NAND but i cant see if that could cause the problem.
The u-boot problem shows up later, when we hoped the problem would disappear in a later patch.
Regards - Paul
-------------------------------------- image.json - when installing from easy installer ------------------------ image.json (2.6 KB)
-------------------------------------- console dump ---------------------------------------------------------------------------- ubierror.txt (4.7 KB)
By hacking drivers/usb/gadget/udc/core.c - usb_gadget_vbus_disconnect() function to check the pointers the symptom is cured - the background of the problem is still open …
From what I understood you were able to solve your initial rootfs problem, but now you’re having a problem related to USB. Is this correct?
I also noticed you’re using the 5.4 Downstream kernel from NXP. Is there any particular reason to use it? We have an upstream-based 5.4 we use for our iMX6 and iMX7 images (BSP 5 reference images and Torizon OS 5):
Hi Lucas,
the USB was our initial problem and the reason we started patching 5.4.19x
For now we “solved” the USB problem by modifying drivers/usb/gadget/udc/core.c - usb_gadget_vbus_disconnect() function – at least until there may be comes a patch.
We assumed that the downstream was the most stable, and comming from the toradex git repo that it was good for toradex modules and its longterm support until dec. 2025. On top of that it had good binary compatibility with our previous platform running 4.19.xx on a cortex-A5.
OK, so you managed to solve the problems you were having, at least for now.
We assumed that the downstream was the most stable, and comming from the toradex git repo that it was good for toradex modules and its longterm support until dec. 2025. On top of that it had good binary compatibility with our previous platform running 4.19.xx on a cortex-A5.
It’s a valid point. For our iMX6 and iMX7 SoMs we offer both the downstream and the upstream-based kernel 5.4 for our BSP 5 reference images, so we will support those until BSP 5 reaches EOL.
and its longterm support until dec. 2025. On top of that it had good binary compatibility with our previous platform running 4.19.xx on a cortex-A5.