StarSurfer Posted April 26, 2022 Share Posted April 26, 2022 Hello everyone, i build a own Image for the EspressoBin and it wont boot. In the u-boot log shows boot.scr but on the Image himself is just a boot.scr.uimg. What is the problem ? Greetings StarSurfer Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 Hit any key to stop autoboot: 0 starting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found / ** File not found /boot.scr ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** File not found /boot/boot.scr ** ## Executing script at 06d00000 Wrong image format for "source" command scanning bus for devices... Device 0: unknown device / ** Bad device scsi 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device scsi 0 ** ## Executing script at 06d00000 Wrong image format for "source" command / ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command / Card did not respond to voltage select! ** Bad device mmc 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ Card did not respond to voltage select! ** Bad device mmc 0 ** ## Executing script at 06d00000 Wrong image format for "source" command Marvell>> 0 Quote Link to comment Share on other sites More sharing options...
ManoftheSea Posted April 27, 2022 Share Posted April 27, 2022 Hello, @StarSurfer, This is my fault, and something I'll need to repair for release. I believe the fastest solution for you would be to mount your image and rename the file boot.scr.uimg to boot.scr . This won't work because the boot.cmd was changed to use the newer u-boot default parameters. Follow the directions below. Alternately, if you flash the latest u-boot (2022.04) and wipe the environment variables according to instructions I haven't posted to the espressobin page yet, the u-boot 2022.04 default boot looks for the boot.scr.uimg file. An initial pass of those instructions looks like, from the u-boot serial console: - env default -a - setenv ethaddr <YOUR_ADDR_HERE> - saveenv 1 Quote Link to comment Share on other sites More sharing options...
StarSurfer Posted April 29, 2022 Author Share Posted April 29, 2022 Hello ManoftheSea Thank you for your feedback. I could flash an old image without any problems, but unfortunately that doesn't do me any good, since the kernel modules for the DVB Media Adapter PCI are not included in the images by default. That's why I always build the OS completely and check the kernel modules DVB for PCI. Updated u-boot (2022.04) needs new default boot environment and new boot script (TODO with 2022.05 release) U-boot Script 404 Not Found 0 Quote Link to comment Share on other sites More sharing options...
ManoftheSea Posted May 1, 2022 Share Posted May 1, 2022 If you built the OS yourself, you should have built u-boot as well. In cache/sources/u-boot/v2022.04/ you should be able to find "flash-image...bin" files. As I mentioned above, I'm still working on getting all the necessary files in place. But run the commands I gave you: env default -a saveenv the armbianEnv.txt boot environment should be fine matching the build you did, and the boot script is part of the default u-boot env. 0 Quote Link to comment Share on other sites More sharing options...
StarSurfer Posted May 8, 2022 Author Share Posted May 8, 2022 Hello manofthesea, I have now managed to boot my self-built images. But unfortunately I found out that he doesn't compile the ddbridge for pcie. What I also don't understand is, Why aren't there any DVB Devices modules compiled in the Armbian kernel? 0 Quote Link to comment Share on other sites More sharing options...
ManoftheSea Posted May 8, 2022 Share Posted May 8, 2022 Since we build our own kernel instead of using Debian's upstream, sometimes the kernels are tuned to the device, and sometimes the kernels are detuned through mistake or optimization. For instance, my own kernel builds have turned off a LOT of device drivers, it's the difference between a 180 minute build and a 25 minute build. If you would like the Armbian builder to build modules that you use, please submit a PR against https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu64-current.config or linux-mvebu64-edge.config. 1 Quote Link to comment Share on other sites More sharing options...
StarSurfer Posted May 8, 2022 Author Share Posted May 8, 2022 Now I managed to compile the DDBridge, but now no Ethernet works anymore. New image and he finds only log no WAN or otherwise. 0 Quote Link to comment Share on other sites More sharing options...
ManoftheSea Posted May 8, 2022 Share Posted May 8, 2022 Ethernet is handled by module "phy_mvebu_a3700_comphy", and the switch by "mv88e6xxx". I have no idea how you might have lost these, but... do you have them? List of modules related to ethernet: Spoiler tag_dsa 16384 1 mv88e6xxx 151552 0 dsa_core 94208 2 tag_dsa,mv88e6xxx hsr 40960 1 dsa_core bridge 262144 2 mv88e6xxx,dsa_core stp 20480 1 bridge llc 20480 2 bridge,stp phy_mvebu_a3700_comphy 16384 3 0 Quote Link to comment Share on other sites More sharing options...
StarSurfer Posted May 8, 2022 Author Share Posted May 8, 2022 now its working. i guess the standard .config for kernel building didnt checked the networkcard for the espressobin. I checked the ddbridge and other marvell network cards and now its runnnig. Greetings StarSurfer 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.