Surfans F20 "NAND open error"

[mxl]

Thanks for the quick reply

[GraFfiX]

I bought a Surfans F20 Player as well and I want to install the native port on it.
[...]
Is it save to proceed with the installation of the native port with the latest (v7) bootloader from this thread?
[...]
Flash info:
readID opcode  = FF C8 D1 C8
readID address = C8 D1 C8 D1
readID dummy   = D1 C8 D1 C8
[...]

This shows you have the GigaDevice flash (same as JosephM's) so yes it's safe to install with the v7 bootloader.

I installed the ROCKbox native port from the v7 bootloader, after a success message I first booted into ROCKbox from the BOOT Menue, this worked.
Then I rebooted and I just got a flickering screen.
So I powered the device off by long pressing power.
A new press on power just gives me the flickering screen again...
So I loaded the v7 bootloader from command promt again...
I reinstalled ROCKbox and powered off after.
I pressed power again and all I got is a flickering screen again.
So I started the bootloader again and created a Flashdump and the info files again.
here are they https://mega.nz/file/jTQS1K6Y#2OMx0mlbN7KqH24NBsz7AEeZqBCtWyXwTirj_9ecDxM

Then I restored the original bootloader. Now the player is working again with its original Firmware (not with ROCKbox sadly). I hope you will have success in getting the thing working with ROCKbox! If you need something else from me I try to provide it to you.

I don't know what the issue is, but if you try a few things it might help narrow things down:

• Go into the bootloader menu (hold volume up when powering on) and boot Rockbox - see if the LCD flickers
• Boot the original firmware from the bootloader menu - check if the LCD works
• Boot the original firmware by holding PLAY when powering on

Also if you could explain what you mean by the screen "flickering" that would help. Can you see the Rockbox logo or menus? Do they look corrupted? Or do you see randomly colored "noise"? Better yet, post a video of the problem if you can. It doesn't have to be great, as long as the problem is visible.

Greetings, I recently acquired one of these players, and I'm having trouble getting the bootloader flashed on the device. I can boot the bootloader, but the image on the screen is flipped and inverted?

These are the parameters:

Code: [Select]

readID opcode  = FF EF AA 21
readID address = EF AA 21 00
readID dummy   = EF AA 21 00
sfc params0  = 06 05 04 03
sfc params1  = 02 55 AA 55
sfc params2  = 00 61 02 02
sfc params3  = B4 2F 00 00
Any clue what changes I could make to get the screen to present properly, and get the bootloader to install to my device? I can provide any further info you need. Thanks.

[amachronic]

That flash should be one of the supported ones. Could you try getting a backup dump (Bootloader > Backup)?

Try one of these builds to fix the LCD:

• Flipped: https://drive.google.com/file/d/15_B6O7VlvhZckoQ7RnxHAsJ11-aV0A-J/view?usp=sharing
• Inverted: https://drive.google.com/file/d/1me64CVVZ_kYmM5ox7fledYMrrfO6jR_k/view?usp=sharing
• Flipped + inverted: https://drive.google.com/file/d/1l9cacil9olcyvPd3w4cg6l7n78Y3KptL/view?usp=sharing

[GraFfiX]

That flash should be one of the supported ones. Could you try getting a backup dump (Bootloader > Backup)?

Try one of these builds to fix the LCD:

• Flipped: https://drive.google.com/file/d/15_B6O7VlvhZckoQ7RnxHAsJ11-aV0A-J/view?usp=sharing
• Inverted: https://drive.google.com/file/d/1me64CVVZ_kYmM5ox7fledYMrrfO6jR_k/view?usp=sharing
• Flipped + inverted: https://drive.google.com/file/d/1l9cacil9olcyvPd3w4cg6l7n78Y3KptL/view?usp=sharing

Thanks so much! The inverted version worked. Here is a backup of the bootloader:
https://drive.google.com/file/d/1EngBxCV74uR06bXdygffZGASd7m4nvzs/view?usp=drive_link

[amachronic]

Nice, now we just need to find out how to detect the LCD automatically.  

Are you able to flash that bootloader? If it still gives errors please post what it says.

[GraFfiX]

Nice, now we just need to find out how to detect the LCD automatically.  

Are you able to flash that bootloader? If it still gives errors please post what it says.

Yes, the bootloader flashed successfully. One difference I did notice, normally the bootloader menu is black background with white lettering, using this version, it's white background with black lettering. Other than that, I don't see any differences.

[GraFfiX]

Nice, now we just need to find out how to detect the LCD automatically.  

Are you able to flash that bootloader? If it still gives errors please post what it says.

So, unfortunately, it looks like the colors are actually inverted on my display. I didn't notice it until I ran Quake. It's odd, because using the "lcd-invert" files you sent actually flips the display for me, but using the "lcd-invert+flip" results in the colors matching, but the display/lettering is all still backwards. Do you have any suggestions? I have the source, and can compile it successfully, but I'm not sure exactly where in the source the LCD orientation is. Thanks again for your help.

EDIT** I spoke too soon, while this build does work, I tried to actually use the device today. When the screen went to sleep, the display would not light up again. After holding down the power button, it did turn off, but first it showed the "Surfans" logo screen, however it was flipped and not inverted. Would really appreciate any tips you could give me.

[amachronic]

Ok, so the LCD configuration is in firmware/target/mips/ingenic_x1000/erosqnative/lcd-erosqnative.c. Vertical/horizontal flip is controlled by this command:

Code: [Select]

    /* Set Address Mode */
    LCD_INSTR_CMD,      0x36,
    LCD_INSTR_DAT,      0xd8,

The data byte is what controls the orientation. Bit 7 = vertical flip, bit 6 = horizontal flip. The "inverted" build is just a horizontal flip, so 0xd8 becomes 0x98. Bit 3 is RGB/BGR order, so changing that may help fix the colors.

Another thing you can try is adding the "display invert on" command (0x21), assuming the default is non-inverted; maybe also try 0x20 "display invert off" just in case it defaults to on for some reason.

Code: [Select]

    // vvv add this
    LCD_INSTR_CMD, 0x21,
    // ^^^
    /* Exit Sleep */
    LCD_INSTR_CMD,      0x11,
    LCD_INSTR_UDELAY,   120000,
    /* Display On */
    LCD_INSTR_CMD,      0x29,
    LCD_INSTR_UDELAY,   20000,
    LCD_INSTR_END,

To stop the display from going to sleep you can comment out / remove the code in lcd_tgt_sleep(), the backlight will still turn off but the controller will keep running normally.

I don't remember if dconrad ever figured out what the display controller was... not that it would help since you could have a different one, but most of them support a similar command set (called MIPI DCS) and you can check eg. the ILI9341 datasheet for info.

[GraFfiX]

Ok, so the LCD configuration is in firmware/target/mips/ingenic_x1000/erosqnative/lcd-erosqnative.c. Vertical/horizontal flip is controlled by this command:

Code: [Select]

    /* Set Address Mode */
    LCD_INSTR_CMD,      0x36,
    LCD_INSTR_DAT,      0xd8,

The data byte is what controls the orientation. Bit 7 = vertical flip, bit 6 = horizontal flip. The "inverted" build is just a horizontal flip, so 0xd8 becomes 0x98. Bit 3 is RGB/BGR order, so changing that may help fix the colors.

Another thing you can try is adding the "display invert on" command (0x21), assuming the default is non-inverted; maybe also try 0x20 "display invert off" just in case it defaults to on for some reason.

Code: [Select]

    // vvv add this
    LCD_INSTR_CMD, 0x21,
    // ^^^
    /* Exit Sleep */
    LCD_INSTR_CMD,      0x11,
    LCD_INSTR_UDELAY,   120000,
    /* Display On */
    LCD_INSTR_CMD,      0x29,
    LCD_INSTR_UDELAY,   20000,
    LCD_INSTR_END,

To stop the display from going to sleep you can comment out / remove the code in lcd_tgt_sleep(), the backlight will still turn off but the controller will keep running normally.

I don't remember if dconrad ever figured out what the display controller was... not that it would help since you could have a different one, but most of them support a similar command set (called MIPI DCS) and you can check eg. the ILI9341 datasheet for info.

Thanks! That worked beautifully. I set the address mode instr_dat to 0x98, and added instr_cmd 0x21 per your instructions, everything is displayed properly now. I haven't tested the sleep fix yet, but I will report back when I do.

[coomer101]

Hi all,
I recently received an aigo eros Q running a v1.9 firmware
Had the nand issue using the bootloader linked on the wiki page
As posted before (thanks!), this boot loader worked.
https://drive.google.com/file/d/1S5HsTPbqPpBoyJExfhBcXRpEUkh86xGk/view?usp=sharing

Can we get this bootloader added to the wiki?
The only way I was able to get this installed is via this thread, so I'd hate for the links to die
I opened it up to confirm the nand chip as well.

[amachronic]

Yeah, I need to tag a new 'official' bootloader release -- we've had other features like GPT partition table support added since the last one.

[coomer101]

Yeah, I need to tag a new 'official' bootloader release -- we've had other features like GPT partition table support added since the last one.

Oh wow, yes please do!
I also have a Surfans F20 on a v3.1 firmware, I'll look into getting the native port on it on my next day off.
Any idea if I can just install one of the older firmwares and then go about installing the native port as usual?
It also came in a different box than the F20 I got last year, why do they keep changing stuff lol
As far as I can tell it's functionally identical to v2.7, so wtf is the point with these annoying revisions?

[speachy]

> Any idea if I can just install one of the older firmwares and then go about installing the native port as usual?

In a word:  Don't.

There are numerous hardware changes, and I've seen multiple reports that installing (eg) 2.7 on top of 3.0 causes audio output to stop working, and it's nto clear that Surfans will supoprt you if complain.

In theory a single software image could detect the hardware revision and behave accordingly, but that requires (1) hardware to report a revision number and (2) the software to check (and care).

If someone can get me the various surfans firmware files for these later hardware revisions I can generate pre-patched update files for the *hosted* port, but if you're looking to load up the native port, IIUC that doesn't matter.

[coomer101]

> Any idea if I can just install one of the older firmwares and then go about installing the native port as usual?

In a word:  Don't.

There are numerous hardware changes, and I've seen multiple reports that installing (eg) 2.7 on top of 3.0 causes audio output to stop working, and it's nto clear that Surfans will supoprt you if complain.

In theory a single software image could detect the hardware revision and behave accordingly, but that requires (1) hardware to report a revision number and (2) the software to check (and care).

If someone can get me the various surfans firmware files for these later hardware revisions I can generate pre-patched update files for the *hosted* port, but if you're looking to load up the native port, IIUC that doesn't matter.

Would love to help, just tell me what to do lol

[mic64]

Hi All

I was able to build a native version for my HiFi Walker FW 1.7 with this help.
I can at least use it in the Bootloader and the Player.
But the Colors are still wrong. Any theme with covers looks wrong. like inverted. Also the Bootloader Menu is white.
So just text themes for now :-)

You mention above that "Bit 3 is RGB/BGR " and this could help fix the colros.
 How can I add this to the /lcd-erosqnative.c

it looks like this now
    /* Set Address Mode */
    LCD_INSTR_CMD,      0x36,
    LCD_INSTR_DAT,      0x98,

thank you