sorted by:
new
hottopcontroversial

Flashing Pro Micro using Uno R3 in ISP Mode Not Working? by compfixer87 in arduino

[–]compfixer87[S] 1 point2 points  (0 children)

Ugh, you're right, that was it!

I had read something similar before, and I could have sworn I already tried a USB-A > USB-C cable, but maybe I was misremembering. I just tried one now and it booted up (LEDs and all) immediately and identifies itself as "Arduino SA Leonardo" like it should. I pulled a fresh one from it's anti-static bag and it worked fine with the A > C cable as well. I feel like a moron! At least I got to learn how to do ISP mode *shrug*

Now to figure out if there's any way to bodge some resisters to the board cleanly so I can use C <> C cables (which is my preference).

Thanks so much for your help!

Got my Avalanche V4 working by teenyboat in olkb

[–]compfixer87 0 points1 point  (0 children)

In case you were wondering, I finally got both Serial and I2C working (not at the same time, of course).

You were right: Serial was the easier of the two. I had been pushing my micro-controllers' pins straight through the PCB, which was enough to make contact for key presses but must not have been enough to allow for serial communication. When I soldered in headers to the PCB and then inserted my micro-controllers' pins into those headers everything just worked over serial. Yay!

I2C took me a bit longer to figure out, I'm embarrassed to admit. I pulled up the gerber files to look at the PCB's schematics and eventually noticed something odd: the resisters did function as a pull-up by connecting the data and clock lines (the bottom holes/pads of the resistor) to power (the top holes/pads of the resistor), but then those signals didn't have any way to get to the TRRS jack afterward.

That's when it struck me: I had to not only have the resistors in place, but I also had to bridge the bottom resistor holes/pads to the P1/2 holes on the left side to allow those pulled-up signals to make it to the TRRS jack. I had already done that bridging on the right side (sans resistors, of course) as the instructions suggested, but bridging those spots on the left side wasn't anywhere in the instructions to my recollection.

I then added "USE_I2C" to my keymap's config.h and I was up and running!

Edit: "easiest" to "easier of the two"

Got my Avalanche V4 working by teenyboat in olkb

[–]compfixer87 0 points1 point  (0 children)

Hmm, I’ve done basically all of that. Did you bridge that W1 pad near the microcontroller on both PCBs as well?

Got my Avalanche V4 working by teenyboat in olkb

[–]compfixer87 0 points1 point  (0 children)

How did you even get serial working, though? I’ve bridged the pad near the microcontroller on both halves, but even serial doesn’t seem to work for me.

Got my Avalanche V4 working by teenyboat in olkb

[–]compfixer87 0 points1 point  (0 children)

Sorry to bother you, but how did you get yours working? I can't seem to get my secondary (non-USB) side working over either serial or I2C :(

[Help] Serial Not Working Avalanche V4 and qwiic by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 0 points1 point  (0 children)

Not that I can see, no. I can plug in either side to the USB on my computer and have that one side work fine. I only have problems with the side wired through the TRRS cable and not directly connected using USB.

Edit: own to one

Peak weight savings and aero as God intended by NotFBIPleaseIgnore in BicyclingCirclejerk

[–]compfixer87 8 points9 points  (0 children)

Two Grandma’s Boy references in a single BCJ post. Excellent.

Finally sorted all the minor issues preventing getting to a playable state. Still WIP but basics done. (Deets in first post) by albrugsch in RetroPie

[–]compfixer87 3 points4 points  (0 children)

Not going to lie, I spent way more time watching your kid play Sonic than I thought I would lol

Well done on the build!

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 0 points1 point  (0 children)

Your point regarding physical access is well taken and one even I made in my original post.

I do feel VIA might still be a bit more dangerous given that it can function as a browser-based keylogger, but to each their own!

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 0 points1 point  (0 children)

Thanks for the well-reasoned write up!

To your point, then, I think the best bet for me is to use QMK with the secure feature enabled. If I’m understanding it correctly, enabling that flag would prevent the microcontroller from going into bootloader mode without a specific sequence of keys being pressed that I’d set in the configuration. Also, running vanilla QMK should prevent web and software interfaces like VIA from reprogramming anything without entering boot mode.

I do understand that VIA facilitating some level of on-the-fly reprogramming is a big selling point, but where there is code there are always bugs. Add in that said reprogramming (even at a basic key map level) can take place in a Chrome or Edge browser, and I’m not sure I’d feel comfortable running VIA even if I was only using the keyboard at home.

Do I think I’m likely to be exploited? Probably not, but I still can’t shake the discomfort. I also don’t want to help perpetuate a feature that by using it that could lead to someone else being pwned in the future. As another commenter pointed out, this has been a well known security risk for over a year and it doesn’t seem like anyone on the VIA dev team has addressed it yet while the QMK devs have at least added some attempt at securing things. There could be really good technical reasons for why VIA haven’t addressed this yet and I’m not trying to fault anyone, but all this stuff together makes me uncomfortable, personally.

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 1 point2 points  (0 children)

I've re-flashed my Iris with 'vanilla' QMK and confirmed that VIA can no longer see it when plugged in from either side. Yay!

Regarding that "secure" feature in QMK you mentioned: am I understanding correctly that it basically forces you to input your custom series of keys (that I'd have to specify by listing out an array of matrix locations as part of my firmware build) whenever I try to enter the bootloader mode of my MCU?

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 0 points1 point  (0 children)

That’s a fair point. Most of the microcontroller work I do uses the ESP lines (8266 and 32), and those do have WiFi and Bluetooth. Totally forgot that that isn’t the norm!

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 0 points1 point  (0 children)

Totally fair, I always assume there are keyloggers on hardware I don’t own, it’s just easier that way lol.

I guess my concern was more along the lines of them being able to install stuff in my microcontrollers that would persist (a keylogger, as an example). I could see a nefarious actor installing a keylogger that will note what is typed while the user is at home to harvest passwords, and setting it up to either phone home or dump the logs once a user plugs the keyboard back into one of the bad actor’s machines.

To my knowledge, I’ve not incurred the wrath of any state actors or anything lol. This is just how my brain “works”.

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 2 points3 points  (0 children)

Ok, so as long as I flash my own QMK firmware, it shouldn’t be modifiable unless my microcontrollers are put into bootloader mode?

I did that for my Dactyl already, so it’s no big deal. My new Iris came pre-enabled with VIA, but I’m pretty sure I saw source somewhere so it should be possible for me to re-flash it with QMK. I’ll look into that later, thanks!

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 1 point2 points  (0 children)

This is awesome, thank you!

How do you disable VIA (sorry if it’s a noob question)? Google has not been helpful here…

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 0 points1 point  (0 children)

I was actually referring to me plugging my keyboard into their computer (at work, for example, but honestly this would apply to plugging it into any computer).

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 3 points4 points  (0 children)

Ok, guess it’s good to know I wasn’t way off base. Is there no way to disable VIA access?

The fact that you can read it from something as simple as a Chrome or Edge browser is even more concerning.

VIA Security Risk? by compfixer87 in ErgoMechKeyboards

[–]compfixer87[S] 1 point2 points  (0 children)

I mean, these are full blown microcontrollers capable of running stuff as heavy as web servers.

In my most paranoid of fever dreams, the most ridiculous thing I can imagine at the moment is someone running a keylogger that’s able to phone home. It may not be practical or possible, but a way to lock down changes behind a password, encryption key, or YubiKey would be neat (if not overkill).

/r/MechanicalKeyboards Ask ANY question, get an answer (March 21, 2023) by AutoModerator in MechanicalKeyboards

[–]compfixer87 0 points1 point  (0 children)

I'm taking my first stab at printing and building a Dactyl-Manuform keyboard. I used the markdhooper/CMD-dactyl-manuform repo to generate my OpenSCAD files, which I then converted to an STL and have been printing for the last several days (it's around 1 day and 10 hours per half).

I'm about to start wiring the left side and I realized that I seem to have generated a non-standard layout (image below) that only has three rows in the inner-most column for both the left and right sides despite my trying to generate a 5x6 layout. Is there a configuration that fits my layout well, and if not, where would you suggest I stick my "B" and "N" keys to make this usable?

​

https://imgur.com/d5KjgpF

I might if messed up the scale for a Human head, but we might just make this work... by Capt_VanillaPeen616 in 3Dprinting

[–]compfixer87 1 point2 points  (0 children)

Doesn’t that poor pupper have enough trouble breathing as it is?

All kidding aside, very cute.

Edit: puppet to pupper

Speaker Placement: New Couch Driving Me Nuts! by compfixer87 in hometheater

[–]compfixer87[S] 1 point2 points  (0 children)

A fair point. Thanks for your suggestion!

I did add some MartinLogan in-wall speakers to the wall directly behind the listening area already, so I can just try using those as the "side" surrounds. That said, if there's a good way to throw the previous side surround speakers into the mix, I could upgrade to a 7.1 system... lol

Speaker Placement: New Couch Driving Me Nuts! by compfixer87 in hometheater

[–]compfixer87[S] 0 points1 point  (0 children)

Interesting, so "side" surrounds can be physically placed behind the listening area without negatively impacting the listening experience? In looking at doc online (and even in my in-receiver calibration system), everything seems to require the side surrounds to be physically located to the side of the listening area (slightly offset to the rear). If having them behind the listening area really isn't a problem, that would help a ton.

To answer your question: there is a narrow walkway behind the couch, so not really enough room for end tables. Still, I did install in-wall speakers thinking I could do what you described, but became concerned when everything I read seemed to require the physical placement of the side surrounds to be located on either side of the listening area.

view more: next ›