Hi everyone,
I am working with a product that has an am335x ARM CPU and runs a Linux OS. The entire product image is built with buildroot and includes U-Boot, Linux kernel and our application. The Linux kernel that has been used until now is version 3.2.25, but now we are going to replace the WiFi module and the Linux kernel is to old. I have upgraded Linux to version 5.10 but now the Linux kernel does not boot. After the print "Starting kernel ..." nothing happens.
It feels like it is due to this error that I see during FW update:
mount: mounting /dev/mmcblk0p4 on /mnt/storage failed: Invalid argument
Can it be that I have missed some pin configuration or any specific configuration needed for our CPU? Any help is appreciated.
Below is prints during start and also during FW update.
Start up
---------
U-Boot SPL 2018.11-rc1 (May 22 2022 - 20:12:58 +0000)
Trying to boot from MMC2
U-Boot 2018.11-rc1 (May 22 2022 - 20:12:58 +0000)
CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from MMC... OK
Saving Environment to MMC... Writing to MMC(1)... OK
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 13
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
3559384 bytes read in 349 ms (9.7 MiB/s)
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-5.10.114
Created: 2022-05-25 13:55:23 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3559320 Bytes = 3.4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
Starting kernel ...
During FW upgrade with new Linux kernel I got this message:
--------------------------------------------------------------------
CURRENT BAUD1: 115200
CURRENT BAUD2: 115200
Starting logging: OK
Starting mdev...
Initializing random number generator... done.
Starting system message bus: done
Starting network...
Starting connman ... done.
Starting network time protocol daemon: ntpd.
EXT3-fs (mmcblk0p4): error: unable to read superblock
EXT2-fs (mmcblk0p4): error: unable to read superblock
mount: mounting /dev/mmcblk0p4 on /mnt/storage failed: Invalid argument
Starting SWUpdate
Start production loader...
Swupdate v2018.11.0
Licensed under GPLv2. See source distribution for detailed copyright notices.
fbv - The Framebuffer Viewer
/etc/flashing-status-images/programming.jpg
480 x 272
Error opening /mnt/storage/publicSignedImageKey.pem
[ERROR] : SWUPDATE failed [0] ERROR : unable to load key filename /mnt/storage/publicSignedImageKey.pem
[ERROR] : SWUPDATE failed [0] ERROR : Error loading pub key from /mnt/storage/publicSignedImageKey.pem
Crypto cannot be initialized
Thanks,
Ann
I am working with a product that has an am335x ARM CPU and runs a Linux OS. The entire product image is built with buildroot and includes U-Boot, Linux kernel and our application. The Linux kernel that has been used until now is version 3.2.25, but now we are going to replace the WiFi module and the Linux kernel is to old. I have upgraded Linux to version 5.10 but now the Linux kernel does not boot. After the print "Starting kernel ..." nothing happens.
It feels like it is due to this error that I see during FW update:
mount: mounting /dev/mmcblk0p4 on /mnt/storage failed: Invalid argument
Can it be that I have missed some pin configuration or any specific configuration needed for our CPU? Any help is appreciated.
Below is prints during start and also during FW update.
Start up
---------
U-Boot SPL 2018.11-rc1 (May 22 2022 - 20:12:58 +0000)
Trying to boot from MMC2
U-Boot 2018.11-rc1 (May 22 2022 - 20:12:58 +0000)
CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from MMC... OK
Saving Environment to MMC... Writing to MMC(1)... OK
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 13
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
3559384 bytes read in 349 ms (9.7 MiB/s)
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-5.10.114
Created: 2022-05-25 13:55:23 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3559320 Bytes = 3.4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
Starting kernel ...
During FW upgrade with new Linux kernel I got this message:
--------------------------------------------------------------------
CURRENT BAUD1: 115200
CURRENT BAUD2: 115200
Starting logging: OK
Starting mdev...
Initializing random number generator... done.
Starting system message bus: done
Starting network...
Starting connman ... done.
Starting network time protocol daemon: ntpd.
EXT3-fs (mmcblk0p4): error: unable to read superblock
EXT2-fs (mmcblk0p4): error: unable to read superblock
mount: mounting /dev/mmcblk0p4 on /mnt/storage failed: Invalid argument
Starting SWUpdate
Start production loader...
Swupdate v2018.11.0
Licensed under GPLv2. See source distribution for detailed copyright notices.
fbv - The Framebuffer Viewer
/etc/flashing-status-images/programming.jpg
480 x 272
Error opening /mnt/storage/publicSignedImageKey.pem
[ERROR] : SWUPDATE failed [0] ERROR : unable to load key filename /mnt/storage/publicSignedImageKey.pem
[ERROR] : SWUPDATE failed [0] ERROR : Error loading pub key from /mnt/storage/publicSignedImageKey.pem
Crypto cannot be initialized
Thanks,
Ann
