![Smile :)](./images/smilies/icon_e_smile.gif)
typos due to my touch screen are possible[size]
if the board will have a button, then another simple test would be: push button - led blinks - push button - led offmatt3o wrote: ↑I talked to the lab that will probably produce the board, we have to also provide a very simple test program that will be used in QC to verify that the board is working. The easiest would probably be a blinking LED.
Push button is hard-wired to reset line.derzemel wrote: ↑if the board will have a button, then another simple test would be: push button - led blinks - push button - led offmatt3o wrote: ↑I talked to the lab that will probably produce the board, we have to also provide a very simple test program that will be used in QC to verify that the board is working. The easiest would probably be a blinking LED.
I don't know about that yetmohitgarg wrote: ↑Will they be flashing over USB or use a dedicated programmer, USB has the advantage that USB connection will also be verified.
oh wow this is funky!flabbergast wrote: ↑Hi folks, here's another oneFirst let me say that Mohit's board is probably better, because atmega32u4
I like it.
But for the more adventurous, here's an alternative. (I was mostly curious if I can route that thing; turns out yes but it ain't pretty.) Picture here. No silkscreen because I didn't clean that up yet.
Features:
- Kinetis MKL27ZxxxVFT4 (an ARM Cortex M0+ chip, in QFN48 package, 128 or 256kB flash, 32kB RAM)
this looks great. So if I get it right the size of the board is 30.6x22mm including the USB peninsula?mohitgarg wrote: ↑ v0.2
The pads with the silkscreen ring are PWM pins. Once the design is finalised, I'll squeez in th pin names on silkscreen.
Still waiting to see if matteo is interested and the elf logo
Dimensions are 30.6x18mm, with the 8x4mm microusb tab.
I'm not sure, if I get it right with your version we could use both haata and hasu's firmwares. That would be definitely a good point. Also expandibility and future-proofing are other two important factors. The teensy 2 I guess will be discontinued sooner or later.flabbergast wrote: ↑So it kind of depends on what do we want to get in the end. A proven and definitely usable micro in a (much) better package, or try to push out a new thing (that will hit some snags along the way, quite possibly leaving people somewhat disappointed)?
Definitely a possibility, along with 1.27mm headers. They aren't that difficult to solder.matt3o wrote: ↑hold on. idea.
Instead on those big holes for the i/o why don't we use a micro-header similar to the one in the HHKB? Like this http://i.imgur.com/1Y5fpl.jpg (the small one on top), but I'm sure there are others even smaller
Yes, realized what you were asking after Mohitgarg replied. Sorry!matt3o wrote: ↑@derzemel, I mean not for the USB... but for all inputs!(we still need a USB of course). Instead of through hole pads we could use a small header and provide with the male (or female depending what's on the PCB) connector attached to like 10cm of cables.
Yes, the size is 30.6x22 including the USB peninsula.matt3o wrote: ↑ this looks great. So if I get it right the size of the board is 30.6x22mm including the USB peninsula?
I can't make them both so we have to pick one design (of course we can make one later). I like flabbergast specs and mohitgarg design. Can we have them merged together?
I'm afraid 22mm is a pinch too much. Ideally we shouldn't exceed 19mm (height of the keycap) but we can probably go up to 20mm. Better to add few mm horizontally than vertically.mohitgarg wrote: ↑Yes, the size is 30.6x22 including the USB peninsula.
Agreed on that. My only concern about ARM is compatibility with existing firmware but flabberghast says we are good with that, so what would be the benefit of atmega vs arm? Only pricing?mohitgarg wrote: ↑I think before proceeding forward, we should decide on the MCU
it's just an idea. You designers have the last word. Do whatever you want to make it happenmohitgarg wrote: ↑About the board to wire connector
Chirsandreae's firmware has 31 kB when compiled for ATXmega. I think it still fits on ATmega but requires 1 kB or smaller boot loader. And it will cross the 32 kB limit almost for sure once I add the features I want. It runs only on ATmega and ATXmega now. Chris indicated an intention to support ARM but I do not have any clue when it happens and if ever. Of course one can shave about 10 kB from the firmware size if the interpreter is disabled. The interpreter allows running of c-like programs which can generate precisely timed keyboard/mouse events.flabbergast wrote: ↑And I'm not sure we're hitting the flash/RAM limits yet. We're close (with TMK with all the features on), but not there yet.