ergodox, help with teensy

[gcb]

just finished my right hand (this time with the diodes on the right side of the board and am trying to flash the teensy... i knew i should have familiarized with it before any soldering... sigh.

what happen is as follow:

when i first plugged it, the LED was flashing, which i assume is the blinky code that comes from the factory.

i opened the teensy-aplication, dragged the epp file (no way to open it via menus. annoying) pressed the reset button.... it seemed to work. linux dmesg showed a new HID device attached. but it was faster than instantaneous. the assembly instructions says it might take a second or so. i uploaded the hex. reset. and nothing. unplug, plug. see the HID device. nothing. no typing.

So i tried to upload the blink code... can't find it anywhere, so i gave up and install the arduino IDE, install the teensy part on top, just so i can click examples>blinky... it says it upload fine to the device. but nothing blinks.

where do i go from there? I tried the 'grown up' version https://www.pjrc.com/teensy/loader_cli.html but i failed miserably on understanding how to send an epp file with it. or even what the heck an epp file is.

[gcb]

i'm screwing up on the usage i think...

finally found the pre-compiled blink HEX and uploaded with the command line, and it works fine.

Code: [Select]

$ ./teensy_loader_cli -mmcu=atmega32u4 -v -w ../blink_slow_Teensy2.hex 
Teensy Loader, Command Line, Version 2.0
Read "../blink_slow_Teensy2.hex": 2274 bytes, 7.0% usage
Waiting for Teensy device...
 (hint: press the reset button)
Found HalfKay Bootloader
Read "../blink_slow_Teensy2.hex": 2274 bytes, 7.0% usage
Programming..................
Booting

now it is slowly blinking at me. mocking my ineptitude.

[gcb]

hum. uploading the HEX file alone seems to 'almost work'


but the left buttons with LED do nothing. when it power up, it lights all three leds, then lights them all brighter, and then turn the bottom two off. the top one remains.

is this normal?

besides the led and left-most buttons... there are a few screw ups. such as space=0. up arrow=nothing. down arrow=. (using the assembly instructions qwerty hex)

it is probably yet another screw up on the diodes...

damn diode 4:6 is inverted... fixing that joker...

[gcb]

that diode fix seems to have did the trick for some things.

but the top led is still always on.

pressing NUM_LOCK on another keyboard correctly makes the num lock keys work as numbers.

but pressing the top left key which on my map is supposed to be NUM_LOCK, will actually toggle between unmodified key (e.g. jkl) and keypad modified (kp_left, kp_begin, kp_right)

any ideas? is this related to the EPP file that i'm not sure i uploaded correctly?


update: another odity... it never ends. after a while, it gets into random mode... right hand key mostly types in symbols such as ()><.,

i'm using what i suppose is this https://github.com/benblazak/ergodox-firmware/blob/master/src/keyboard/ergodox/layout/qwerty-kinesis-mod.c
but from a zip file in the instructions. does not seem to have any lock-in 3rd layer for symbols.

[gcb]

for some reason, i did the exact same steps on my work win7 box and now it works perfectly... sigh.

So it was indeed something related to uploading the epp and hex file somehow. or my bad solder joints settled down overnight

dammit... who though having all those cables on the top would be smart? it is hell to use with a laptop. the conectors should have been in the middle. ..doesn't help that masdrop send in audio cables with a 1ft long plug!