Are there any improvemens of devkit? I mean, on the time when it was sent to clients basically nothing was working, difficoult to develop something using “devkit”. Does the situation changed? Any updates?
Where the matrix devkit channel gone? Thank You.
Check the news area. There were several updates, including videos with kit-to-kit phone calls.
1 Like
I’d love to get my hands on one…
Today i wanted to recover my devkit and ended in a bootloop:
U-Boot SPL 2019.04-g6fc5b2293e (Sep 08 2021 - 06:53:04 -0700)
power_bd71837_init
DDRINFO: start DRAM init
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC1
Initializing FSL USDHC port 0
Initializing FSL USDHC port 1
U-Boot 2019.04-g6fc5b2293e (Sep 08 2021 - 06:53:04 -0700), Build: jenkins-u-boot_builds-uboot_devkit_build-94
CPU: Freescale i.MX8MQ rev2.0 1500 MHz (running at 1000 MHz)
CPU: Commercial temperature grade (0C to 95C) at 30C
Reset cause: POR
Model: Librem 5 DevKit i.MX8M SOM LPDDR4-1600
DRAM: 3 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x52]
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
BuildInfo:
- ATF 1fd3ff8
- U-Boot 2019.04-g6fc5b2293e
flash target is MMC:0
Net:
Warning: ethernet@30be0000 (eth0) using random MAC address - 3e:e5:0f:d0:96:7e
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2328 bytes read in 3 ms (757.8 KiB/s)
## Executing script at 80000000
8677959 bytes read in 204 ms (40.6 MiB/s)
46324 bytes read in 18 ms (2.5 MiB/s)
18954193 bytes read in 407 ms (44.4 MiB/s)
Booting Debian 5.13.0-1-librem5 from mmc 0:1...
Bad Linux ARM64 Image magic!
24211464 bytes read in 516 ms (44.7 MiB/s)
46324 bytes read in 19 ms (2.3 MiB/s)
18954193 bytes read in 408 ms (44.3 MiB/s)
Booting Debian from mmc 0:1...
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Loading Ramdisk to fe316000, end ff5297d1 ... OK
Loading Device Tree to 00000000fe307000, end 00000000fe3154f3 ... OK
Starting kernel ...
[ 0.049116] debugfs: Directory 'dummy-syscon@30340000' with parent 'regmap' already present!
[ 0.208080] debugfs: Directory 'dummy-reset-controller@30390000' with parent 'regmap' already present!
[ 0.380564] rtc-m41t80 0-0068: Oscillator failure, data is invalid.
[ 0.387867] rtc-m41t80 0-0068: Oscillator failure, data is invalid.
[ 0.394160] rtc-m41t80 0-0068: hctosys: unable to read the hardware clock
[ 1.217432] bq25890-charger 0-006b: Failed to register power supply
[ 1.245742] bq25890-charger 0-006b: Failed to register power supply
[ 1.313133] bq25890-charger 0-006b: Failed to register power supply
[ 1.340206] bq25890-charger 0-006b: Failed to register power supply
[ 1.769922] bq25890-charger 0-006b: Failed to register power supply
[ 2.225061] bq25890-charger 0-006b: Failed to register power supply
[ 9.085880] bq25890-charger 0-006b: Failed to register power supply
[ 9.192883] bq25890-charger 0-006b: Failed to register power supply
[ 9.226177] bq25890-charger 0-006b: Failed to register power supply
[ 9.264763] bq25890-charger 0-006b: Failed to register power supply
[ 9.281709] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a20000/usb-typec@52
␀␀
U-Boot SPL 2019.04-g6fc5b2293e (Sep 08 2021 - 06:53:04 -0700)
power_bd71837_init
DDRINFO: start DRAM init
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC1
Initializing FSL USDHC port 0
Initializing FSL USDHC port 1
U-Boot 2019.04-g6fc5b2293e (Sep 08 2021 - 06:53:04 -0700), Build: jenkins-u-boot_builds-uboot_devkit_build-94
CPU: Freescale i.MX8MQ rev2.0 1500 MHz (running at 1000 MHz)
CPU: Commercial temperature grade (0C to 95C) at 32C
Reset cause: POR
Model: Librem 5 DevKit i.MX8M SOM LPDDR4-1600
DRAM: 3 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C0 0x52]
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
BuildInfo:
- ATF 1fd3ff8
- U-Boot 2019.04-g6fc5b2293e
flash target is MMC:0
Net:
Warning: ethernet@30be0000 (eth0) using random MAC address - c2:57:45:4c:00:d8
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2328 bytes read in 4 ms (568.4 KiB/s)
## Executing script at 80000000
8677959 bytes read in 203 ms (40.8 MiB/s)
46324 bytes read in 18 ms (2.5 MiB/s)
18954193 bytes read in 407 ms (44.4 MiB/s)
Booting Debian 5.13.0-1-librem5 from mmc 0:1...
Bad Linux ARM64 Image magic!
24211464 bytes read in 515 ms (44.8 MiB/s)
46324 bytes read in 18 ms (2.5 MiB/s)
18954193 bytes read in 408 ms (44.3 MiB/s)
Booting Debian from mmc 0:1...
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Loading Ramdisk to fe316000, end ff5297d1 ... OK
Loading Device Tree to 00000000fe307000, end 00000000fe3154f3 ... OK
Starting kernel ...
[ 0.048522] debugfs: Directory 'dummy-syscon@30340000' with parent 'regmap' already present!
[ 0.203831] debugfs: Directory 'dummy-reset-controller@30390000' with parent 'regmap' already present!
[ 0.334729] rtc-m41t80 0-0068: Oscillator failure, data is invalid.
[ 0.342551] rtc-m41t80 0-0068: Oscillator failure, data is invalid.
[ 0.348862] rtc-m41t80 0-0068: hctosys: unable to read the hardware clock
[ 1.212866] bq25890-charger 0-006b: Failed to register power supply
[ 1.241475] bq25890-charger 0-006b: Failed to register power supply
[ 1.294582] bq25890-charger 0-006b: Failed to register power supply
[ 1.322816] bq25890-charger 0-006b: Failed to register power supply
[ 1.770863] bq25890-charger 0-006b: Failed to register power supply
[ 2.225103] bq25890-charger 0-006b: Failed to register power supply
i installed the kit with the command
scripts/librem5-flash-image --dir . --board devkit --download-attempts 0
everything looked fine but the board doesnt boot. any idea?
I guess that it is worth to download/extract again (latest/current package by extracting it within newly created folder):
git clone https://source.puri.sm/Librem5/librem5-flash-image.git
and use (instead of scripts/librem5-flash-image):
./scripts/librem5-devkit-flash-image --board devkit −− as already (basically) described here. Adding --variant plain or --variant luks would be optional (I guess again).