So I thought this was driven by the community, open and helpful. Obviously, I was mistaken. Sorry for having asked a question.
See, it was possible to solve the problem without me after all. We are just a few people who are contributing to this project in our spare time and with our private resources and neither you or Globalscale are our customers.
Images, which are here, are clearly the best possible for Espressobin but they are still in early stage. This means they do not receive any support since supporting unfinished work would burn out/kill virtually all of our resources in no time. This can lead to closing the entire project down. There are 100.000+ users of Armbian and there is no way few people could solve their/yours/our problems. For free or for money. I can only point them/you to the forum and google in most cases. Your problem can be and it was heard but can’t be addressed in real time. Since you solved the problem, you might help others?
A community is not just you and me.
My harsh reply was simply the result of feeling scorned. The sentence “Our (free) support ends here.” closing the very first message
I received sounded a little too much as “Pay if you want to know more”. Your last message tells me I misunderstood, so I’m sorry
for this, please accept my apologies.
I know what open-source development is. I have been doing this for 24 years now, in various projects, in various languages, in various environments.
I do belong to several organizations in this field, some more free software and copyleft licenses oriented, some more open-source and permissive
licenses oriented (I have been voted as an Apache member more than 10 years ago). I work on free software full time, and a very large part of
this job is helping users and maintaining a community. I do not have the skills for maintaining a Linux distribution, sorry, I’m just a regular
Linux user since 1996 (before that I developed free software on Unix/Solaris).
I am glad that you are able to understand the situation. Well, before I started this project, now four years ago, I was also just a regular Linux user. From the same century 🙂 My first Linux was below 1.0 with Unix/Solaris/VMS experience as well and I needed to learn how to develop and maintain such project. I have some similar experiences, but not like such.
Maintaining this project is, in fact, full-time volunteering job and a hobby for a group of people. Stress level is already high, while there is no other way to relieve than work less and cut down people who want something from me/us. I would like to help, but then more important things get delayed and overall we made a bigger problem.
Expanding the project with putting more and more of only our own money is a bit stupid since the project doesn’t bring any financial gain, we are not even close to cover basic expenses, while most board makers, those who are profiting with our free work, including Globalscale, deny any financial help. Not a penny for a usable system software.
– kernel upgraded to 4.4.96
– optional 4.13.10 RealTime kernels https://forum.armbian.com/topic/5576-fully-preemptible-kernels/
– kernel upgrade to 4.4.102
– Debian Stretch or Ubuntu Xenial
– added NEXT branch with kernel 4.14.2
Cant wait for this because I’m having no luck getting docker working on the ubuntu 16 build.
Kernels/images were updated to 4.14.14 and 4.4.112
Debian Stretch or Ubuntu Xenial based
DVFS driver and few minor fixes:
— armbian (@armbian) March 3, 2018
Stability issues are solved with these updated versions by a refined DDR training algorithm (provided by Marvell).
All available CPU_DDR frequency combinations are there for all boards.
The updated flash images were rebuilt with the following refreshed parts:
Please support Armbian.
I can’t see my reply in this forum?
Is it being green-lighted somehow?
I could not see this reply before so I am posting it again.
I hope that it works this time.
When I am trying to start Armbian 5.38 that I downloaded from the Amrbian page then I get an error message. Please see below.
I flashed an SD card with Etcher and booted.
I hoped it would be as simple as that.
Do I need to follow another tutorial?
Booting Trusted Firmware
BL1: Built : 09:41:56, Jun 2 2NOTICE: BL2: v1.2(release):armada-17.02.0:
NOTICE: BL2: Built : 09:41:57, Jun 2 20NOTICE: BL31: v1.2(release):armada-17.02.0:
U-Boot 2015.01-armada-17.02.0-g8128e91 (Jun 02 2017 – 09:41:51)
DRAM: 1 GiB
CPU @ 1000 [MHz]
L2 @ 800 [MHz]
TClock @ 200 [MHz]
DDR @ 800 [MHz]
Comphy-0: PEX0 2.5 Gbps
Comphy-1: USB3 5 Gbps
Comphy-2: SATA0 5 Gbps
Now running in RAM – U-Boot at: 3ff2b000
U-Boot DT blob at : 000000003fa18168
MMC: XENON-SDHCI: 0
SF: Detected W25Q32DW with page size 256 Bytes, erase size 4 KiB, total 4 MiB
PCIE-0: Link down
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
flags: ncq led only pmp fbss pio slum part sxs
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
15084032 bytes read in 5120 ms (2.8 MiB/s)
4271091 bytes read in 1580 ms (2.6 MiB/s)
** File not found boot/dtb/marvell/armada-3720-community.dtb **
## Loading init Ramdisk from Legacy Image at 01100000 …
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 4271027 Bytes = 4.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
IMHO, your uboot is too old.
I’m using the mainline image and I didn’t have any trouble.
In my boot.scr I’ve got
setenv fdt_name_a boot/dtb/marvell/armada-3720-community.dtb
setenv fdt_name_b boot/dtb/marvell/armada-3720-espressobin.dtb
and on my arbian , i’ve got an “armada-3720-espressobin.dtb” in /boot/dtb/marvell/ and no community version.
However, did you update the uboot as per their instruction ?
Personnally , I didn’t need, but I have a newer version of u-boot on my board ( “Jan 29 2018” , when yours is from “Jun 02 2017”)
I do think that the old uboot will try to fetch the first dtb and failed, when the newer version will try each dtb until one works.
You must be logged in to reply to this topic.
Technical specification tables can not be displayed on mobile. Please view on desktop