pete11235 Posted November 20, 2018 Share Posted November 20, 2018 Hi - I ordered a 2gb Espressobin from Globalscale and later flashed flash-image-2g-2cs-1200_750.bin, which caused my Espressobin to hang at: TIM-1.0 WTMI-devel-18.07.0-6050fd5 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 0.898V I am able to boot to SATA using the sata recovery image, but cannot flash back to the working flash-image-2g-2cs-1000_800.bin. Here is what happens when I boot to SATA and attempt to flash the old bin: Booting Trusted Firmware BL1: v1.2(release):armada-17.02.0:v0.2-1324-g1cd562c BL1: Built : 16:29:17, Apr 20 2NOTICE: BL2: v1.2(release):armada-17.02.0:v0.2-1324-g1cd562c NOTICE: BL2: Built : 16:29:17, Apr 20 20NOTICE: BL31: v1.2(release):armada-17.02.0:v0.2-1324-g1cd562c NOTICE: BL31: U-Boot 2015.01-armada-17.02.0-01546-g184fa4e (Apr 20 2017 - 16:21:34) I2C: ready DRAM: 512 MiB Board: DB-88F3720-ESPRESSOBin 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: 1ff2b000 U-Boot DT blob at : 000000001fa18168 MMC: XENON-SDHCI: 0 SF: Unsupported flash IDs: manuf c2, jedec 2536, ext_jedec c225 *** Warning - spi_flash_probe() failed, using default environment PCIE-0: Link down SCSI: Target spinup took 0 ms. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs Net: neta0 Hit any key to stop autoboot: 0 Marvell>> bubt flash-image-2g-1000_800_boot_sd_and_usb.bin spi usb Burning U-BOOT image "flash-image-2g-1000_800_boot_sd_and_usb.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found reading flash-image-2g-1000_800_boot_sd_and_usb.bin Image checksum...OK! SF: Unsupported flash IDs: manuf c2, jedec 2536, ext_jedec c225 Failed to probe SPI Flash I initially attempted a UART flash, but I get a similar error, but with a different SF message: SF: unrecognized jedec id bytes: c2, 25, 36 I read through a few posts, tried things like flashing via tftp instead of USB, but to no avail. Can anyone help? Link to comment Share on other sites More sharing options...
skandalfo Posted November 21, 2018 Share Posted November 21, 2018 This looks like you are using (recovery) images that haven't been patched for supporting the Macronix flash chips. Did you check this thread? Link to comment Share on other sites More sharing options...
pete11235 Posted November 23, 2018 Author Share Posted November 23, 2018 So just got around to reading through that post and I gave it a go, using @FoodGenius's guide, however I am not able to write to the SPI after booting into the mini OS. I am now getting this error: / # ls /mnt/a / # ls /mnt a / # mount /dev/sda1 /mnt/a [ 101.293731] EXT4-fs (sda1): recovery complete [ 101.304031] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) / # cd /mnt/a /mnt/a # ls Image lost+found armada-3720-espressobin.dtb mtd0.img /mnt/a # dd if=mtd0.img of=/dev/mtd0 dd: can't open '/dev/mtd0': No such device /mnt/a # ls -l /dev/ total 0 crw--w--w- 1 1000 0 5, 1 Jan 1 00:02 console crw-r--r-- 1 0 0 90, 0 Nov 21 2018 mtd0 crw-r--r-- 1 0 0 90, 2 Nov 21 2018 mtd1 mtd0 definitely exists as you can see from the ls output, but I am not able to write to it. I don't know if the guide he followed was specific to his Espressobin and I need to modify the mini OS he built or its something else. I feel so close, its too bad that they don't have a recovery image that supports Macronix flash chips! Link to comment Share on other sites More sharing options...
martinayotte Posted November 23, 2018 Share Posted November 23, 2018 26 minutes ago, pete11235 said: mtd0 definitely exists as you can see from the ls output, but I am not able to write to it. Did you tried using "flashcp" from "mtd-utils" ? Link to comment Share on other sites More sharing options...
pete11235 Posted November 23, 2018 Author Share Posted November 23, 2018 @martinayotte - Just gave it a try, again its staying "No such device": /mnt/a # ls Image lost+found armada-3720-espressobin.dtb mtd0.img /mnt/a # flashcp -v ./mtd0.img /dev/mtd0 While trying to open /dev/mtd0 for read/write access: No such device /mnt/a # flashcp -v ./mtd0.img /dev/mtd0 ls -la shows: While trying to open /dev/mtd0 for read/write access: No such device /mnt/a # ls -la /dev/ total 0 drwxr-xr-x 3 1000 0 480 Jan 1 00:00 . drwxrwxrwt 11 0 0 280 Jan 1 00:00 .. drwxr-xr-x 2 0 0 40 Jan 1 00:00 .mount crw--w--w- 1 1000 0 5, 1 Jan 1 00:04 console crw-r--r-- 1 0 0 90, 0 Nov 21 2018 mtd0 crw-r--r-- 1 0 0 90, 2 Nov 21 2018 mtd1 crw-r--r-- 1 0 0 90, 4 Nov 21 2018 mtd2 crw-r--r-- 1 0 0 90, 6 Nov 21 2018 mtd3 crw-r--r-- 1 0 0 90, 8 Nov 21 2018 mtd4 crw-r--r-- 1 0 0 90, 10 Nov 21 2018 mtd5 brw-r--r-- 1 0 0 31, 0 Nov 21 2018 mtdblock0 brw-r--r-- 1 0 0 31, 1 Nov 21 2018 mtdblock1 brw-r--r-- 1 0 0 31, 2 Nov 21 2018 mtdblock2 brw-r--r-- 1 0 0 31, 3 Nov 21 2018 mtdblock3 brw-r--r-- 1 0 0 31, 4 Nov 21 2018 mtdblock4 brw-r--r-- 1 0 0 31, 5 Nov 21 2018 mtdblock5 crw-rw-rw- 1 1000 0 1, 3 Nov 21 2018 null crw-rw-rw- 1 1000 0 5, 2 Nov 21 2018 ptmx cr--r--r-- 1 1000 0 1, 8 Nov 21 2018 random brw-r--r-- 1 0 0 8, 0 Jan 1 00:00 sda brw-r--r-- 1 0 0 8, 1 Jan 1 00:00 sda1 crw-rw-rw- 1 1000 0 5, 0 Nov 21 2018 tty cr--r--r-- 1 1000 0 1, 9 Nov 21 2018 urandom crw-rw-rw- 1 1000 0 1, 5 Nov 21 2018 zero I'm pretty new to working with flash, so I'll apologize in advance if I am overlooking something stupid Link to comment Share on other sites More sharing options...
martinayotte Posted November 23, 2018 Share Posted November 23, 2018 6 minutes ago, pete11235 said: again its staying "No such device" What "cat /proc/mtd" is reporting ? Link to comment Share on other sites More sharing options...
pete11235 Posted November 23, 2018 Author Share Posted November 23, 2018 /mnt/a # cat /proc/mtd dev: size erasesize name /mnt/a # Link to comment Share on other sites More sharing options...
martinayotte Posted November 23, 2018 Share Posted November 23, 2018 So, it didn't found the flash chip ... On 11/20/2018 at 12:06 PM, pete11235 said: unrecognized jedec Probably you still have those in "dmesg" ... Link to comment Share on other sites More sharing options...
pete11235 Posted November 23, 2018 Author Share Posted November 23, 2018 I don't see that message in dmesg, heres the output from dmesg: https://pastebin.com/bmbzWL5k Link to comment Share on other sites More sharing options...
martinayotte Posted November 23, 2018 Share Posted November 23, 2018 26 minutes ago, pete11235 said: I don't see that message in dmesg, heres the output from dmesg: Your log still shows the following : [ 5.088391] m25p80 spi0.0: unrecognized JEDEC id bytes: c2, 25, 36 [ 5.094727] m25p80: probe of spi0.0 failed with error -2 Link to comment Share on other sites More sharing options...
pete11235 Posted November 23, 2018 Author Share Posted November 23, 2018 Oh I completely missed that! That's odd, I just confirmed that it is a Macronix chip, in fact the exact one they talk about in the referenced thread above (mx25u3235f - attached picture of it). I don't understand what I am doing wrong... Link to comment Share on other sites More sharing options...
pete11235 Posted November 23, 2018 Author Share Posted November 23, 2018 I am an idiot, I didnt go far enough down in the forum, I got it working using this method: 1 Link to comment Share on other sites More sharing options...
Recommended Posts