Jump to content

mlevistm

Members
  • Posts

    5
  • Joined

  • Last visited

  1. @ebin-dev: here you go TIM-1.0 WTMI-devel-18.12.0-a0a1cb8 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.143V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL1: Built : 13:46:59, Dec 26 2018 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL2: Built : 13:47:01, Dec 26 2018 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):1f8ca7e (Marvell-devel-18.12.2) NOTICE: BL31: Built : 13:4 U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Dec 26 2018 - 13:45:06 +0100) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU 1000 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 800 [MHz] DRAM: 1 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 up MMC: sdhci@d0000: 0 Loading Environment from SPI Flash... SF: Detected is25wp032 with page size 256 Bytes, erase size 64 KiB, total 4 MiB OK Model: Marvell Armada 3720 Community Board ESPRESSOBin
  2. @ebin-dev: SPI flash is recognized. I can only post U-Boot 18.12.3 output in January as I don't have access to the espressobin these days.
  3. Thank you both for the quick replies! @ebin-dev: sata recovery with the image from the parallel thread didn't work for me. What worked was booting into linux and dd the flash image provided in the parallel thread to mtdblock0 as described by kotc.
  4. @kotc can you share the workaround please? I have the same issue, bricked my board and I get the "SF: unrecognized JEDEC id bytes: 9d, 70, 16" error. Thanks!
  5. Hello everyone, I am new to the forum. Does anyone know if the SATA HAT will power the NanoPi M4 board too? I see a power connector on the HAT. Thanks
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines