voltagex

  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

voltagex's Achievements

  1. Yes, and no, hostapd only handles access points, not connecting to wifi as a client.
  2. Weird, flashed back to the one you suggested now that the download page is back up, had the same issue - must have been the SD card after all. It's also now working with my 2020.10 bootloader!
  3. So, I thought this was worth a try: diff --git a/config/sources/families/mvebu64.conf b/config/sources/families/mvebu64.conf index 091b7633..79e85954 100644 --- a/config/sources/families/mvebu64.conf +++ b/config/sources/families/mvebu64.conf @@ -1,6 +1,6 @@ ARCH=arm64 -BOOTSOURCE='https://github.com/MarvellEmbeddedProcessors/u-boot-marvell.git' -BOOTBRANCH='branch:u-boot-2018.03-armada-18.12' +BOOTSOURCE='https://github.com/u-boot/u-boot' +BOOTBRANCH='branch:master' BOOTENV_FILE='mvebu64.txt' ATFSOURCE='https://github.com/MarvellEmbeddedProcessors/atf-marvell' ATFDIR='arm-trusted-firmware-espressobin' TIM-1.0 WTMI-devel-18.12.1-e6bb176 WTMI: system early-init DDR topology parameters: ======================== ddr type DDR3 ddr speedbin 12 bus width 16-bits cs num 2 cs[0] - group num 0 cs[0] - bank num 8 cs[0] - capacity 1024MiB cs[1] - group num 0 cs[1] - bank num 8 cs[1] - capacity 1024MiB CPU VDD voltage default value: 1.108V DRAM windows: ============= WIN[0] - base addr 0x60000000 WIN[0] - size 0x40000000 WIN[1] - base addr 0xa0000000 WIN[1] - size 0x20000000 memory test region: =================== CS[0] 0x60000000 - 0x9fffffff CS[1] 0xa0000000 - 0xbfffffff SELF-REFRESH TEST PASS SELF-REFRESH TEST PASS CS0: QS GATE TRAINING PASSED CS1: QS GATE TRAINING PASSED DLL TUNING PASSED NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 14:05:30, Oct 20 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 14:05:30, Oct 20 2020 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 14:05:30 U-Boot 2020.10-armbian (Oct 20 2020 - 14:05:01 +0000) DRAM: 2 GiB Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 5 Gbps 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 PCIE-0: Link up MMC: sdhci@d0000: 0 Loading Environment from SPIFlash... SF: Detected w25q32dw with page size 256 By tes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: neta@30000 [PRIME] My own kernels boot but I'm still having issues with the latest armbian SD card images (same issue with 2017 and 2018 u-boots). I'm not game to touch atf - someone with Marvell's wtp tools set up can do that
  4. Marvell>> bubt flash-image-DDR3-2g_2cs_7-600_600.bin Burning U-BOOT image "flash-image-DDR3-2g_2cs_7-600_600.bin" from "tftp" to "spi" Using neta@30000 device TFTP from server 192.168.10.1; our IP address is 192.168.10.253 Filename 'flash-image-DDR3-2g_2cs_7-600_600.bin'. Load address: 0x8000000 Loading: ############################################################# 4.8 MiB/s done Bytes transferred = 895012 (da824 hex) Image checksum...OK! 722980 bytes written, 172032 bytes skipped in 8.713s, speed 105174 B/s Done! Marvell>> reset resetting ... TIM-1.0 WTMI-devel-18.12.1-e6bb176 WTMI: system early-init DDR topology parameters: ======================== ddr type DDR3 ddr speedbin 12 bus width 16-bits cs num 2 cs[0] - group num 0 cs[0] - bank num 8 cs[0] - capacity 1024MiB cs[1] - group num 0 cs[1] - bank num 8 cs[1] - capacity 1024MiB CPU VDD voltage default value: 1.108V DRAM windows: ============= WIN[0] - base addr 0x60000000 WIN[0] - size 0x40000000 WIN[1] - base addr 0xa0000000 WIN[1] - size 0x20000000 memory test region: =================== CS[0] 0x60000000 - 0x9fffffff CS[1] 0xa0000000 - 0xbfffffff SELF-REFRESH TEST PASS SELF-REFRESH TEST PASS CS0: QS GATE TRAINING PASSED CS1: QS GATE TRAINING PASSED DLL TUNING PASSED NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 09:15:30, Oct 20 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 09:15:30, Oct 20 2020 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(debug):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 09:15:30, Oct U-Boot 2018.03-devel-18.12.3-armbian (Oct 20 2020 - 09:15:15 +0000) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU 600 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 600 [MHz] DRAM: 2 GiB Comphy chip #0: Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps 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 PCIE-0: Link down MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPI Flash... SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Marvell Armada 3720 Community Board ESPRESSOBin Net: eth0: neta@30000 [PRIME] 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... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found / ** Bad device usb 0 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ ** Bad device usb 0 ** ## 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 / Card did not respond to voltage select! ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ Card did not respond to voltage select! ** Bad device mmc 1 ** ## Executing script at 06d00000 Wrong image format for "source" command / ** File not found /boot.scr ** ## Executing script at 06d00000 Wrong image format for "source" command /boot/ 3185 bytes read in 13 ms (239.3 KiB/s) ## Executing script at 06d00000 Boot script loaded from 0 ** Bad device 0 0x9000000 ** ** Bad device specification 0 /boot/uInitrd ** ** Bad device specification 0 /boot/Image ** ** Bad device specification 0 /boot/dtb/ ** No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ** Bad device 0 0x9000000 ** ** Bad device 0 0x9000000 ** Applying user provided fixup script (fixup.scr) ## Executing script at 09000000 Wrong image format for "source" command Bad Linux ARM64 Image magic! Marvell>> printenv baudrate=115200 boot_a_script=ext4load ${boot_interface} ${devnum}:1 ${scriptaddr} ${prefix}boot.scr;source ${scriptaddr}; boot_interface=mmc boot_prefixes=/ /boot/ boot_targets=usb sata mmc1 mmc0 bootargs=root=/dev/mmcblk0p1 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart= usb-storage.quirks= cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done bootcmd_mmc0=setenv devnum 0; setenv boot_interface mmc; run scan_dev_for_boot; bootcmd_mmc1=setenv devnum 1; setenv boot_interface mmc; run scan_dev_for_boot; bootcmd_sata=setenv devnum 0; scsi scan; scsi dev 0; setenv boot_interface scsi; run scan_dev_for_boot; bootcmd_usb=setenv devnum 0; usb start;setenv boot_interface usb; run scan_dev_for_boot; bootdelay=2 bootlogo=false console=both consoleargs=console=ttyS2,1500000 console=tty1 devnum=0 docker_optimizations=on earlycon=off eth1addr=00:51:82:11:22:01 eth2addr=00:51:82:11:22:02 eth3addr=00:51:82:11:22:03 ethact=neta@30000 ethaddr=00:51:82:11:22:00 ethprime=eth0 fdt_addr=0x6000000 fdt_high=0xffffffffffffffff fdt_name=fdt.dtb fdtcontroladdr=7f62d490 fileaddr=6d00000 filesize=c71 gatewayip=10.4.50.254 get_images=tftpboot $kernel_addr $image_name; tftpboot $fdt_addr $fdt_name; run get_ramfs get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramfs_addr 0x8000000; tftpboot $ramfs_addr $ramfs_name; else setenv ramfs_addr -;fi hostname=marvell image_name=Image initrd_addr=0x1100000 initrd_image=uInitrd initrd_size=0x2000000 ipaddr=0.0.0.0 kernel_addr=0x7000000 load_addr=0x9000000 loadaddr=0x8000000 netdev=eth0 netmask=255.255.255.0 overlay_error=false ramfs_addr=0x8000000 ramfs_name=- root=root=/dev/nfs rw rootdev=/dev/mmcblk0p1 rootfstype=ext4 rootpath=/srv/nfs/ scan_dev_for_boot=for prefix in ${boot_prefixes}; do echo ${prefix};run boot_a_script; done scriptaddr=0x6d00000 serverip=192.168.10.1 set_bootargs=setenv bootargs $console $root ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:none nfsroot=$serverip:$rootpath $extra_params stderr=serial@12000 stdin=serial@12000 stdout=serial@12000 verbosity=1 Environment size: 2298/65532 bytes Marvell>> Apologies, I couldn't move the code block once I'd put it in here. I'm trying to boot Armbian_20.08.2_Espressobin_buster_current_5.8.6.img written onto a known-good SD card. I've tried both on an older bootloader and the 2018 one suggested by Armbian.
  5. Not sure if this is the right forum to report this but - dl.armbian.com is redirecting me to https://minio.k-space.ee/armbian/dl/espressobin/u-boot/ which is throwing an error: NoSuchKeyThe specified key does not exist.dl/espressobin/u-boot/armbian/armbian/dl/espressobin/u-boot/163FA81E77EC23A1394e75a7-0234-4f85-9911-0a00ffd23a46
  6. I've configured and connected to a wifi network just fine, but I want to change the config non-interactively. The config isn't in /etc/wpa_supplicant/wpa_supplicant.conf or anywhere else I'd expect, and https://github.com/armbian/config/ only mentions hostapd. Where's the config stored? Edit: /etc/NetworkManager/system-connections/[my SSID]
  7. Ah, I was confused - my board (purchased last month and delivered recently) has them soldered. Many thanks.
  8. Are you talking about the pads labeled Power Key Jumper?
  9. Hi all, In the review of the Fire3 at least one person mentions powering this board via something other than the MicroUSB. This would allow me to use the serial console that's supposedly exposed over that port instead of wiring up yet another USB to serial converter. What I can't work out is a) which pin/s are used to power it, and b) what kind of power supply is used. I'd rather not fry the board (it'll do that itself under load) so can someone point me in the right direction? Thanks in advance.