Skip to content
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

g2core via Motate on an LPC CPU (Smoothieboard) #8

Open
xpix opened this issue Mar 25, 2017 · 2 comments
Open

g2core via Motate on an LPC CPU (Smoothieboard) #8

xpix opened this issue Mar 25, 2017 · 2 comments

Comments

@xpix
Copy link

xpix commented Mar 25, 2017

Hello,

if it possible to build motate for an LPC1769?
It's the cpu of the smoothieboard and it would be great to use this as CNC Controller.

I found this here for GRBL:
https://github.com/gnea/grbl-LPC

@giseburt
Copy link
Member

Absolutely! Anyone willing to give it a go we'll support the effort as much as we can. Pull requests are always welcome!

As for the technical side, it's completely practical. It will just take some time and effort.

-Rob

@RadicalZephyr
Copy link

Hi there, I'm really interested in a port to LPC as well (so I can run g2core!), and would love some pointers on how to get started. I'm fairly new to the world of embedded development so this might be an overly ambitious project for me, but I'm very interested in learning.

In terms of the layering of Motate, my understanding is that the architecture level is handled because the LPC1769 is an ARM Cortex M3, but that the platform, processor and board would support would all need to be created for this.

So I have a few questions on how to get started.

From my understanding, all of these files live inside the MotateProject/motate directory, with the processor layer being folders in that directory, and then arch, platform and board related things under the subdirectories of the corresponding names. Is that correct?

Second, which "end" should I start work from? It seems most natural to start at the lowest level that needs to be implemented (platform) and work my way up, but I think the knowledge contained in the board level is a little more obvious to me.

Third, would it be okay to open a WIP/tracking PR that we can use to focus discussion and feedback with around code changes needed for this?

Finally, do you have any pointers on specific learning resources for this kind of work? 😄

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants