- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#51
A20 / Re: cannot boot from emmc
Last post by aleix - July 01, 2024, 11:15:53 PMNarrowed down the step at which it stops booting. After apt update & upgrade it boots fine. Then this is installed:
And after installing this, and rebooting, the problem appears.
The first line of discrepancy before and after the problem is
Also tried installing the same packages without apt upgrade, and same problem. These packages lead to this:
Perhaps this linux image is the culprit?
Code Select
# apt install curl ufw wireguard-tools sox alsa-utils opus-tools rsync
And after installing this, and rebooting, the problem appears.
The first line of discrepancy before and after the problem is
Code Select
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
Also tried installing the same packages without apt upgrade, and same problem. These packages lead to this:
Code Select
Selecting previously unselected package linux-image-5.10.0-30-rt-armmp.
Preparing to unpack .../08-linux-image-5.10.0-30-rt-armmp_5.10.218-1_armhf.deb ...
Unpacking linux-image-5.10.0-30-rt-armmp (5.10.218-1) ...
Selecting previously unselected package linux-image-rt-armmp.
Preparing to unpack .../09-linux-image-rt-armmp_5.10.218-1_armhf.deb ...
Unpacking linux-image-rt-armmp (5.10.218-1) ...
Perhaps this linux image is the culprit?
#52
A20 / cannot boot from emmc [SOLVED]
Last post by aleix - July 01, 2024, 10:10:34 PMHello,
Board: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.L
Installed OS: official image from https://images.olimex.com/release/a20/
Once it is installed through a microSD card, this command is used:
Everything works fine and the OS is booted from emmc.
Then, a few packages are installed (after apt update & upgrade), a firewall is set and root account is disabled (passwd -l root and nologin from /etc/passwd).
Then, when rebooting, cannot boot anymore, and the same behaviour is tested on three identical boards.
This is the the output:
Would appreciate any help.
Thanks
Board: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.L
Installed OS: official image from https://images.olimex.com/release/a20/
Once it is installed through a microSD card, this command is used:
Code Select
olinuxino-sd-to-emmc
Everything works fine and the OS is booted from emmc.
Then, a few packages are installed (after apt update & upgrade), a firewall is set and root account is disabled (passwd -l root and nologin from /etc/passwd).
Then, when rebooting, cannot boot anymore, and the same behaviour is tested on three identical boards.
This is the the output:
Code Select
U-Boot SPL 2021.04+olimex-1-20231103.141125 (Nov 03 2023 - 14:12:28 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Loading configuration from EEPROM: OK
Verifying data: OK
Trying to boot from MMC2
U-Boot 2021.04+olimex-1-20231103.141125 (Nov 03 2023 - 14:12:28 +0000) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
ID: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.L
SN: 00025829
MAC: 30:1F:9A:D1:36:BE
I2C: ready
DRAM: 1 GiB
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC: mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from EXT4... *** Warning - bad CRC, using default environment
Loading Environment from FAT... ** No device specified **
In: serial
Out: serial
Err: serial
Allwinner mUSB OTG (Peripheral)
Net: eth0: ethernet@1c50000, eth1: usb_ether
starting USB...
Bus usb@1c14000: USB EHCI 1.00
Bus usb@1c14400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c14000 for devices... 1 USB Device(s) found
scanning bus usb@1c14400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2274 bytes read in 2 ms (1.1 MiB/s)
## Executing script at 43100000
Boot script loaded from mmc
Checking for /uEnv.txt...
Checking for /boot/uEnv.txt...
1156 bytes read in 1 ms (1.1 MiB/s)
Loaded environment from /boot/uEnv.txt
Loading FIT image...
29502207 bytes read in 1611 ms (17.5 MiB/s)
## Loading kernel from FIT Image at 58000000 ...
Using 'config-9243' configuration
Trying 'kernel-1' kernel subimage
Description: Linux kernel 5.10.0-30-rt-armmp
Type: Kernel Image
Compression: uncompressed
Data Start: 0x580000d4
Data Size: 5050880 Bytes = 4.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x40080000
Entry Point: 0x40080000
Hash algo: crc32
Hash value: 65d19ea1
Hash algo: sha1
Hash value: a27f53b86204312d87ebfc878360ffdd422ff938
Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading ramdisk from FIT Image at 58000000 ...
Using 'config-9243' configuration
Trying 'ramdisk-1' ramdisk subimage
Description: Ramdisk for kernel 5.10.0-30-rt-armmp
Type: RAMDisk Image
Compression: Unknown Compression
Data Start: 0x584d140c
Data Size: 24164998 Bytes = 23 MiB
Architecture: ARM
OS: Linux
Load Address: 0x4fe00000
Entry Point: 0x4fe00000
Hash algo: crc32
Hash value: 219c745e
Hash algo: sha1
Hash value: cc65dc7beda697ff7c2bc9111557f32bff2819fe
Verifying Hash Integrity ... crc32+ sha1+ OK
Loading ramdisk from 0x584d140c to 0x4fe00000
WARNING: 'compression' nodes for ramdisks are deprecated, please fix your .its file!
## Loading fdt from FIT Image at 58000000 ...
Using 'config-9243' configuration
Trying 'fdt-4' fdt subimage
Description: unavailable
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x59befbc8
Data Size: 26587 Bytes = 26 KiB
Architecture: ARM
Load Address: 0x4fa00000
Hash algo: crc32
Hash value: f5ec9034
Hash algo: sha1
Hash value: 4db0e46ea10ec1b5b306e7881dc999f4003045c9
Verifying Hash Integrity ... crc32+ sha1+ OK
Loading fdt from 0x59befbc8 to 0x4fa00000
## Loading fdt from FIT Image at 58000000 ...
Trying 'overlay-1' fdt subimage
Description: unavailable
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x59c1ee24
Data Size: 1001 Bytes = 1001 Bytes
Architecture: ARM
Load Address: 0x4fa10000
Hash algo: crc32
Hash value: d1d51f29
Hash algo: sha1
Hash value: fa0c14efb55dbe4bdf8aa7241a3e600b486e3ef6
Verifying Hash Integrity ... crc32+ sha1+ OK
Loading fdt from 0x59c1ee24 to 0x4fa10000
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
base fdt does did not have a /__symbols__ node
make sure you've compiled with -@
Could not find a valid device tree
SCRIPT FAILED: continuing...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Card did not respond to voltage select! : -110
Scanning disk mmc@1c0f000.blk...
Disk mmc@1c0f000.blk not ready
Scanning disk mmc@1c11000.blk...
Found 2 disks
No EFI system partition
Applying overlay: '/usr/lib/olinuxino-overlays/sun7i-a20/spi1-spidev.dtbo'...
408 bytes read in 5 ms (79.1 KiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Failed to apply overlay.
Restoring the original FDT blob...
BootOrder not defined
EFI boot manager: Cannot load any image
Card did not respond to voltage select! : -110
scanning bus for devices...
SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Device 0: unknown device
Device 0: unknown device
ethernet@1c50000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@1c50000
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC de:ad:be:ef:00:01
HOST MAC de:ad:be:ef:00:00
RNDIS ready
The remote end did not respond in time.missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-30-1f-9a-d1-36-be
ethernet@1c50000 Waiting for PHY auto negotiation to complete...
Code Select
=> mmcinfo
Device: mmc@1c11000
Manufacturer ID: 13
OEM: 14e
Name: Q2J55
Bus Speed: 52000000
Mode: MMC High Speed (52MHz)
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 7.1 GiB
Bus Width: 4-bit
Erase Group Size: 512 KiB
HC WP Group Size: 8 MiB
User Capacity: 7.1 GiB WRREL
Boot Capacity: 16 MiB ENH
RPMB Capacity: 4 MiB ENH
Boot area 0 is not write protected
Boot area 1 is not write protected
Would appreciate any help.
Thanks
#53
A20 / Re: A20-SOM with Li-Ion withou...
Last post by mavstuff - July 01, 2024, 06:05:58 PMThanks for the information. I am using external 7A BMS curcuit currently
#54
NXP / Re: Debugging IMX8MP SOM boot
Last post by LubOlimex - July 01, 2024, 04:52:39 PMYeah I just checked "Table 6-1. Boot MODE pin settings" (from chapter "Chapter 6 SNVS, Reset, Fuse, and Boot") of the "IMX8MPRM.pdf" and it seems the same as the back of the board.
Why the board boots off SD card when set to 1-0-1-0, probably some fallback if selected mode fails.
Why the board boots off SD card when set to 1-0-1-0, probably some fallback if selected mode fails.
#55
NXP / Re: Debugging IMX8MP SOM boot
Last post by thj - July 01, 2024, 04:18:06 PMThe table on the back seems matches with my reading of the datasheet.
The datasheet says that if all boot modes fail I should end up with the board in usb serial mode, I don't think my XHCI debug cable should work (https://www.datapro.net/products/usb-3-0-super-speed-a-a-debugging-cable.html) and I have to make one to test this mode.
I'll play with the switches and the image. It would be helpful if the ROM output anything on serial when it can't boot, but I don't read anything like that in the soc datasheet
The datasheet says that if all boot modes fail I should end up with the board in usb serial mode, I don't think my XHCI debug cable should work (https://www.datapro.net/products/usb-3-0-super-speed-a-a-debugging-cable.html) and I have to make one to test this mode.
I'll play with the switches and the image. It would be helpful if the ROM output anything on serial when it can't boot, but I don't read anything like that in the soc datasheet
#56
NXP / Re: Debugging IMX8MP SOM boot
Last post by LubOlimex - July 01, 2024, 03:10:19 PMYes, the default mode is ON, OFF, ON, OFF this is booting from SD card. I will investigate the table at the back I suspect it is not good.
#57
A10 / Re: Missing file operations du...
Last post by Navaneeth - July 01, 2024, 01:52:19 PMYes I understand your point.
Have two questions.
1) dirty_writeback_centisecs, dirty_expire_centisecs why these settings are not working?.
2) how much time it will take for typical shutdown?. Is there any pin which can trigger automatic shutdown?.
Have two questions.
1) dirty_writeback_centisecs, dirty_expire_centisecs why these settings are not working?.
2) how much time it will take for typical shutdown?. Is there any pin which can trigger automatic shutdown?.
#58
A20 / Re: A20 board problem if a bac...
Last post by LubOlimex - July 01, 2024, 09:03:17 AMDo you have only the battery applied as power source to the board when you try to boot? Consider that you might need to hold the PWR button to start the board when only battery is present.
Consider that the battery might be very big and discharged and your main power supply might be unsuitable for that draw of board + discharged battery. Try with better main power supply (with more current available, thus bigger wattage). Maybe try with smaller battery.
If it is not that, please give us more details, like what sort of battery do you use and where is it applied?
Usually people use Li-Po batteries like these:
https://www.olimex.com/Products/Power/Lipo-battery/
Consider that the battery might be very big and discharged and your main power supply might be unsuitable for that draw of board + discharged battery. Try with better main power supply (with more current available, thus bigger wattage). Maybe try with smaller battery.
If it is not that, please give us more details, like what sort of battery do you use and where is it applied?
Usually people use Li-Po batteries like these:
https://www.olimex.com/Products/Power/Lipo-battery/
#59
A20 / Re: A20-SOM with Li-Ion withou...
Last post by LubOlimex - July 01, 2024, 08:52:09 AMIt is not a good idea. My experience shows that it is dangerous. Most Li-Po batteries should have some sort of undervoltage or overvoltage protection (unless you stripped it). Here is a battery controller (stripped from one of our Li-Po batteries):
When picking a battery consider something like these (in some of the pictures you can see the controller):
https://www.olimex.com/Products/Power/Lipo-battery/
When picking a battery consider something like these (in some of the pictures you can see the controller):
https://www.olimex.com/Products/Power/Lipo-battery/
#60
NXP / Debugging IMX8MP SOM boot
Last post by thj - June 30, 2024, 10:20:29 PMI have the imx8mp SOM and EVB, the other day I got buildroot-202405212131.img booting on the board the other day and I was successfully able to connect on the network and pull a dmesg off the board.
Returning to board today I'm not able to get the board to boot, I managed twice to get an error from spl, but without any consistency.
I got this error after pulling out the SD card:
The boot switches on delivery were set to NAND 8-BIT 512 Pages (1010).
I have tried setting them to SD card (1100) and USB Serial Download (1000) with a XHCI debug cable attached and 4 different SD cards, but none of these options let me boot.
I have a tigard ftdi device attached to A53_DBG1 at 115200 which I could use for terminal access before.
I'm not sure what to try get. I have verified the voltages are correct on the test points on the SOM. When in NAND boot the sys_status led illuminates which it did when I could boot successfully.
I can add a jtag header, but I'd prefer other steps before soldering to the evb.
Returning to board today I'm not able to get the board to boot, I managed twice to get an error from spl, but without any consistency.
I got this error after pulling out the SD card:
Code Select
U-Boot SPL 2020.04 (May 21 2024 - 18:08:43 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0
ROMAPI: download failure offset 0x60000 size 0x200
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
The boot switches on delivery were set to NAND 8-BIT 512 Pages (1010).
I have tried setting them to SD card (1100) and USB Serial Download (1000) with a XHCI debug cable attached and 4 different SD cards, but none of these options let me boot.
I have a tigard ftdi device attached to A53_DBG1 at 115200 which I could use for terminal access before.
I'm not sure what to try get. I have verified the voltages are correct on the test points on the SOM. When in NAND boot the sys_status led illuminates which it did when I could boot successfully.
I can add a jtag header, but I'd prefer other steps before soldering to the evb.