(Programming HELP) Hand Wired Failure

[Moistgun]

I recently have put together a hand wired keyboard using a teensy, attempting to follow along with Matt30s guide on DT using TMK software.

It is a 60% Apple Extended Keyboard 2. 
and has a non standard bottom row.

https://deskthority.net/workshop-f7/how-to-build-your-very-own-keyboard-firmware-t7177.html
I'm thought that I followed the instructions and made all the changes needed based on the link, but that must not have been true because it did not work.

I don't know if correctly followed the second part where I changed the keymap_plain.c file to my needs, but the main problem is that I don't know how to compile the documents into something I can flash the teensy with in the first place.
I cant tell if the layout works or what not because I don't know how to make a hex file.

I tried to use winAVR but I don't know what I'm doing.
EDIT: seems as though there are WinAVR issues with Windows 10

[MOZ]

If you can share the matrix, I can guide you on using EasyAVR, if you are up fr that. It's fairly simple.

[3K]

You need to scroll down in his guide, matt3o wrote some extra lines for compiling. The folder you provided did'nt compile for me, however your GH60 (I figure you used this one, as matt30 suggests in his tutorial) folder pasted into my TMK blank folder compiled.

The theory is to navigate to the GH60 folder and run some piece of software to compile.

[Moistgun]

If you can share the matrix, I can guide you on using EasyAVR, if you are up fr that. It's fairly simple.

The matrix should be in the dropbox file I linked, will that suffice? I would love the help. just let me know what to give you

You need to scroll down in his guide, matt3o wrote some extra lines for compiling. The folder you provided did'nt compile for me, however your GH60 (I figure you used this one, as matt30 suggests in his tutorial) folder pasted into my TMK blank folder compiled.

The theory is to navigate to the GH60 folder and run some piece of software to compile.

Show Image

Im not sure I know what you mean it pasted into your blank folder compiled.


When I try to run what you have in the command prompt i get
makefile 133 ..tmk_core/protocol/lufa.mk no such file or directory
makefile 134 ..tmk/common.mk no such file or directory
makefile 135 ..tmk_core/rules.mk no such file or directory
make *** no rule to make target tmk_core/rules.mk stop.

[3K]

Yes, that's what I get too, when compiling out of your folder. I'm pretty sure your folder is missing some files. Did you try redownloading?

[Moistgun]

Yes, that's what I get too, when compiling out of your folder. I'm pretty sure your folder is missing some files. Did you try redownloading?

I haven't had a chance to re-download it, but I could do that.
I can just paste in the files that I changed I guess, but that is assuming I did it right in the first place.

Don't I need to run WinAVR and use the command prompt within that program so it can have the ability to compile it?
If thats the case, I cant figure out how to do that.

When I get home, I will try out the EasyAVR and see if I can make that work.
Too many options!

[3K]

Yes, that's what I get too, when compiling out of your folder. I'm pretty sure your folder is missing some files. Did you try redownloading?

I haven't had a chance to re-download it, but I could do that.
I can just paste in the files that I changed I guess, but that is assuming I did it right in the first place.

That's what I would suggest you to do.

Don't I need to run WinAVR and use the command prompt within that program so it can have the ability to compile it?
If thats the case, I cant figure out how to do that.

When I get home, I will try out the EasyAVR and see if I can make that work.

I'm not quite sure, but I only used WinAVR after compiling. Only to flash the readily compiled software to the teensy.

[MOZ]

If you can share the matrix, I can guide you on using EasyAVR, if you are up fr that. It's fairly simple.

The matrix should be in the dropbox file I linked, will that suffice? I would love the help. just let me know what to give you

If you can provide an excel file with your pin matrix and layout, that would help.

[Moistgun]

If you can provide an excel file with your pin matrix and layout, that would help.

I have put together the matrix in an excel file

https://www.dropbox.com/s/7qm62sy3w87se4q/Matrix%20and%20Pins%20.xlsx?dl=0

Moz or whoever cares. please take a look and let me know what you think.

[Moistgun]

Tried my hand at using easyAVR by myself with no luck.

[3K]

Tried my hand at using easyAVR by myself with no luck.

What exactly is not working? Also did you try winavr as matt3o suggested?

When done, run the teensy loader, activate the "Auto" button, load the firmware (the hex file) and press the reset button on the teensy. The firmware will be uploaded and the keyboard will start working right away!

[Moistgun]

Tried my hand at using easyAVR by myself with no luck.

What exactly is not working? Also did you try winavr as matt3o suggested?

When done, run the teensy loader, activate the "Auto" button, load the firmware (the hex file) and press the reset button on the teensy. The firmware will be uploaded and the keyboard will start working right away!

I don't have any issues getting a hex file onto the teensy.
My problem is in compiling a new hex file after changing all the documents in the TMK folder.

I have since re downloaded from a more recent thread, and might have made progress on what files I needed initially.
Also I worked through them with a little more concentration and a little less frustration this go around.

I have the files ready to be compiled but I still don't know if it will compile or really how to with winAVR. Im at work and cant run the .exe files on this machine anyways.

[MOZ]

Place this file in C:\users\<username>\.EasyAVR folder (Or something along those lines).
https://www.dropbox.com/s/by4z2tza46rmhwg/moistgun60.py?dl=0

You will need to edit the file according to how your LEDs are wired.

[Moistgun]

Place this file in C:\users\<username>\.EasyAVR folder (Or something along those lines).
https://www.dropbox.com/s/by4z2tza46rmhwg/moistgun60.py?dl=0

You will need to edit the file according to how your LEDs are wired.

Error 429
Will do it eventually!

[MOZ]

Sorry. Didn't know my Dropbox was this popular :/

https://drive.google.com/file/d/0B5XIrLtiUwFVYkxjRUV6UkRuMDA/view?usp=sharing

[Moistgun]

Sorry. Didn't know my Dropbox was this popular :/

https://drive.google.com/file/d/0B5XIrLtiUwFVYkxjRUV6UkRuMDA/view?usp=sharing

You truly are king of the newbies.

Thanks MOZ

I will give it a shot when I get home.

[Moistgun]

Since I have no indicator leds, will this section cause any issues?

# The total number of LED outputs (indicators + backlights)
num_leds = 2
# The number of LED indicators (for example, caps lock)
num_ind = 2
# The number of backlight enable modes.  This counts the number of
# options available for the BL_ENABLE key
num_bl_enab = 2

[MOZ]

Shouldn't. I assigned unused pins.

[Moistgun]

Shouldn't. I assigned unused pins.

Im home.

I dont know what im supposed to do with that .py file you gave me.

[Moistgun]

Tried TMK again and no luck. likely due to dirty code and reversed diodes in the software???

[Moistgun]

Was finally able to compile the hex file using TMK on linux, but Idk I'f that's corrupt or my hardware is jacked, but this thing is ****ed.

If I press a number key I get the correct output, k cool, but if I press a key in the qwerty row, it inputs all keys in that column,  so the s key outputs 2wsx and so on.   Then it gets worse as I tinker with it making me shut down my computer,

because once the tmk teensy has been plugged in, my soarers model m and my tmk gh60 stop working all together until I restart windows.

[user 18]

Was finally able to compile the hex file, but Idk I'f that's corrupt or my hardware is jacked, but this thing is ****ed.

If I press a number key I get the correct output, k cool, but if I press a key in the qwerty row, it inputs all keys in that column,  so the s key outputs 2wsx and so on.   Then it gets worse as I tinker with it making me shut down my computer,

because once the tmk teensy has been plugged in, my soarers model m and my tmk gh60 stop working all together until I restart windows.

That sounds more like a hardware issue than an issue with the firmware.

[Moistgun]

That sounds more like a hardware issue than an issue with the firmware.

Thats where my guess was leaning towards. Maybe the diode direction?

Edit Resistor - diode

[user 18]

That sounds more like a hardware issue than an issue with the firmware.

Thats where my guess was leaning towards. Maybe the resistor direction?

Resistors are directionless. If you used resistors in the matrix, that's a problem. You should be using diodes.

Diode orientation does matter.

[MOZ]

Shouldn't. I assigned unused pins.

Im home.

I dont know what im supposed to do with that .py file you gave me.

Download the latest release from here: https://deskthority.net/wiki/Easy_AVR_USB_Keyboard_Firmware

1. Run Easy AVR once.
2. Exit.
3. Copy the file I uploaded to C:\users\<username>\.EasyAVR folder (Or something along those lines).
4. Run Easy AVR again, Go to File -> New Default layout and choose "Moistgun's 60"
5. Configure
6. Build Firmware
7. Load onto Teensy.

[Moistgun]

Shouldn't. I assigned unused pins.

Im home.

Download the latest release from here: https://deskthority.net/wiki/Easy_AVR_USB_Keyboard_Firmware

1. Run Easy AVR once.
2. Exit.
3. Copy the file I uploaded to C:\users\<username>\.EasyAVR folder (Or something along those lines).
4. Run Easy AVR again, Go to File -> New Default layout and choose "Moistgun's 60"
5. Configure
6. Build Firmware
7. Load onto Teensy.

I dont know what im supposed to do with that .py file you gave me.
the closest thing resembling what youre talking about is this folder.
\Desktop\easykeymap_windows_2_01_09\library\easykeymap\boards

this has all the boards you see in the new default layer window, but putting the moistgun60 file in there doesnt make it show up.  also all the files in that folder are .pyc files, not .py files

[Moistgun]

If I have a .py file from MOZ for EasyAVR,
does anyone know what im supposed to do with it to make it show up in the default layers when starting up the program? 

I have the file, but putting it in different folders isn't making it show up in the program.

[3K]

If I have a .py file from MOZ for EasyAVR,
does anyone know what im supposed to do with it to make it show up in the default layers when starting up the program? 

I have the file, but putting it in different folders isn't making it show up in the program.

Did you install a copy of Python? Did you read and try this https://github.com/dhowland/EasyAVR/blob/master/README.md#windows-user-tutorial ?

I have no idea what MOZ is, never used EasyAVR, nor experienced most of your problems, but maybe this could help...

[MOZ]

If I have a .py file from MOZ for EasyAVR,
does anyone know what im supposed to do with it to make it show up in the default layers when starting up the program? 

I have the file, but putting it in different folders isn't making it show up in the program.

Sorry, I missed your PM.

1. What OS are you using?
2. Where did you download EasyAVR from?

[Moistgun]

No worries!

I've been trying windows and I have Linux on my pc, but I don't know the os well at all.

I downloaded from your link you posted a few responses ago

[odd]

Put that file moz gave you in your home dir on your win box like he wrote, not the install dir.

Example,  where to drop on home dir on

Linux: ~/. EasyAVR
Windows: ‰username‰/EasyAVR

[MOZ]

1. Download latest version from here: https://deskthority.net/wiki/Easy_AVR_USB_Keyboard_Firmware
2. Extract anywhere.
3. Run Easy AVR once.
4. Exit.
5. Copy the file I uploaded to C:\users\<username>\.EasyAVR folder (Or something along those lines).
6. Run Easy AVR again, Go to File -> New Default layout and choose "Moistgun's 60"
7. Configure
8. Build Firmware
9. Load onto Teensy.

[Moistgun]

The tool automatically creates ~/.EasyAVR/ (probably /home/username/.EasyAVR on Linux and c:\users\username\.EasyAVR on Windows)

I know what you are talking about now, and will test it tonight.

[Moistgun]

1. Download latest version from here: https://deskthority.net/wiki/Easy_AVR_USB_Keyboard_Firmware
2. Extract anywhere.
3. Run Easy AVR once.
4. Exit.
5. Copy the file I uploaded to C:\users\<username>\.EasyAVR folder (Or something along those lines).
6. Run Easy AVR again, Go to File -> New Default layout and choose "Moistgun's 60"
7. Configure
8. Build Firmware
9. Load onto Teensy.

Sooo, I followed your steps, which are very clear, Im just dumb
programmed and rebooted.
the only key that does anything is e
every other key does nothing except the e key...

lmao

[suicidal_orange]

That sounds like you have one diode the wrong way round, you can guess which one )

[Moistgun]

That sounds like you have one diode the wrong way round, you can guess which one )

but theyre all facing the same direction.  Black strip down. 

[0100010]

Can you post some pics of the matrix wiring?

[Moistgun]

Can you post some pics of the matrix wiring?

sorry about the quality.

all diodes are facing the same way, black stripe down.

Did I just do a mess of a job wiring it? or do you think its the AVR?

[0100010]

Do you get solid continuity for every row and column testing with a multimeter?

[Moistgun]

Do you get solid continuity for every row and column testing with a multimeter?

 

I don't have a multi meter. So I haven't tested it.

[0100010]

http://www.homedepot.com/p/Commercial-Electric-Analogue-Multimeter-M1015B/202353292

[Moistgun]

http://www.homedepot.com/p/Commercial-Electric-Analogue-Multimeter-M1015B/202353292

I drive by a hdx and microcenter daily so I will grab one.
How do I test with it? just do one switch at a time by touching both pins or do I need to test the rows and columns some way

[user 18]

just do one switch at a time by touching both pins

This definitely won't get you anywhere, the switches are open and you certainly won't get continuity.

or do I need to test the rows and columns some way

I'd start by putting each probe on opposite ends of each row and column. If one doesn't give you continuity, there's an issue somewhere, and you can narrow it down by testing intermediate locations.

[0100010]

What user 18 said.  Put the meter on the highest ohm setting and confirm continuity end to end for row and column.  I would then confirm continuity from each row / column to the teensy (using the solder point for each of your row / column wires).  Lastly I would confirm no continuity from every column to every row (provided none of the switches are depressed).

Do all of these steps without the teensy powered.  Hopefully you will find an unexpected shorted or open circuit, which after correcting will lead to a working matrix.

[Moistgun]

What user 18 said.  Put the meter on the highest ohm setting and confirm continuity end to end for row and column.  I would then confirm continuity from each row / column to the teensy (using the solder point for each of your row / column wires).  Lastly I would confirm no continuity from every column to every row (provided none of the switches are depressed).

Do all of these steps without the teensy powered.  Hopefully you will find an unexpected shorted or open circuit, which after correcting will lead to a working matrix.

Super!
Ill grab one after work tonight and give it a shot!

Thanks for all the descriptive information!

[Moistgun]

Just to point out, these are alps switches.

Knowing that the pins are different from an mx switch, does my wiring still look like the diodes are going the right way?

would you please take a second to look at the photos again?

[suicidal_orange]

A switch is a switch - when you press it the pins connect, current flows through them and the controller notices

As the diode for e is the right way round it could be defective - you should only see continuity through it one way, if it goes both ways it's broken.

edit:  Realise I should explain myself here.

Either you messed up 13 out of 14 columns and 4 out of 5 rows, looking at your wiring it looks good so I don't believe for one moment you messed up that badly!

The other option is you have one dodgy diode and the firmware doesn't match the diode orientation, so it doesn't work (except the broken bit)


The first thing I would do is change it to this in the config - this reverses the expected orientation of the diodes and may well make it work, but I suspect the e key will cause ghosting issues...

Code: [Select]

strobe_cols = False
It's a much quicker fix than checking the entire matrix, you have nothing to lose

[0100010]

That is true - to 'reverse' the "direction" of the matrix in software first.  Would be much faster testing wise that ohming out the matrix.

[Moistgun]

A switch is a switch - when you press it the pins connect, current flows through them and the controller notices

As the diode for e is the right way round it could be defective - you should only see continuity through it one way, if it goes both ways it's broken.

edit:  Realise I should explain myself here.

Either you messed up 13 out of 14 columns and 4 out of 5 rows, looking at your wiring it looks good so I don't believe for one moment you messed up that badly!

The other option is you have one dodgy diode and the firmware doesn't match the diode orientation, so it doesn't work (except the broken bit)


The first thing I would do is change it to this in the config - this reverses the expected orientation of the diodes and may well make it work, but I suspect the e key will cause ghosting issues...

Code: [Select]

strobe_cols = False
It's a much quicker fix than checking the entire matrix, you have nothing to lose

Very cool! Ill give it a shot tonight and let you know what happens.

Thanks for the explanation. I was actually looking through the file and noticed the section about diodes going col to rows or rows to cols, and got confused 

[suicidal_orange]

Thanks for the explanation. I was actually looking through the file and noticed the section about diodes going col to rows or rows to cols, and got confused 

To be honest I don't get it either - the words seem to match your board as it is, but if that was the case it would work better.

If changing that setting makes it work I think the default should be changed as that's how pretty much everyone builds them, I guess everyone either follows that tutorial or copies a board on here made by someone who did so it's become a "standard" in the world of "customs" )