Surfans F20 "NAND open error"

[twotoneblue]

Dear amachronic and kaas,

I hope I am not interrupting your exchange, but if it helps, here is a backup of the native bootloader taken after loading amachronic's bootloader v4 with jztool (https://drive.google.com/file/d/1xvTcsPqMgWUUic_VzPFrYSAAqe117ugT/view?usp=sharing). Albeit not requested at this point, I also made a zip archive of (all) the available debug dumps (https://drive.google.com/file/d/17irOvVhWSZW18bn6DYpiDMTG0yMFHyEo/view?usp=sharing).

As for running Rockbox from the bootloader menu; I extracted the zip of the native Rockbox (should it have been a daily hosted build?) onto the SD card and started it from the bootloader menu. It runs and plays a FLAC file with no noticeable problems. The only thing I saw was the message: "error accessing playlist control file" as I unplugged the USB connection to the computer.

Notably, while some tiny pops can be heard when plugging into the Line Out, no sound comes out of it during playback.

[amachronic]

...

Thanks, you did everything right. Aside from line out not working, it sounds like Rockbox runs fine. But isn't that the same as the hosted build?

The ONFI info is okay and matches up with the Winbond datasheet. The raw values are correct but I got the endianness wrong in the dumper, so the text dump appears wrong. It seems there's still something wrong with the flash read, some pages are being read as 0xff intermittently and some are getting zeros prepended to them. So we're not quite there yet, but getting closer.

[amachronic]

Turns out I didn't put the chip into buffered read mode. That's fixed, also fixed the ONFI dumper. Maybe this build will actually work? Either a full flash dump or bootloader backup should be enough to confirm.

https://drive.google.com/file/d/1a5GbTZWmyxsgglfdRjHJ4EfXoyEZBCZD/view?usp=sharing

[twotoneblue]

Hi,

Interesting! It seems that this time the readable text (e.g. "Winbond") in the ONFI dump is gone again. Debug files and bootloader backup at https://drive.google.com/file/d/11mzSyUDyyRi6DGnfWFrtbZQOpWC43cwo/view?usp=sharing.

Rockbox runs and plays fine apparently. No USB-related error message this time. No sound in Line Out.

My sincerest thanks for your continued efforts, amachronic!

[twotoneblue]

But isn't that the same as the hosted build?

Btw, sorry I forgot to answer this; yes, it is the same functionality as observed with the hosted build :-)

[kaas]

Turns out I didn't put the chip into buffered read mode. That's fixed, also fixed the ONFI dumper. Maybe this build will actually work? Either a full flash dump or bootloader backup should be enough to confirm.

https://drive.google.com/file/d/1a5GbTZWmyxsgglfdRjHJ4EfXoyEZBCZD/view?usp=sharing

Hi, would it still help if I do this as well (or the one you posted previously), or is twotoneblue's backup enough for now?

[amachronic]

You're welcome to try another backup, but unfortunately twotoneblue's backup is showing the same issue as before and it's safe to assume yours would too. I haven't had time to investigate further.

In case anyone is interested the bootloader sources are on Gerrit, and Linux also supports this flash, so maybe that's useful as a reference.

[amachronic]

Looks like I left all the timing parameters at the minimum defaults, so I think commands were being sent to the flash too quickly and that's why the read data was all wrong. Now I've increased the timings so the delay between commands is longer. Here's a new bootloader to try. Fingers crossed...

[twotoneblue]

The output from this version looks very reasonable to my untrained eyes! 

https://drive.google.com/file/d/1jorB9t9JSbcazm8ZPJwVyVw5aecDNvrK/view?usp=sharing

[amachronic]

Looks good to me! The dump matches up with the v2.7 firmware images.

All that's left to do is try installing the v6 bootloader build and see if it can boot Rockbox and the original firmware.

[twotoneblue]

Great!

First, for good measure; a corrected zip with the bootloader backup - I forgot this file in the previous one: https://drive.google.com/file/d/1-zqsdh3BWI4Q0mxOGWuB8L2nor_43X7W/view?usp=sharing

I ran the install and update from the bootloader menu with success (having renamed the bootloader-v6 file to "bootloader.erosq" on the SD-card, else the installation gives a file not found error, naturally), and the latest native rockbox seems to start fine. Dual boot also works, so this looks good.

[amachronic]

Cool!

I'll update the official bootloader builds and wiki soon. I think it's pretty safe to say newer Surfans F20 units with FW v2.7 are now supported.

[twotoneblue]

Nice work, amachronic - many thanks!

The native dual boot setup is a good one to have, providing the rockbox goodness for headphones, but also catering for the occasional need for the line out or the bluetooth function throught the aigo player.

Speaking of which, now that the status of Surfans F20 v2.7 will be moved to supported, should I open a separate thread/issue (or even bug report) about the silence of the line out? And, would you have any ideas on how one can proceed to investigate this problem?

My sincerest thanks again for your efforts!

[JosephM]

Cool!

I'll update the official bootloader builds and wiki soon. I think it's pretty safe to say newer Surfans F20 units with FW v2.7 are now supported.

I hate to revive the thread, but I don't think that's the case. I got a new unit today with the 2.7 FW and it seems like it has yet another flash chip. (Or at least I'm hitting the same nand read error, even with the v6 bootloader.) Using the debug code provided, I got

Code: [Select]

readID opcode  = FF C8 D1 C8
readID address = C8 D1 C8 D1
readID dummy   = D1 C8 D1 C8
sfc params0  = 06 05 04 03
sfc params1  = 02 55 AA 55
sfc params2  = 00 63 02 02
sfc params3  = A4 2F 00 00
which from looking at the Linux SPI Nand identification code makes me think it's the GigaDevice GD5F1GQ4UExxG. https://www.gigadevice.com/datasheet/gd5f1gq4xexxg/

[Falco98]

I think it's pretty safe to say newer Surfans F20 units with FW v2.7 are now supported.

That's good news.  The unit I bought a couple months ago came with 2.7 and I felt a little "dirty" forcing a downgraded FW version (2.5) onto it, even though that worked about as well as we expect any builds to work at present (AFAIK).  Can you advise me whether I should try upgrading soon?  I've enjoyed following the tech discussion here, but must admit it's somewhat over my head.

Also, purely as an aside: this unit is eventually intended for my FIL to be his car music player (hardwired, since we already know BT is off the table for the foreseeable future), but the one thing that'll need to be working before that is for USB charging to function correctly (just fwiw); since it boots to USB now instead of to the player, i'm afraid it won't work for him since I'd be telling him to just leave it plugged in in his car.  Just mentioning this here in case anyone has any insight as to whether i should expect this to ever be fixed.