Closed ghostbuster91 closed 1 week ago
I doubt your display is broken by flashing different firmwares. Just in case the setting got scrambled, I would try toggling external power off/on so that you can make sure it is on on both sides. Then wait a minute (so the setting is persisted to flash), and reset the controller. (Sometimes display doesn't boot up properly on ext. power on but it can boot after a reset.)
It looks like you figured out what happened: The nice!view got a custom status screen in the last year, and the .conf settings you used don't apply to them.
If I were you I wouldn't bother testing the old firmware. I'd flash the new one (if you want you can disable the custom screen https://github.com/zmkfirmware/zmk/issues/1273#issuecomment-1712938706 and keep your .conf settings) and test that. As an aside, you might want to use ZMK main along with https://github.com/dhruvinsh/zmk-tri-state module instead of nickconway's ZMK fork (which needs to be manually updated).
Then wait a minute (so the setting is persisted to flash)
What setting do you have in mind here?
Thanks for the suggestions. I tried restarting it on a battery and on ext_power. Still the issue persists :(
What setting do you have in mind here?
I mean the internally stored state of the external power toggle. When you use e.g. &ext_power EP_ON
, the state gets saved to storage after one minute (to reduce flash wear on repeated uses).
I don't have other suggestions, but if you make a help post on the Discord maybe other folks can comment.
Got you. Thanks for your suggestions. I will look for more help on discord.
I am going to close the issue for now. If I get some new information that will be worth sharing I will post it here and we might then reopen.
Hi,
I have a custom keyboard with a self made shield - https://github.com/ghostbuster91/Dilemma3x6_3-zmk This is a split keyboard equipped with nice!nanos & nice!views. More about the keyboard here.
Today I updated the firmware in the left half (master). Previous firmware version was from almost a year ago. I am using a fork of zmk which is fairly up-to-date: https://github.com/nickconway/zmk/
The keyboard used to work well so far with both displays.
The update didn't go smoothly as first the build failed with following errors:
At first, I decided to just comment out anything custom connected with the display and see if the build will pass (commit).
It did so I installed new firmware on the board. After that, I noticed that the display stopped working. It started to show some gibberish. I thought that maybe this is due to some misconfiguration on my side.
I found this issue which mentions the same errors and applied the suggestion. This fixed the compilation so I uploaded new firmware on the board. However, the screen remained borked. I thought that it might be due to https://github.com/zmkfirmware/zmk/issues/1749
After this I decided to build the old firmware once again using the zmk revision from the day the of the last commit in my repository. That was 19 Jul, so I took f3110d1d1ea195725551b4c997c542a4003e1452 which is right before:
The build passed without any issues - https://github.com/ghostbuster91/Dilemma3x6_3-zmk/pull/4 and I uploaded it on the board. However the screen issue remains.
Below, photo of both halves, the right one with updated firmware and the left one with the original one.![image](https://github.com/zmkfirmware/zmk/assets/5662622/724c69dd-7d07-4535-8a70-6161fe483be4)