kotc Posted November 29, 2018 Share Posted November 29, 2018 so on 2018-11-20 i've ordered an espressobin and tried armbian. and i probably got bitten by "yet another spi chip". using: U-Boot 2017.03-armada-18.09.1-ga92bd86-armbian (Sep 05 2018 - 21:49:34 +0200) i get: SF: unrecognized JEDEC id bytes: 9d, 70, 16. from the chip lookup (U10): IS25WP032 - UNSUPPORTED by armbian as of 2018-11-29 so i will try to gather already seen spi chips and their status with corresponding armbian uboots/kernels. since i'm new in the espressobin land, i ask other owners to post their chips and status. Link to comment Share on other sites More sharing options...
kotc Posted November 29, 2018 Author Share Posted November 29, 2018 @ebin-dev could you contact me on freenode (irc) ? Link to comment Share on other sites More sharing options...
ebin-dev Posted November 29, 2018 Share Posted November 29, 2018 Hi there, if you wish to support the yet another unexpected and undocumented change to SPI then you need to patch some files (see i.e. here and here). It should not be too difficult. Do you own a V7 EspressoBin ? I am waiting for Marvell to update their bootloader sources on Github. Support for the V7 EspressoBin is expected. Hopefully the above issue will also be solved. Link to comment Share on other sites More sharing options...
kotc Posted November 29, 2018 Author Share Posted November 29, 2018 on amazon it stated 'v5', so i guess that's that. and confirming on the board is v5_0_1 Link to comment Share on other sites More sharing options...
kotc Posted November 29, 2018 Author Share Posted November 29, 2018 umkay, uboot fixed, didnt even need to do uart rescue (as i was able to boot armbian kernel and write uboot from there to spi). for future reference changes to spi_flash_ids.c: {"is25wp032", INFO(0x9d7016, 0x0, 64 * 1024, 64, SECT_4K) }, i also had to hack around uboot to enable issi flash. but now i have working uboot booting my armbian-ascii (devuan). Link to comment Share on other sites More sharing options...
mlevistm Posted December 27, 2018 Share Posted December 27, 2018 @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! Link to comment Share on other sites More sharing options...
ebin-dev Posted December 27, 2018 Share Posted December 27, 2018 23 minutes ago, mlevistm said: I have the same issue, bricked my board and I get the "SF: unrecognized JEDEC id bytes The new 18.12 bootloader should also support issi flash (see the parallel thread). Link to comment Share on other sites More sharing options...
kotc Posted December 27, 2018 Author Share Posted December 27, 2018 @mlevistm: uboot works even without boot env. 1/ stop autoboot by pressing any key early 2/ set bootargs variable with cmdline (assuming you want to boot to sdcard): setenv bootargs "console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/mmcblk0p1 rootwait" 3/ load kernel and dt (your paths might be different): load mmc 0 0x7000000 boot/Image load mmc 0 0x6000000 boot/armada-3720-espressobin.dtb 4/ if above went without errrors, boot: booti 0x7000000 - 0x6000000 5/ once you are in linux, add missing spi flash description and recompile flashimage/uboot, then write it to spi using flash tools (in my case plain dd to mtdblock0 worked),or: 5b/ use the newest image from parallel thread. 6/ once it's written, you should continue with normal armbian first time setup as seen on downloads page (ie. clear env etc). disclaimer: untested and might contain some typos Link to comment Share on other sites More sharing options...
mlevistm Posted December 29, 2018 Share Posted December 29, 2018 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. Link to comment Share on other sites More sharing options...
ebin-dev Posted December 29, 2018 Share Posted December 29, 2018 26 minutes ago, mlevistm said: What worked was booting into linux and dd the flash image provided in the parallel thread to mtdblock0 Could you post the output of U-Boot 18.12.3 ? Does it recognise your SPI flash now ? Link to comment Share on other sites More sharing options...
mlevistm Posted December 30, 2018 Share Posted December 30, 2018 @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. Link to comment Share on other sites More sharing options...
mlevistm Posted January 5, 2019 Share Posted January 5, 2019 @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 Link to comment Share on other sites More sharing options...
Recommended Posts