- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#11
New Product Ideas / Re: ARM64 SOM for industrial a...
Last post by thom_nic - November 21, 2024, 12:51:47 AMHey thanks for the reply! I would consider the A64 SOC in a SOM form-factor. It's missing CAN support unfortunately but we could use a SPI or I2C to CAN chip. I see the A64 board is industrial temp rated which we need. We evaluated the A13-SOM but found it had poor thermal performance (and the A13 is not industrial temp rated anyway.)
If you released an A64-SOM I would definitely purchase a couple for evaluation.
If you released an A64-SOM I would definitely purchase a couple for evaluation.
#12
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by Titomax - November 20, 2024, 06:16:23 PMHi Lub,
I confirm that also using ID "10234" from "T2-SOM204-1Gs16Me8G-MC-I" all is working as expected.
As workaround for my issue I'll start using this procedure.
Thank you for your support.
I confirm that also using ID "10234" from "T2-SOM204-1Gs16Me8G-MC-I" all is working as expected.
As workaround for my issue I'll start using this procedure.
Thank you for your support.
#13
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by Titomax - November 20, 2024, 12:54:25 PMQuote from: LubOlimex on November 20, 2024, 12:04:47 PMBetter try with the ID of T2-SOM204-1Gs16Me8G-MC-I.
Ok, I didn't use "T2-SOM204-1Gs16Me8G-MC-I" because I thought that wasn't possible specify a configuration with a different hardware mounted.
Let's me try also with ID you suggested.
I'll give you a feedback.
#14
A20 / Re: virtual temperature measur...
Last post by LubOlimex - November 20, 2024, 12:34:59 PMThere is no true DAC (aka analog output) on Allwinner A20 chip, the only DAC is related to the audio but not sure if you can use it for task you want. I guess you need DAC for that task.
#15
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by LubOlimex - November 20, 2024, 12:04:47 PMBetter try with the ID of T2-SOM204-1Gs16Me8G-MC-I.
#16
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by LubOlimex - November 20, 2024, 12:03:45 PMThe problem is visible in the log - the board boot defaults to some generic config - this is pretty major problem.
The fast way to boot would probably be to try a workaround then, put some board that is nearly identical via the u-boot. Set is like the older board "T2-SOM204-1Gs16Me8G-MC-I". Do he following:
- run your Armbian image but interrupt u-boot
- type:
olinuxino config write 10234 C2 0002AC2C 30:1F:9A:D1:67:37
then type:
saveenv
then
reset
See if it boots.
The fast way to boot would probably be to try a workaround then, put some board that is nearly identical via the u-boot. Set is like the older board "T2-SOM204-1Gs16Me8G-MC-I". Do he following:
- run your Armbian image but interrupt u-boot
- type:
olinuxino config write 10234 C2 0002AC2C 30:1F:9A:D1:67:37
then type:
saveenv
then
reset
See if it boots.
#17
A20 / virtual temperature measuremen...
Last post by Hattes - November 20, 2024, 11:59:03 AMTarget is to use Lime2 as a "virtual temperature measurement" instead of real NTC to fool a heat pump. how to get analog output to Lime2 or other ideas how to make a virtual NTC?
#18
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by Titomax - November 20, 2024, 11:41:30 AMHi Lub,
just an update.
I modified EEPROM data from U-boot console using the command:
I set the info from my specified SOM module changing only the ID from 11462 to 8958 so that the SOM is now identified as "A20-SOM204-1Gs16Me16G-MC".
Now all is working as expected.
I put a system under test to see if malfunctions appear.
What kind of modifications are present on the U-boot or image switching from COMMERCIAL to INDUSTRIAL grade ID ?
Are there any driver specific modifications to support different grade IC ?
Please let me know if this approach can be used without encountering stability issues.
just an update.
I modified EEPROM data from U-boot console using the command:
Code Select
olinuxino config write 8958 c 11112222 aa:bb:cc:dd:ee:ffI set the info from my specified SOM module changing only the ID from 11462 to 8958 so that the SOM is now identified as "A20-SOM204-1Gs16Me16G-MC".
Now all is working as expected.
I put a system under test to see if malfunctions appear.
What kind of modifications are present on the U-boot or image switching from COMMERCIAL to INDUSTRIAL grade ID ?
Are there any driver specific modifications to support different grade IC ?
Please let me know if this approach can be used without encountering stability issues.
#19
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by Titomax - November 20, 2024, 10:31:46 AMHi Lub,
the system doesn't boot from the SD card.
The same SD card boots from the EVB but using the previous T2 board with 8GB eMMC.
The Armbian image we are using is using ID recognition and I verified that the ID for the T2 16 GB is missing.
We cannot touch the Armbian image. How can I make U-boot start correctly ?
Can I modify the EEPROM so that U-boot can recognize the board as a different one already managed ?
If I change the ID so the U-boot see the board as a "A20-SOM204-1Gs16Me16G-MC - 8958" ? May I encounter compatibility problem ?
See the output from the U-boot console using "olinuxino config list" command:
ARMBIAN IMAGE:
LATEST OFFICIAL IMAGE:
FAILED BOOT LOG FROM ARMBIAN IMAGE :
the system doesn't boot from the SD card.
The same SD card boots from the EVB but using the previous T2 board with 8GB eMMC.
The Armbian image we are using is using ID recognition and I verified that the ID for the T2 16 GB is missing.
We cannot touch the Armbian image. How can I make U-boot start correctly ?
Can I modify the EEPROM so that U-boot can recognize the board as a different one already managed ?
If I change the ID so the U-boot see the board as a "A20-SOM204-1Gs16Me16G-MC - 8958" ? May I encounter compatibility problem ?
See the output from the U-boot console using "olinuxino config list" command:
ARMBIAN IMAGE:
Code Select
=> olinuxino config info
Model: Rev.C2
Serial:0002AC2C
MAC: 30:1F:9A:D1:67:37
=> olinuxino config list
Supported boards:
----------------------------------------
A20-OLinuXino-LIME - 7739
A20-OLinuXino-LIME-n4GB - 7743
A20-OLinuXino-LIME-n8G - 8934
A20-OLinuXino-LIME-s16MB - 9076
A20-OLinuXino-LIME-e16Gs16M - 9516
A20-OLinuXino-LIME-e4Gs16M - 9696
T2-OLinuXino-LIME-IND - 9211
T2-OLinuXino-LIME-s16M-IND - 9215
T2-OLinuXino-LIME-e4G-IND - 9219
T2-OLinuXino-LIME-e4Gs16M-IND - 9734
A20-OLinuXino-LIME2 - 7701
A20-OLinuXino-LIME2-e4GB - 8340
A20-OLinuXino-LIME2-e16GB - 9166
A20-OLinuXino-LIME2-n4GB - 7624
A20-OLinuXino-LIME2-n8GB - 8910
A20-OLinuXino-LIME2-s16MB - 8946
A20-OLinuXino-LIME2-e16Gs16M - 9604
A20-OLinuXino-LIME2-e4Gs16M - 9613
A20-OLinuXino-LIME2-G2 - 9905
T2-OLinuXino-LIME2-IND - 9239
T2-OLinuXino-LIME2-s16MB-IND - 9247
T2-OLinuXino-LIME2-e8Gs16M-IND - 9243
A20-OLinuXino-MICRO - 4614
A20-OLinuXino-MICRO-n4GB - 4615
A20-OLinuXino-MICRO-e4GB-IND - 8661
A20-OLinuXino-MICRO-IND - 8828
A20-OLinuXino-MICRO-e4GB - 8832
A20-OLinuXino-MICRO-n8G - 8918
A20-OLinuXino-MICRO-e16G - 9042
A20-OLinuXino-MICRO-s16MB - 9231
A20-OLinuXino-MICRO-e4Gs16M - 9684
A20-OLinuXino-MICRO-e16Gs16M - 9689
T2-OLinuXino-MICRO-IND - 9223
T2-OLinuXino-MICRO-e4GB-IND - 9227
T2-OLinuXino-MICRO-s16MB-IND - 9235
T2-OLinuXino-MICRO-e4Gs16M-IND - 9739
T2-OLinuXino-MICRO-e4Gs16M-IND - 9789
A20-SOM-n4GB - 4673
A20-SOM - 7664
A20-SOM-IND - 8849
A20-SOM-n8GB - 8922
A20-SOM-e16GB - 9155
A20-SOM-e16GB-IND - 9148
A20-SOM-e16Gs16M - 9047
T2-SOM-IND - 9259
T2-SOM-e8Gs16M-IND - 9827
A20-SOM204-1G - 8991
A20-SOM204-1Gs16Me16G-MC - 8958
A20-SOM204-1G-M - 10257
T2-SOM204-1Gs16Me4G-C-I - 10157
T2-SOM204-1Gs16Me8G-MC-I - 10234
T2-SOM204-1G-I - 10238LATEST OFFICIAL IMAGE:
Code Select
=> olinuxino config info
ID: T2-SOM204-1Gs16Me16G-MC-I Rev.C2
SN: 0002AC2C
MAC: 30:1F:9A:D1:67:37
=> olinuxino config list
Supported boards:
----------------------------------------
A20-OLinuXino-LIME - 7739
A20-OLinuXino-LIME-n4GB - 7743
A20-OLinuXino-LIME-n8G - 8934
A20-OLinuXino-LIME-s16MB - 9076
A20-OLinuXino-LIME-e4GB - 9160
A20-OLinuXino-LIME-e16Gs16M - 9516
A20-OLinuXino-LIME-e4Gs16M - 9696
T2-OLinuXino-LIME-IND - 9211
T2-OLinuXino-LIME-s16MB-IND - 9215
T2-OLinuXino-LIME-e4G-IND - 9219
T2-OLinuXino-LIME-e4Gs16M-IND - 9734
T2-OLinuXino-LIME-e8Gs16M-IND - 10481
T2-OLinuXino-LIME-e16Gs16M-IND - 11444
A20-OLinuXino-LIME2 - 7701
A20-OLinuXino-LIME2-e4GB - 8340
A20-OLinuXino-LIME2-e16GB - 9166
A20-OLinuXino-LIME2-n4GB - 7624
A20-OLinuXino-LIME2-n8GB - 8910
A20-OLinuXino-LIME2-s16M - 8946
A20-OLinuXino-LIME2-e16Gs16M - 9604
A20-OLinuXino-LIME2-e4Gs16M - 9613
A20-OLinuXino-LIME2-G2 - 9905
T2-OLinuXino-LIME2-IND - 9239
T2-OLinuXino-LIME2-s16M-IND - 9247
T2-OLinuXino-LIME2-e8Gs16M-IND - 9243
T2-OLinuXino-LIME2-e16Gs16M-IND - 11439
A20-OLinuXino-MICRO - 4614
A20-OLinuXino-MICRO-n4GB - 4615
A20-OLinuXino-MICRO-e4GB-IND - 8661
A20-OLinuXino-MICRO-IND - 8828
A20-OLinuXino-MICRO-e4GB - 8832
A20-OLinuXino-MICRO-n8G - 8918
A20-OLinuXino-MICRO-e16G - 9042
A20-OLinuXino-MICRO-s16M - 9231
A20-OLinuXino-MICRO-e4Gs16M - 9684
A20-OLinuXino-MICRO-e16Gs16M - 9689
T2-OLinuXino-MICRO-IND - 9223
T2-OLinuXino-MICRO-e4G-IND - 9227
T2-OLinuXino-MICRO-s16M-IND - 9235
T2-OLinuXino-MICRO-e4Gs16M-IND - 9739
T2-OLinuXino-MICRO-e8Gs16M-IND - 9789
T2-OLinuXino-MICRO-e16Gs16M-IND - 11449
A20-SOM-n4GB - 4673
A20-SOM - 7664
A20-SOM-IND - 8849
A20-SOM-n8GB - 8922
A20-SOM-e16GB - 9155
A20-SOM-e16GB-IND - 9148
A20-SOM-e16Gs16M - 9047
T2-SOM-IND - 9259
T2-SOM-e8Gs16M-IND - 9827
T2-SOM-e16Gs16M-IND - 11454
A20-SOM204-1G - 8991
A20-SOM204-1Gs16Me16G-MC - 8958
A20-SOM204-1G-M - 10257
T2-SOM204-1Gs16Me4G-C-I - 10157
T2-SOM204-1Gs16Me8G-MC-I - 10234
T2-SOM204-1Gs16Me16G-M-I - 11458
T2-SOM204-1Gs16Me16G-MC-I - 11462
T2-SOM204-1G-I - 10238FAILED BOOT LOG FROM ARMBIAN IMAGE :
Code Select
U-Boot SPL 2019.04-armbian (Feb 22 2021 - 16:44:34 +0100)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
EEPROM: Ready
Config: Valid
Trying to boot from MMC1
U-Boot 2019.04-armbian (Feb 22 2021 - 16:44:34 +0100) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Model: Rev.C2
Serial:0002AC2C
MAC: 30:1F:9A:D1:67:37
I2C: ready
DRAM: 1 GiB
NAND: 0 MiB
MMC: mmc@1c0f000: 0, mmc@1c12000: 1
Loading Environment from EXT4... OK
Setting up a 800x480 lcd console (overscan 0x0)
In: serial
Out: vga
Err: vga
Allwinner mUSB OTG (Peripheral)
Net: eth0: ethernet@1c50000
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 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
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 4 ms (926.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
204 bytes read in 2 ms (99.6 KiB/s)
8443205 bytes read in 472 ms (17.1 MiB/s)
7590712 bytes read in 424 ms (17.1 MiB/s)
Found mainline kernel configuration
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
## Loading init Ramdisk from Legacy Image at 43200000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8443141 Bytes = 8.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 2 ms (1.8 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
204 bytes read in 1 ms (199.2 KiB/s)
8443205 bytes read in 474 ms (17 MiB/s)
7590712 bytes read in 422 ms (17.2 MiB/s)
Found mainline kernel configuration
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
## Loading init Ramdisk from Legacy Image at 43200000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8443141 Bytes = 8.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
NAND booting is temporary disabled.
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
DMA reset timeout
DMA reset timeout
=> #20
A20 / Re: T2-OLinuXino-LIME2-e16Gs16...
Last post by LubOlimex - November 20, 2024, 10:10:47 AMIt doesn't boot from the SD card? Or it doesn't boot form the eMMC?
What exactly is the boot log of a failed boot?
Notice that your issue is different form the issue of the poster above you. He used old Olimage, you use entirely different image (Armbian).
Armbian Linux has nothing to do with Olimage Linux.
I don't think there is ID recognition at all in Armbian which means that you'd have to configure the u-boot manually for the 16Gb eMMC.
What exactly is the boot log of a failed boot?
Notice that your issue is different form the issue of the poster above you. He used old Olimage, you use entirely different image (Armbian).
Armbian Linux has nothing to do with Olimage Linux.
I don't think there is ID recognition at all in Armbian which means that you'd have to configure the u-boot manually for the 16Gb eMMC.