Category: Driver Boards
Are you going with ColorCNC by romanetz or LiteX-CNC.
Either way the basic thing is, your create a config for the firmware using a json file, follow the instructions to build the firmware, upoad the bit file to the Colorlight board, then create a Linuxcnc config & ini files.
Litex-CNC (it's been awhile since I decided not to use this as I felt it was easier to go another route.)
So, no one does not upload a config to the board, a new bit file has to be built.
The way I tackle a new project.
Read the whole thread, take notes, follow the link on the github page to the docs, read the docs, have a browse around the github page. Take a bit of time to get the feel.
Setup a build environment, and attempt to build a config. Then I'd modify one of the supplied configs to get a hang of it.
Eventually I'll upload a bit file to the board, probably from one of the supplied json files. Reread the read or refer to any note regarding creating a hal file.
May take a couple of nights or weeks depending on a lot of things. You may find you'll have to read & reread & reread some more. I'm sure there's some examples scattered about in the thread.
Research is the key point. All the info is there.
If you don't fully understand how it works, you may have to find someone to do the hard work for you. Or have a look of one of the more active projects, maybe Linuxcnc-RIO, which uses a larger range of FPGA boards (even the mesa clone I designed works with Linuxcnc-RIO) and doesn't rely on the ever changing availability or certain Colorlight boards being available and actually being shipped to you.
