Orange Pi3 lts

[Ukhellfire]

5 hours ago, Rockford the Roe said:

Yup, I'm also stuck at this part, and it's not just on Armbian. It also doesn't even work with the BSP u-boot.

Are you bringing the board up through patches? Are you putting the patches in the patches folder? Or the userpatches folders?

 

15 minutes ago, orangepifan said:

If you want me to send a serial cable to you, PM me and we can arrange details, otherwise enjoy 

I shall bare this in mind thank you!

[Kamileon]

Hi, i also would like to test Armbian on this board.

1 hour ago, Ukhellfire said:

What gets me, is it boots with the orange pi 3 image.

What is strange is that I have tried Armbian for Orange Pi 3 on a LTS board and it didn't boot.

[Rockford the Roe]

24 minutes ago, Ukhellfire said:

Are you bringing the board up through patches? Are you putting the patches in the patches folder? Or the userpatches folders?

 

I'm actually doing something else entirely. I'm trying to port Arch Linux ARM for my LTS. I used your kernel and OrangePi's provided u-boot and built them manually following these instructions.

[Ukhellfire]

On 3/13/2022 at 12:28 AM, Rockford the Roe said:

 

I'm actually doing something else entirely. I'm trying to port Arch Linux ARM for my LTS. I used your kernel and OrangePi's provided u-boot and built them manually following these instructions.

Oh OK! Yeah that's probably a bit different I guess? Haven't looked at it. I dont see see why that wouldn't work. Except my kernel isn't 100% complete yet. The driver needs editing and little bits etc...

Have just discovered that my patches wernt being applied properly on armbian build though.

 

Well now I'm stuck here...

 

 

[Werner]

4 hours ago, Ukhellfire said:

Well now I'm stuck here...

 

 

 

Might be related to 3rd party WIFI drivers. Retry with EXTRAWIFI=no

[Ukhellfire]

4 hours ago, Werner said:

Might be related to 3rd party WIFI drivers. Retry with EXTRAWIFI=no

Ah OK. It does seem to be when compiling wifi drivers. 

rtl88x2bu I believe...

So I shall give this a go! Is there anywhere I can find extra build flags like this? Is there a list anywhere?

 

[Werner]

21 minutes ago, Ukhellfire said:

So I shall give this a go! Is there anywhere I can find extra build flags like this? Is there a list anywhere?

Yes. https://docs.armbian.com/Developer-Guide_Build-Options/

[Ukhellfire]

24 minutes ago, Werner said:

Yes. https://docs.armbian.com/Developer-Guide_Build-Options/

I've gone through that documentation so many times! I must of scanned over that and missed it! Thank you! It's worked!

Is there any way to pass this without having to set it as a flag every time I build? 

Now to test it! Fire it up!

 

[Werner]

5 minutes ago, Ukhellfire said:

Is there any way to pass this without having to set it as a flag every time I build? 

Yes. Just read the very same page again

Quote

These parameters are meant to be applied to the ./compile.sh command. They are all optional. They can also be added to your build configuration file to save time. Default values are marked bold if applicable.

 

[Ukhellfire]

On 3/13/2022 at 12:13 PM, Werner said:

Yes. Just read the very same page again

 

I have just read through that aswell! Wow! Very observant me! 

 

Good News!

 

It boots! i can log in. desktop shows.

 

feels like the cpu is overheating somewhat, and then eveything locks up.

 

No Wifi, but im pretty certain thats due to the fact its not enabled in the dts file. This is the least of my worries though at the moment.

[Werner]

5 minutes ago, Ukhellfire said:

feels like the cpu is overheating somewhat, and then eveything locks up.

Kind a to be expected. H6 is known to produce quite some heat. Put a heat sink to it.

I have these babies for my Allwinner SoCs (Well actually H6/H616 only, others do not need cooling at all): https://www.amazon.com/-/de/dp/B077VM8FJW/

Yeah I know, they are kind a overkill but I live living the way 'go big or go home'

[Ukhellfire]

On 3/13/2022 at 1:04 PM, Werner said:

Kind a to be expected. H6 is known to produce quite some heat. Put a heat sink to it.

I have these babies for my Allwinner SoCs (Well actually H6/H616 only, others do not need cooling at all): https://www.amazon.com/-/de/dp/B077VM8FJW/

Yeah I know, they are kind a overkill but I live living the way 'go big or go home'

Oh ive got some heatsinks im going to wack on them. not quite that big, but still!  haha!

Well the only reason im mention it, is because of the lock up, and the fact that when it was running the orangepi3 armbian, and the orangepi os, it was nowhere near as hot...

 

Well today has been a lot of error solving, chasing my tail etc... but it has taught me one thing. Start with the simpler things! Haha!

Today has been spent trying to get the WiFi module to build properly. With no success. 

So for now, I'm going to concentrate on bringing the board up properly first. Make sure everything else is working etc... 

Then I'll battle the WiFi. I think it's going to be the hardest part to this to be honest. 

 

Just going to leave this here 😉

 

Running very smoothly too! I guess I'll be battling the WiFi sooner than I thought! 

Do need to swap the leds over in the config so the green led is on when it's booted though! It's the little things! 

[mete]

Nice!

Wi-fi is the only thing not working right now?

Do you have it somewhere where I can build it myself? Or do you have plans to "release" it soon?

 

Thanks man!

[Ukhellfire]

6 minutes ago, mete said:

Nice!

Wi-fi is the only thing not working right now?

Do you have it somewhere where I can build it myself? Or do you have plans to "release" it soon?

 

Thanks man!

At the moment, everything is local. I do have the rudimental bare bones of the repositories on my github. But would take a bit of playing to get it to build. I'm going to be deleting the repos and starting a fresh from my local build. Then I will be submitting pull requests to armbian. Feel free to keep an eye on my github though. Will be in the next few days it's done. 

failing that, I can always upload .img file somewhere?

 

Across the surface everything is working. I havent dug deeper yet, and probably won't have time to, at least not for a few days.

That's why I've been playing with things I can do remotely, like building it, trying to get the WiFi working etc. 

 

For this reason I would love some testers!

And even maybe some help with code etc, once I've uploaded the repositories completely. 

I'll post the link once it's up! 

[orangepifan]

24 minutes ago, Ukhellfire said:

For this reason I would love some testers!

And even maybe some help with code etc, once I've uploaded the repositories completely. 

I'll post the link once it's up! 

 

Please post source, at least. I can build myself if need be. Failing that, I can also just flash the .img to see what happens.

What did you have to do to get it stop hanging?

I'd encourage you to post source sooner rather than later, because even without WiFi this is still pretty valuable (users can use Ethernet OR external USB adapter).

GREAT JOB and carry on!

[Ukhellfire]

On 3/14/2022 at 10:17 PM, orangepifan said:

 

Please post source, at least. I can build myself if need be. Failing that, I can also just flash the .img to see what happens.

What did you have to do to get it stop hanging?

I'd encourage you to post source sooner rather than later, because even without WiFi this is still pretty valuable (users can use Ethernet OR external USB adapter).

GREAT JOB and carry on!

Oh I will be don't worry! Over the next few days. 

The img I can upload remotely, so is easier for me to do at the moment. 

 

I want to make sure the board is stable before I carry on with wifi really. 

Thats what stopped it hanging. I stopped trying to compile the WiFi driver. It's due to there only being older (5.13.y) kernel versions around I think. 5.15.y things changed from what I can tell. Not 100% sure on that yet...

 

Well as promised. 

Here's the link to the img I am currently running. 

As I said, I haven't had hardly anytime to test. So please test away!

I need to know everything that doesn't work! 

 

https://drive.google.com/file/d/1pmi_FMRy0nsLo-szKk9xZaR20F-dQSOP/view?usp=sharing

[Kamileon]

@Ukhellfire unfortunately your image doesn't boot on my Orangepi. Will be getting my UART adapter today so I will check boot process.

[Ukhellfire]

Just now, Kamileon said:

@Ukhellfire unfortunately your image doesn't boot on my Orangepi. Will be getting my UART adapter today so I will check boot process.

Really? I'm running it right now? Is there different variants of the board I wonder? 

Any feed back would be amazing! 

Would uou be able to send me the dtb/dts file of an img that does boot on yours? 

[Kamileon]

It's a standard Orangepi Debian Buster image, don't know about different variants

Here are dtb/dts files from that image: https://nextcloud.lodz.webredirect.org/s/Jks6x9o9sCfysPD

[Ukhellfire]

2 hours ago, Kamileon said:

It's a standard Orangepi Debian Buster image, don't know about different variants

Here are dtb/dts files from that image: https://nextcloud.lodz.webredirect.org/s/Jks6x9o9sCfysPD

 

Hmm very strange. I think there may be 2 variants. What v number does it say on you board? Mines a v1.4

[Kamileon]

Mine i also V 1.4

https://nextcloud.lodz.webredirect.org/s/MH8SxkMfjZZQe5i

 

@Ukhellfire This is what I get from UART starting your image

U-Boot SPL 2021.10-armbian (Mar 14 2022 - 08:18:53 +0000)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.2(debug):a04808c1-dirty
NOTICE:  BL31: Built : 08:18:34, Mar 14 2022
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc07c170, model: OrangePi 3 LTS
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2021.10-armbian (Mar 14 2022 - 08:18:53 +0000) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3 LTS
DRAM:  2 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3202 bytes read in 4 ms (781.3 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
154 bytes read in 3 ms (49.8 KiB/s)
35780 bytes read in 9 ms (3.8 MiB/s)
4191 bytes read in 6 ms (681.6 KiB/s)
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)
## Executing script at 45000000
12462020 bytes read in 619 ms (19.2 MiB/s)
21735432 bytes read in 1077 ms (19.2 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41710000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    12461956 Bytes = 11.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 4941d000, end 49fff784 ... OK
   Loading Device Tree to 00000000493ab000, end 000000004941cfff ... OK

Starting kernel ...

 

Hangs on "Starting kernel ..."

What is checksum for that image?

 

For reference this is Orangepi image booting that works

 

[191]HELLO! BOOT0 is starting!
[195]boot0 commit : b65841975dcb31f64a2c69344f60db12b98791ae
 
[213]PMU: AXP806
[216]vdd-sys vol:980mv
[219]set pll start
[222]set pll end
[224]DRAM VERSION IS V2_76
[227]PMU:Set DDR Vol 1200mV OK.
[230]PMU:Set DDR Vol 1200mV OK.
[1439]DRAM CLK =744 MHZ
[1441]DRAM Type =7 (3:DDR3,4:DDR4,6:LPDDR2,7:LPDDR3)
[1446]DRAM zq value: 003b3bfb
[1750]IPRD=00710071--PGCR0=00000f5d--PLL=b0003d00
[1755]Actual DRAM SIZE =2048 M
[1758]DRAM SIZE =2048 M,para1 = 000030fa,para2 = 08001000
[1769]DRAM simple test OK.
[1772]dram size =2048
[1775]card no is 0
[1777][mmc]: mmc driver ver 2017-10-19 10:34:00
[1781][mmc]: sdc0 spd mode error, 2
[1785][mmc]: mmc 0 bias 00000000
[1793][mmc]: Wrong media type 0x00000000
[1797][mmc]: ***Try SD card 0***
[1807][mmc]: HSSDR52/SDR25 4 bit
[1810][mmc]: 50000000 Hz
[1813][mmc]: 14840 MB
[1815][mmc]: ***SD/MMC 0 init OK!!!***
[1945]Loading boot-pkg Succeed(index=0).
[1949]Entry_name        = u-boot
[1964]Entry_name        = parameter
[1967]Entry_name        = monitor
[1971]Entry_name        = scp
[1980]set arisc reset to de-assert state
[1984]Entry_name        = soc-cfg
[1988]Entry_name        = dtb
[1992]Ready to disable icache.
[1995]Jump to secend Boot.
INFO:    Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):c5e8aec
NOTICE:  BL3-1: Built : 14:42:22, Apr 26 2018
NOTICE:  BL3-1 commit: c5e8aec20ca8c6ce31078c5689cbdb1a7352c813

INFO:    BL3-1: Initializing runtime services
ERROR:   Error initializing runtime service tspd_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x4a000000
INFO:    BL3-1: Next image spsr = 0x1d3


U-Boot 2014.07-orangepi (Dec 30 2021 - 09:15:17) Xunlong Software 

[2.043]uboot commit : b65841975dcb31f64a2c69344f60db12b98791ae
 
[2.043]secure enable bit: 0
[2.043]normal mode: with secure monitor
I2C:   ready
[2.044]pmbus:   ready
[2.044][ARISC] :arisc initialize
[2.070][ARISC] :arisc para ok
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :arisc version: []
[SCP] :sunxi-arisc driver v1.10 is starting
[2.084][ARISC] :sunxi-arisc driver startup succeeded
[2.085]PMU: AXP806
[2.085]PMU: AXP806 found
[2.085]bat_vol=0, ratio=0
[2.085]set pc_bias(1) bias:1800
[2.085]set pg_bias(5) bias:1800
[2.085]set power on vol to default
[2.086]dcdca_vol = 1000, onoff=1
[2.090]aldo2_vol = 3300, onoff=1
[2.094]bldo3_vol = 1800, onoff=1
[2.098]cldo2_vol = 3300, onoff=1
[2.103]cldo3_vol = 3300, onoff=1
[2.107]find power_sply to end
[2.107]cant find pll setting(1320M) from  pll table,use default(408M)
[2.109]PMU: cpux 408 Mhz,AXI=204 Mhz
[2.109]PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz MBus=400Mhz
[2.114]DRAM:  2 GiB
[2.117]fdt addr: 0xb9ccb0e0
[2.118]gd->fdt_size: 0x1a6c0
[2.121]Relocation Offset is: 74d85000
[2.207]gic: sec monitor mode
[2.207]line:180 func:check_ir_boot_recovery start 
[2.207]ir boot recovery not used
[2.207][key recovery] no use
[2.208][box standby] read rtc = 0x0
[2.208][box standby] start_type = 0x1
[2.208][box standby] to kernel
[2.208]workmode = 0,storage type = 1
[2.210]MMC:	 2
SUNXI SD/MMC: 2
[mmc]: [0-63|64] 
[mmc]: [0-54|55] 
[mmc]: [6-51|46] 
[mmc]: [0-13|14] [27-31|5] [36-53|18] 
[mmc]: [0-51|52] [59-59|1] [61-63|3] 
[mmc]: [0-28|29] [59-63|5] 
[mmc]: [0-61|62] 
[mmc]: [6-54|49] [56-61|6] 
[mmc]: [2-6|5] [9-58|50] 
[mmc]: [1-28|28] 
Normal
[7.003]MMC:	 0
SUNXI SD/MMC: 2, SUNXI SD/MMC: 0
[7.024]sunxi flash init ok
[7.024]hdmi hdcp not enable!
[7.024]display init start
[7.024]drv_disp_init
[7.041]init_clocks: finish init_clocks.
[7.060]__clk_enable: clk is null.
[7.060]hdmi cec clk enable failed!
[7.066]request pwm success, pwm1:pwm1:0x300a000.
[7.074]key emac have not been burned yet
[7.074][ac200] tv_read_sid,line:188
 [7.074]sunxi_efuse_readn failed:-1
[7.081]drv_disp_init finish
[7.081]hdmi hdcp not enable!
200 bytes read in 14 ms (13.7 KiB/s)
Set HDMI disp_mode to 1080p60
[7.099]hdmi hpd out, force open?
200 bytes read in 13 ms (14.6 KiB/s)
Set fb0_width to 1280
Set fb0_height to 720
[7.116]display init end
Using default environment

bmp_name=/boot/boot.bmp
230456 bytes read in 26 ms (8.5 MiB/s)
[7.153]show bmp on ok
[7.153]inter uboot shell
Hit any key to stop autoboot:  0 
mmc0 is current device
2615 bytes read in 18 ms (141.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
200 bytes read in 14 ms (13.7 KiB/s)
102389 bytes read in 31 ms (3.1 MiB/s)
6551063 bytes read in 311 ms (20.1 MiB/s)
22480968 bytes read in 994 ms (21.6 MiB/s)
## Booting kernel from Legacy Image at 41000000 ...
   Image Name:   
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    22480904 Bytes = 21.4 MiB
   Load Address: 41000000
   Entry Point:  41000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6550999 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
   reserving fdt memory region: addr=40020000 size=800
   reserving fdt memory region: addr=48000000 size=1000000
   reserving fdt memory region: addr=48100000 size=4000
   reserving fdt memory region: addr=48104000 size=1000
   reserving fdt memory region: addr=48105000 size=1000
   reserving fdt memory region: addr=43000000 size=1a000
   Loading Ramdisk to 499c0000, end 49fff5d7 ... OK
   Using Device Tree in place at 44000000, end 4401d6bf

Starting kernel ...

INFO:    BL3-1: Next image address = 0x41000000
INFO:    BL3-1: Next image spsr = 0x3c5
WARNING: Unimplemented Standard Service Call: 0xc0000026 

Orange Pi 2.1.6 Buster ttyS0

 

[Ukhellfire]

21 minutes ago, Kamileon said:

Hangs on "Starting kernel ..."

What is checksum for that image?

4885d4478d18945fcbdedb1511115e1078c5533ad07bff8f672dfc01faee4737 *Armbian_22.05.0-trunk_Orangepi3-lts_focal_current_5.15.28_xfce_desktop.img

 

Straight from the sha1 file. I was thinking that earlier actually. But figured it couldn't be! I shall now upload that file with the img!

It would be good if that was it! Let me know what you get! 

Yeah that uboot seems as if its booting. Few minor glitches in there from my quick scan over haha! Damn I need to get me a uart cable!

[Rockford the Roe]

21 hours ago, Ukhellfire said:

Well as promised. 

Here's the link to the img I am currently running. 

As I said, I haven't had hardly anytime to test. So please test away!

I need to know everything that doesn't work! 

 

https://drive.google.com/file/d/1pmi_FMRy0nsLo-szKk9xZaR20F-dQSOP/view?usp=sharing

I'm having the same problem as I did with the Orange Pi 3 image. Every-time I try to boot it, I get the message:

ALERT! UUID=9efeebc7-0ce3-44c6-9382-822d4db81542 does not exist.

However, blkid returns with:
 

/dev/sdb1: UUID="6b17d722-0678-4701-9e06-53f39db7da32"

I'm going to change the UUID to the correct one, and if it isn't booting still, then I'm stuck.

[Kamileon]

22 minutes ago, Ukhellfire said:

4885d4478d18945fcbdedb1511115e1078c5533ad07bff8f672dfc01faee4737 *Armbian_22.05.0-trunk_Orangepi3-lts_focal_current_5.15.28_xfce_desktop.img

 

Straight from the sha1 file. I was thinking that earlier actually. But figured it couldn't be! I shall now upload that file with the img!

It would be good if that was it! Let me know what you get! 

Yeah that uboot seems as if its booting. Few minor glitches in there from my quick scan over haha! Damn I need to get me a uart cable!

That's weird, I redownloaded your image one more and I have exact same sha1sum as the first time which is not what you got from sha1 file
 

sha1sum Armbian_22.05.0-trunk_Orangepi3-lts_focal_current_5.15.28_xfce_desktop.img
dce7241bd8dc2b89e1328034e17686f6e6480719  Armbian_22.05.0-trunk_Orangepi3-lts_focal_current_5.15.28_xfce_desktop.img

Still doesn't boot

[Ukhellfire]

On 3/15/2022 at 10:28 PM, Rockford the Roe said:

I'm having the same problem as I did with the Orange Pi 3 image. Every-time I try to boot it, I get the message:

ALERT! UUID=6b17d722-0678-4701-9e06-53f39db7da32 does not exist.

However, blkid returns with:
 

/dev/sdb1: UUID="6b17d722-0678-4701-9e06-53f39db7da32"

I'm using a USB 3.0 adapter.

Ook that's not to bad at all. 

I believe a quick "rootdelay=" should fix that. 

I think it because it boots from sd it take that little bit longer sometimes for the root filesystem to be loaded. Uboot doesn't see it when it wants it. But you can see it through shell...

 

On 3/15/2022 at 10:51 PM, Kamileon said:

That's weird, I redownloaded your image one more and I have exact same sha1sum as the first time which is not what you got from sha1 file
 

sha1sum Armbian_22.05.0-trunk_Orangepi3-lts_focal_current_5.15.28_xfce_desktop.img
dce7241bd8dc2b89e1328034e17686f6e6480719  Armbian_22.05.0-trunk_Orangepi3-lts_focal_current_5.15.28_xfce_desktop.img

Still doesn't boot

OK that's just weird. I'm going to recompile uboot with root delay anyway. So let me do that. I shall upload the new img with the new sha file all at the same time... we will get this sorted! 

[Rockford the Roe]

11 minutes ago, Ukhellfire said:

I believe a quick "rootdelay=" should fix that.

I set it on armbianEnv.txt, no change.

[orangepifan]

On 3/15/2022 at 10:56 PM, Ukhellfire said:

OK that's just weird. I'm going to recompile uboot with root delay anyway. So let me do that. I shall upload the new img with the new sha file all at the same time... we will get this sorted! 

I should have time to test tonight. My config is Orange PI 3 LTS with 64GB SD card. Let's see what happens!! I seem to recall there is no WiFi yet, so I'll see if I can boot it with a head and then run it over to my ethernet.

 

@UkhellfireWhoops, it seems your shared file is now in the trash. Let me know when you have a new candidate IMG.

[Ukhellfire]

On 3/16/2022 at 12:42 AM, orangepifan said:

@UkhellfireWhoops, it seems your shared file is now in the trash. Let me know when you have a new candidate IMG.

Haha yes it is! If it's not booting, there's no point in it being there! Haha!

 

Right. I now have a new link. I've just shared the folder now instead. That way it will always be the latest etc, with sha1 file...

 

https://drive.google.com/drive/folders/16UHmZsGD4qv7HqY5pPtZcQZ1WeEBDFA8?usp=sharing

 

Any logs/errors etc willalways be appreciated. It's always handy.

 

Oh and look out for any wifi errors etc too, if any! 

 

I have yet to test this img. I can't get to my board tonight. So you guys are going to test this before me. Let me know how it goes!

I've added a rootdelay of 5 seconds to the kernel/uboot. Hopefully this stops that uuid error. 

Oh and I've swapped power and status LEDs round. So it will now be a green light instead of a red one. 

 

On 3/15/2022 at 11:05 PM, Rockford the Roe said:

I set it on armbianEnv.txt, no change.

Ah I didn't see this... OK. Damn it. 

I've set it in both uboot and kernel dts. Would that make a difference? 

Also, how long a delay did you give it?

 

@orangepifan @Rockford the Roe @Kamileon

Has anyone tried the new image?

It boots fine for me. 

I put the sdcard in.

I plug the board into mains. 

It fires up. 

No issues at all.

Green LED  (ocd much?)

 

The only thing I'm seeing as I boot up, is the kernel modules aren't being loaded up.

This probably isn't a major issue though.

 

So. I now wonder, why I can boot, but others can't? 

 

I'm going to re-build with an edited dts file, and upload that alongside the one I uploaded last night.

The dts file I'll be using, caused my board to crash. But I'm wondering if it will work for you guys?

 

There has to be either something different with our boards (which I can't see would be major enough to stop it booting) or that my image corrupted when I uploaded it?? The sha1 checksum mentioned above makes me wonder This? 

 

[Kamileon]

Nope, same as before except the led is green now. Checked sha256sum and seems to be OK but stuck on "Starting kernel ..."

[Ukhellfire]

23 minutes ago, Kamileon said:

Nope, same as before except the led is green now. Checked sha256sum and seems to be OK but stuck on "Starting kernel ..."

Are you running headless?