grblhal / stm32f7xx Goto Github PK

Have you not considered the H750VBT6 chip? It is 480Mhz, and it is cheap enough

Hi terjeio,

Can I please ask if the firmware will use the HSE or HSI as the clock source.

I assume that because this is a Nucleo board that it will use the HSI?

Regards
George

Hello, hello terjeio, I am from China, I am a machining center operator, I like cnc very much, I started DIY cnc 3 years ago, it is very interesting,

Compared with CNC, I think CNC system is more interesting, so I started to learn to contact grbl, because it is open source

Later, I started to learn how to make circuit boards. I made circuit boards for ESP32 GRBL and STM32F4 GRBL_HAL and sold them. Although it did not bring much income, I found it very interesting.

I have made an embedded linux controller with a touch screen based on STM32 F4 GRBL_HAL and Candle, although I have not sold a few, but I have considered future development,

No one knows grbl better than you. I want to adopt a cooperative form. I don’t know if you can add some functions to grbl_hal. Is it difficult to implement? These functions do not need to be open source. I don’t need these functions yet. Now I’m just asking

Function 1: 5-axis RTCP is something that many Chinese buyers consult. This function is of great commercial value. I don’t know how difficult it is to realize? I only know that RTCP is a matter of kinematics.

There are other functions of industrial controllers, such as radius compensation, S acceleration and deceleration, G84 servo spindle tapping,

The above function is just to ask how difficult it is to implement terjeio? It is not particularly necessary, and the current version of grbl_hal is enough

I add keypad plugin via submodule:

git submodule add https://github.com/grblHAL/Plugin_keypad keypad

and add to code to Src/driver.c

#if KEYPAD_ENABLE
#include "keypad/keypad.h"
#endif

define in Inc/my_machine.h for UART keypad

#define KEYPAD_ENABLE        2 

and get error: undefined reference to `keypad_init'

01:59:20 **** Incremental Build of configuration Release for project grblHAL Driver STM32F756 ****
make -j3 all 
arm-none-eabi-gcc -o "grblHAL Driver STM32F756.elf" @"objects.list"   -mcpu=cortex-m7 -T"/Users/r3/STM32CubeIDE/workspace_1.12.0/grblHAL/STM32F7xx/STM32F756ZGTX_FLASH.ld" --specs=nosys.specs -Wl,-Map="grblHAL Driver STM32F756.map" -Wl,--gc-sections -static -u _printf_float --specs=nano.specs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mthumb -u _printf_float -u _scanf_float -Wl,--start-group -lc -lm -Wl,--end-group
/Applications/STM32CubeIDE.app/Contents/Eclipse/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.10.3-2021.10.macos64_1.0.200.202301161003/tools/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld: ./Src/driver.o: in function `driver_init':
driver.c:(.text.driver_init+0x248): undefined reference to `keypad_init'
collect2: error: ld returned 1 exit status
make: *** [makefile:95: grblHAL Driver STM32F756.elf] Error 1
"make -j3 all" terminated with exit code 2. Build might be incomplete.

01:59:20 Build Failed. 3 errors, 0 warnings. (took 649ms)

What did I do wrong?
use board: Nucleo-144 (STM32F756ZG MCU)

Thanks for your great work.

According to your project STM32F756ZGT6 made for pure motor control 8-axis control board, support USB, serial port, Ethernet, it feels very interesting

Hi Terje Io,

I hope you are well.

I have attempted to flash a STM32F746 Nucleo board with the compiled .elf file but could not get it to upload.

I did however manage to get a previous compiled file (for the STM32F411) to succesfully upload to the Nucleo board (even though it is not the correct file).

I created a my_machine_map.h and ensured the BOARD_MY_MACHINE is not commented out but I suspect that it is not compiling properly or selecting my_machine_map.h file.

Regards and have a great day
George

Hi Terjeio,

I am looking at building a prototype based on the STM32F756 and have been trying to work out which pins to assign to the SD Card (SPI).

I notice that within the spi.c file and compared to the MCU datasheet that the MOSI and MISO pin assignments seem to be reversed.

Would you kindly advise if this is correct.

Regards and have a great day
George