Skip to content

ARM: imx: Update Novena to DM/DT

Vagrant Cascadian u-boot 3 versions – In review

Get series with b4
b4 am 87a7c3ka3z.fsf@ponder

Versions newest first · linked by author and title

  1. v2 Latest posting 3/30 of 7 patches 2 repliesIn review
  2. v2 posting 2/30 of 7 patches 0 repliesSuperseded
  3. v2 posting 1/30 of 7 patches 0 repliesSuperseded

Patches in v2 posting 3/3 No applies recorded yet

None of the 7 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [U-Boot] [PATCH V2 0/7] ARM: imx: Update Novena to DM/DT
Quoted 3 lines · Marek Vasut
Quoted 2 lines · Vagrant Cascadian
Quoted 1 line · Marek Vasut

Update Kosagi Novena to DM / DT and remove the warnings.

...

Quoted 17 lines
Quoted 17 lines

I have two oustanding issues... with some files it sometimes fails to load one or more from SATA:

Retrieving file: /boot/initrd.img-5.0.0-trunk-armmp
20077960 bytes read in 375 ms (51.1 MiB/s)
Retrieving file: /boot/vmlinuz-5.0.0-trunk-armmp
4215296 bytes read in 40 ms (100.5 MiB/s)
append: root=UUID=9666ab0b-f932-4e2f-95d7-0e96a12a4540 ro quiet Retrieving file: /usr/lib/linux-image-5.0.0-trunk-armmp/imx6q-novena.dtb
CACHE: Misaligned operation at range [fafb5398, fafb6398]
CACHE: Misaligned operation at range [fafb5398, fafb6398]
ERROR: v7_outer_cache_inval_range - start address is not aligned - 0xfafb5398
ERROR: v7_outer_cache_inval_range - stop address is not aligned - 0xfafb6398
invalid extent block

Quoted 7 lines
Quoted 5 lines

It then falls back to one of the other kernels (using the extlinux.conf parsing) and succeeds. It consistantly gets a cache/alignment error with this specific file. A bit-for-bit identical .dtb loaded from another path works just fine. Older versions of u-boot boot this fine. Would some particular EXT4 flag possibly be causing issues?

I don't know. Do you still run into this with u-boot/master ?

Still occurring with 2019.10-rc2. Haven't tested with master yet.

Using "dcache off" before booting still outputs the CACHE and ERROR messages, but does successfully boot.

Quoted 15 lines
Quoted 15 lines

The second issue is still using one out of four exposed USB ports fails and resets the board:

load usb 0:1 $kernel_addr_r misc/Binaries/linux/Image data abort

pc : [<fefbb67a>]          lr : [<fefbb0fd>]

reloc pc : [<1783367a>] lr : [<178330fd>]
sp : faf7c6e8 ip : 00000003 fp : 00000005
r10: faf8b200 r9 : faf87ea0 r8 : 00000001
r7 : faf8b2c0 r6 : f9f7a040 r5 : faf7c710 r4 : 00000038
r3 : 0000006d r2 : f9f7a0a3 r1 : faf8b32c r0 : f9f7a09f
Flags: nzCv IRQs off FIQs off Mode SVC_32

Code: 4630fc5b 81f0e8bd e7d84606 bf082b2f (f822235c)

Resetting CPU ...

Quoted 5 lines
Quoted 2 lines

The three other usb ports work just fine with the same USB stick and file. All four ports work with 2019.01.

Can you debug it ? I think some of this was due to the EFI stuff , which I think was fixed since. Can you re-check that ?

USB appears to be working fine with 2019.10-rc2.

live well,
vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190820/f9476fa2/attachment.sig>