You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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:
Originally posted by @customsolutions in grblHAL/core#203 (comment)
The text was updated successfully, but these errors were encountered: