-
Notifications
You must be signed in to change notification settings - Fork 84
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
Commit tool table NVS fix. #68
Conversation
How did it break the build? Depending on the number of tools defined this change will potentially overwrite data in the NVS_ADDR_PARAMETERS block (used for offsets). It will also break the assert in grbllib.c: Line 94 in 384fda6
I have been thinking of adding the tool table to the end of the first 1K block in order to get more headroom. This can be done increasing the GRBL_NVS_SIZE define. |
Executable went from 500k to 70k and would not run. I don’t have debugging on teensy so didn’t see where it was failing to load. I probably don’t know enough about the memory map to understand the best place to put things, still learning. |
What did you set N_TOOLS to? |
Left it at 8 for now. |
Without tool table:
This is with ethernet and a few other plugins enabled. And with the 1.54 version of the Teensy libraries - earlier versions are buggy. |
I've added the tool table to NVS debug output - from the
No room for expansion in the global area. This means I have to move the tool table above 1K... With your change:
It goes clear of the parameters area but overlaps the startup area. Debug output has to be enabled in config.h to enable |
18c2004
to
384fda6
Compare
I've closed this pull request as it obviously isn't the correct solution, but I'm going to continue looking at this because I still cannot get the tool table to compile into my build, nor is it really feasible to only have it working with 3 axes. |
Can you try with this patch? It moves the tool table to 1024. [MSG:NVS Area: addr size] |
When I went to compile with the tool table enabled, initially it seemed to break the build. The changes below seemed to fix things for me and allow me to test the functionality.
This was on the teensy4.1 driver with my GRBLHAL2000 board, but I think this would apply to all drivers.