Mainly prep for Proton C and the inevitable wave of conversions.
drashna
All 11 comments
Are we talking about the mcuconf halconf etc?
yiancar
on 12 Oct 2018
Yes.
Specifically, the bootloader_defs.h, chconf.h, halconf.h, mcuconf.h files, and the boards folder which needs to be added to the keyboard's folder, on top of the normal stuff.
I think @jackhumbert mentioned handling it like the drivers, so that if the specific controller is used, that it includes the correct folder (with all of the matching files) into the "include" path.
This way, when we have people adding ARM versions of their boards to the repo, they don't have to worry about all of the extra files, where to find them, and that they're correct. All they have to do is set the MCU info in the rules.mk, and that's it.
drashna
on 12 Oct 2018
Well halconf.h is application specific, it tells the hal drivers which parts to enable. chconf.h is os application specific, selecting frequency theads etc. mcuconfig.h again are application specific for the peripherals.
bootloader_defs.h is ok to move as those its actually only mcu specific.Boards can also be moved providing that all the pins are exposed.
yiancar
on 12 Oct 2018
SO any ideas on this or are people happy with the way it is now?
yiancar
on 22 Oct 2018
well, "internal talk" is kind of leading towards an easier way to convert the pro micro boards over.
The other option is maybe writing a guide on how to convert everything over.
drashna
on 23 Oct 2018
I wouldnt mind writing a guide on how the files work. However there is a huge list of options. I can cover most of them. Some of the options go very deep regarding priorities and IRQs etc.
In general I think a guide can explain how to port over a keyboard to ARM with the basic options. SPI/I2C are pretty straight forward.
yiancar
on 23 Oct 2018
That would be nice!
Though a guide on converting Pro Micro based boards to the Proton C would be best, right now. Since I foresee that happening a lot.
drashna
on 23 Oct 2018
Well I dont have a proton C but i imagine if someone setups a script to copy all the mcu/os files to a new directory, that would be it! matrix.c now works for arm as well so just redefining the pins should do
yiancar
on 23 Oct 2018
Yeah, I think that was talked about as well.
The real question is how to handle Pro Micro vs Proton C for boards.
drashna
on 23 Oct 2018
well if you select an avr target it will build for pro micro if you select stm32 it will build for proton c
you just need the correct pins
yiancar
on 23 Oct 2018
Jack added this.
drashna
on 25 Feb 2019
Related issues
ghost
路
3Comments
alaibe
路
4Comments
jmagee
路
3Comments
vokeio
路
3Comments
helluvamatt
路
4Comments
Most helpful comment
Well
halconf.his application specific, it tells the hal drivers which parts to enable.chconf.his os application specific, selecting frequency theads etc.mcuconfig.hagain are application specific for the peripherals.bootloader_defs.his ok to move as those its actually only mcu specific.Boardscan also be moved providing that all the pins are exposed.