Help debug my "bricked" PCB

[_rubik]

To get some specs out of the way:
- primekb x aio3 meridian rev 1.0 20200419
- qmk with via

I hadn't flashed the board since I initially set it up a few years back. I wanted to play it safe, so I backed up my config with Via, compiled the default primekb/meridian QMK keymap, and flashed it. That works, and I have the default config up and running. I edit the keymap with a few smell tweaks, re-compile, flash, and get this message:

Code: [Select]

Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations
Clearing status
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash  "
Downloading element to address = 0x08000000, size = 40088
Erase    [=========================] 100%        40088 bytes
Erase    done.
Download [=========================] 100%        40088 bytes
Download done.
File downloaded successfully
Submitting leave request...
Transitioning to dfuMANIFEST state
Bummer. But for whatever reason, that default keymap was still loaded. I could make changes in Via, fail to flash again, and those changes persist. It's not totally bricked, I guess, so that's good news. My experience with firmware is limited. Can folks help me start debugging; I'm at a loss

[_rubik]

Reserved for updates

[Sup]

Have you tried to clear the EEPROM and then reflash it with the VIA file? Also you can maybe try the precompiled firmware here https://www.caniusevia.com/docs/download_firmware

[_rubik]

Have you tried to clear the EEPROM and then reflash it with the VIA file? Also you can maybe try the precompiled firmware here https://www.caniusevia.com/docs/download_firmware

I got distracted with a new Corne build. I'll give the EEPROM clear a stab tonight. I was under the impression that something was AWOL with the bootloader and I'd have to do some ISP flashing

[_rubik]

Oh I completely forgot. The Meridian V1 runs an SMT32 which doesn't have eeprom. I think there's some eeprom emulation, but I don't think that can help me here