-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manually Building SuperLongBoard STM32F412 #193
Comments
Here is the platformio.ini I use to build the latest version with VSCode/PlatformIO: |
It is found here.
Do you have the latest grblHAL version? |
Do a recursive pull to get the latest submodules instead, recently a new one was added for the two you disabled. |
I already did a recursive pull but I'm still getting errors with those two flags turned ON. For now, I've kept them OFF. I'm also just adding the custom Sienci plugins they included, such as I loaded the firmware for the SLB. The issue is that the motors are not getting power after I performed a firmware reset. Restoring the SienciHal firmware brings the stepper motors back online. Before resetting, the motors had a slightly high-pitched sound when moving. I'm not sure if this is caused by the settings for the TMC2660. Setting number don't much, they are off by 1 whey I compare with SienciHal. |
Boot entry is part of the base driver so not needed, basic RGB support is also, with a core defined API. I have not looked into the probing plugin yet. There should be a plugins folder with the eventout and rgb plugins: If not download and add it manually - making it generally available is still work in progress.
What is your $4 setting? And M122 output?
Some SienciHal setting numbers were added without requesting them from me and they were already assigned for other purposes. So those had to change. Reloading SienciHal settings into grblHAL is thus a bad idea. |
Pulling the There is another flag
I agree, that's why I'm trying to switch. :D |
Here's my test result.
What works so far:
I'm using gSender since I don't have any other grblHal sender to try on macos. Attaching diagnostic file from gSender which has all the firmware paramenters. |
This has now been fixed. The rest I am not so sure about, can you connect with a terminal and try some commands from that? |
Great! I will test it tomorrow. Will provide feedback. IMHO, Sienci should send you one for the great work you been doing. 👍 |
I have one at home, but I am away for 3 more weeks... |
Try the latest. I initially still got problem with the homing so decided to do RST and start from scratch the it works. So far everything is working except for the tool set routine with my RapidChangeATC. When I touches the tool setter, it stop and freeze the board. Macro used for tool change for reference: https://github.com/greilick-industries/rcatc-scripts-grblhal/blob/main/macros/TC.macro This one is working with sienciHal but has some other minor issue. |
If I run the the tool setter macro (g65p231) directly on a STM32F7xx dev board it completes correctly - so this might be an issue with the SLB. If you try to probe the toolsetter manually does it still crash? |
FYI I have commited some fixes to expression handling that may help if it is a hang, not a crash. |
Since the SuperLongBoard is not yet available in Web Builder, I'm trying to build firmware for the LongBoard32, but I can't seem to get it working, and I keep encountering errors.
So far, I have created an entry in the platformio.ini file:
I also added an entry in driver.json:
I copied the genericSTM32F412VG.json file to the root folder. This file can be found here: (https://github.com/Sienci-Labs/sienciHAL/blob/SLB_Bringup_Dev/genericSTM32F412VG.json).
Then, I executed the following command:
I started with fewer plugins to have a successful build, but I keep getting errors after fixing one issue. Before going down the rabbit hole of trying to fix all the errors, I figured I'd ask if anyone has already had a successful build.
The reason I am building this is that the core of the Sienci grblHAL firmware is not up to date.
The text was updated successfully, but these errors were encountered: