SPI NOR Flash on Odroid HC4

[duing]

How can we acces the SPI NOR Flash on Odroid HC4?

 

The usual error

seems to be the driver, not a thing we can overlay device tree? Id for xt25f128b is implemented.

Zitat

 

unrecognized JEDEC id 0

 

meson-spifc ffd14000.spi: registered host spi0
spi spi0.0: setup mode 0, 8 bits/w, 1000000 Hz max --> 0
spi-nor spi0.0: supply vcc not found, using dummy regulator
spi-nor spi0.0: error -95 reading JEDEC ID
spi-nor spi0.0: probe with driver spi-nor failed with error -95
meson-spifc ffd14000.spi: registered child spi0.0

 

Edited June 22 by duing

[duing]

I tried different overlays, reduced max-frequency, set rx-(-tx)-bus-width and different mode settings indepently. Is it perhaps driven by gpio regulator instead of fixed 3v3? With a vcc-supply property one line (warning) goes away.

Edited June 23 by duing

[duing]

I wanted to play with: kernel on ubifs or perhaps DAX on erofs.

 

The bootloader must be signed differently for SD and NOR flash with some kind of arm-trusted-firmware, a PC binary that can be started as binmisc under qemu in Linux on ARM.

Edited Wednesday at 07:07 PM by duing

[duing]

How do you write U-Boot to SPI NOR flash?

 

Without a working driver upstream, the best I can think of now is just using the shipped U-Boot/Linux (Petitboot from the manufactor). If you want to make it from source, use the shipped cross-compiler on 64 bit PC, perhaps on an archived OS, or rewrite Makefiles.

 

But that leaves the (for some tiny) 16 MB just for the bootloader, which doesn't even knows it's own bootdev. It seems the beforehand bootloader-loader doesn't look after SATA HDD, only SPI NOR or MMC SD. After all, just press a button to alternately load from removable card if one installed and failed to run from NOR.

 

Did I miss a thing in device-tree? The regulator-on.patch is upstream.

Edited 2 minutes ago by duing