MiniGerbil 2 board map

[terjeio]

I wanted to offer to upgrade chip for current users, also i have a board in the works that will be pin compatible. Here is a link https://github.com/customsolutions/STM32F1xx/blob/master/Inc/my_cpu_map.h This is my github. Id be glad to assisit in any way I can.

On Sat, Nov 18, 2023, 1:59 AM Terje Io @.***> wrote:

Do you have a working board map for the MG2, and possibly MG3? Or working links to this information - I can't find any. And which chip variant do they use? The 64K flash ones? If the 64K variant then I see no point in adding board map(s) as I consider it unlikely that end users will replace the MCU.

[image: image] https://user-images.githubusercontent.com/20260062/283986061-40b6949c-503f-4327-9bd3-1f0134c022d4.png

Any assist is appreciated.

Open a new issue in the STM32F1xx driver repo https://github.com/grblHAL/STM32F1xx/issues for that.

P.S i have in the works custom board thatll use same pinout.

With which MCU? You should not design a board for the 128K flash versions (medium density) as this has a stripped down version of grblHAL that is likely to become unsupported soon. The high density versions are ok, but you will get better performance out of STM32F3xx or STM32F4xx since these are faster MCUs with a FPU.

— Reply to this email directly, view it on GitHub https://github.com/grblHAL/core/discussions/203#discussioncomment-7605318, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF5JEYD4JI5PAOEQRZZBGJLYFBTFRAVCNFSM6AAAAAARHDFMYGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMBVGMYTQ . You are receiving this because you were mentioned.Message ID: @.***>

Originally posted by @customsolutions in https://github.com/grblHAL/core/discussions/203#discussioncomment-7607879

[terjeio]

BOARD_NAME should be recognizable as a product name, e.g. "MiniGerbil 2". BOARD_URL should be a link to the product page, preferably where the design files can be found. Not the board map file itself. In the Web Builder the Board map button uses a generated link, from info about the board in driver.json.

A PR for a new board map should:

• Add a #define symbol for it in my_machine.h.
• Add a test for the symbol and include the board map in driver.h when selected.
• Have recognizable names for the #define symbol and the board map file.
• If to be compilable from the web builder add an entry for the board in driver.json.