--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sun, Jul 24, 2016 at 8:20 AM, Albert ARIBAUD albert.aribaud@free.fr wrote:
Hi Luke and all,
hii albert,
I could have solder-bridged PA2 and PA3 (and un-bridged PA5 while at it), but they are used for ST-Link/V2-1 and LD2. I prefer to keep the NUCLEO untouched so that others can use theirs out of the box, so I reworked my existing NUCLEO-specific git branch to replace PA2, PA3 and PA5 with PA13, PA14 and PA15 in the keyboard matrix code. That's not a perfect solution as the EC hardware uses PA13 as LCD_RESET and PA15 as SPI1_NSS, but it Works For Now(tm).
#ifdef STM32F072_NUCLEO
But I still want to write an AZERTY EC firmware, because it will allow "native" use of the keyboard with *any* software on the EOMA-68, not just those which can translate QWERTY to AZERTY; bootloaders, for instance, typically don't do keyboard table translation.
yeahyeah exactly
But an AZERTY EC firmware will require more than just rewriting the key code matrix: for instance, there is no "KEY_&" code, so that one will have to be emulated with a "modifier SHIFT + KEY_1" combination, and so on for the rest. Nothing unfeasible, mind you, or terribly difficult either. It'll just eat up a bit more resources than I initially thought it would; my ballpark estimate is about 256 added bytes for code plus 128 added bytes for read-only data in FLASH, and a few added bytes in RAM.
hmm is KEY_& specific to azerty?
BTW: it might be a good idea to provide written instructions for people to reconfigure their NUCLEO board for EOMA-68 EC hardware compatibility by filling solder bridges SB62 and SB63, and clearing SB13, SB14 and SB21. Is there a separate EOMA-68 doc repo somewhere where I could put this, or can/should I create eoma68/laptop_15in_pcb2/doc/ under the eoma-firmware repo and put that info in there, say as a MarkDown format README-NUCLEO.md file?
yeah drop it into the wiki, it's editable. suggest doing a #ifdef STM32F072_NUCLEO (make -D ST.... option, not in the Makefile or source code)
Also: video of the whole thing in the works! :)
_great_