Blueretro won't respond with v1.9.2_hw1_universal about blueretro HOT 10 CLOSED

That worked!

Thank you so much for all of the help, and let me know if you need me to run any more tests on this.

from blueretro.

Universal v1.9.2 work fine for me on my own adapter.

If possible with your adapter try to get the serial logs:
https://github.com/darthcloud/BlueRetro/wiki/Getting-BlueRetro-debug-logs-via-Serial-port-Windows-10

from blueretro.

Just got a chance to try this out. I get the following on loop every 10 or so seconds.
blueretro logs.txt

The main error seems to be:

# opcode: 0x0403 error: 0x0C retry: 0

assert failed: block_trim_free tlsf.c:496 (block_is_free(block) && "block must be free")


Backtrace: 0x400816fe:0x3ffd2500 0x40091a9d:0x3ffd2520 0x4009d8c1:0x3ffd2540 0x400d3f11:0x3ffd2660 0x400d3a2d:0x3ffd2680 0x400d33ea:0x3ffd26a0 0x400d341d:0x3ffd26d0 0x400d3449:0x3ffd26f0 0x4009d8e5:0x3ffd2710 0x400d93bb:0x3ffd2730 0x4009705c:0x3ffd27c0 0x40092711:0x3ffd27f0

from blueretro.

v1.9.2 now use the NVS partition, I guess somehow that area on your specific device got something into it that make the adapter crash when running with v1.9.2.

Try to reflash v1.9.2 and add the ota.bin 2 additional time at 0x9000 & 0xB000 to reset the NVS partition like so:

Full doc:
https://github.com/darthcloud/BlueRetro/wiki/Flashing-firmware-Windows-10

from blueretro.

Thank you! Just tried flashing those partitions as well, and I'm getting the exact same error. Do I just have a bad device, or could it be something else? In case this is relevant, my Blue Retro Core has an ESP-WROOM-32..

ETA: It looks like the ESP-WROOM-32 is the recommended chip in the BlueRetro docs, so it's probably not relevant.

blueretro logs2.txt

from blueretro.

Probably not if v1.9.1 work fine, I'll look into the change of v1.9.2 again. I might give you a few different build to test later this week.

v1.9.2 universal work fine for me on my N64 so this quite strange.

from blueretro.

Try to flash the ota bin at 0x310000 also.

On first power on it won't work right away, give it a good 1 minute to recreate it's partition (status led will be off) when its done the LED will start pulsing as usual.

Power off and power on again let me know if that work.

from blueretro.

v1.9.2 universal work fine for me on my N64 so this quite strange.

It doesn't actually seem to matter what console I try to use. I've tried booting the BlueRetro with an N64 cable, Wii Ext cable, or no cable at all, and I get the same issue with all of them.

Try to flash the ota bin at 0x310000 also.

I just tried, but the blue status led was on during the entire time it was formatting. Once it was finished, it was back to the same error message as before.

Thanks again for all of your help with this!

blueretro logs 3.txt

from blueretro.

I think the issue come from PS2 pressure buttons feature that is using a significant amount of HEAP memory.

I see the memory card malloc fail in v1.9.2 in mine now, look to be at same step yours crash. No sure why your crash.

Anyway in the latest beta I do not see the malloc fail (probably less memory usage due to the updated esp-idf)

Can you try the latest build?:
https://github.com/darthcloud/BlueRetro/actions/runs/8680779369

from blueretro.

Fixed in v24.04

from blueretro.