Closed forkedcancel closed 4 years ago
Apparently I'm mistaken. It would seem the numbers are correct.
So that just means I've bricked my keyboard in some other way? I've tried flashing the precompiled hex files that come with the latest version of the repo but still the keyboard apparently sends nothing to the receiver.
Is there a chance I need to flash the receiver also? I'm a little worried about doing that now because I've already got 2 broken things, do I really want 3 broken things? But maybe that's the solution, to flash all 3 with the latest.
Aaaaand it turns out that was my problem. Seems all 3 needed to be updating. Closing.
I was having range issues (unreliable transmission within just a few feet) with my redox-w so I set out to change the tx power to 4dB. I updated the main.c to add that change and subsequently bricked my keyboard (mine came from Falbatech as partially assembled so I never had to flash anything other than qmk). Here is the output from program_left.sh. I am running Arch Linux for what it's worth.
I have tried setting WORKAREASIZE to 0, and to 0x10000 (64k), but no matter what it always says "wrote 16384 bytes." Is that correct? My hex file is like 43kb - shouldn't it be writing that many bytes (43832 to be exact) to the nRF51?
It seems like the answer to this is yes. Unfortunately I can't seem to find anyone talking about this problem when I search.
Any ideas?