Can not configure keyboard (singa unikorn) in VIA

[n.rdy]

I'm not sure what I did wrong here but I just got done with my first proper build and things seem to have gone awry. After soldering and assembling I went back into VIA to use the key tester; all is well at this point. I go into the configure tab, it detects the keyboard instantly and I begin customizing the layout. I save it and go back into the key tester and this is where it gets not so fun.

As im pressing each key I realize its not actuating the correct key. For example: when I press W it inputs Q, E inputs W and it follows that all the way down the board. Same with S being A and down and X being Z.

I went back into the configure tab and via just turns..blue. All that is available is "file" at the top left with the options to "import keymap" or "close." When I close and reopen VIA, I can get into the key tester if I'm quick enough but as soon as I try to go into the configure tab, it loads about 75% and just turns blue.

I tried to go into QMK to load the default firmware but as far as I can tell there is no way to reset this keyboard. Google really didn't turn up anything useful.

I'm not sure what I did wrong or how to fix it so If anyone has any idea how to fix this, I would really appreciate it.

[mcRewind]

+1

also having some issues with the layout on via. Here's how mine looks.



My keyboard itself is able to work just fine, but because of this, I'm not able to access programming keys like "q," "a," "enter," or even my split right shift.

[gnho]

You may want to go to QMK discord for this question.

[n.rdy]

+1

also having some issues with the layout on via. Here's how mine looks.

Show Image

My keyboard itself is able to work just fine, but because of this, I'm not able to access programming keys like "q," "a," "enter," or even my split right shift.

apparently i dont get post notifications so i apologize for the delay. what i ended up doing was saving the json and manually editing everything. im not sure where it gets weird but i literally went and changed every key until it was working properly. it didnt show up correctly in the configure tab but in the key tester it accurately represented what was actually happening. 

whatever you do, though, do not click on split in the configure tab. it took me and several other people from discord to figure out how to rectify the issue. turns out i didnt have the proper c++ whatever installed so i couldnt run bootloader to run the stock firmware. if youre still having trouble figuring out, ill attach the layout that i had used.