Just by curiosity, @Arthur_Wolf , do you know if anyone eventually ported smoothieware on this 4-year old ARM32 R2C2 board? The MCU is an LPC1758, which is quite similar to the '68 (same speed and memory specs as the 1759). Only it has 20 pins less – so let’s ignore LCDs and extra GPIOs… Now, reading
http://smoothieware.org/forum/t-1094315/r2c2-port it does not seem it was trivial… if ever it was done!
(not to say I would do it, since I also have a smoothieboard, eh – but it would have been cool to put the R2C2 to use with a modern firmware).
Hi @Jeremie_Francois , Just to try to understand better: when do you say “R2C2 of mine” it’s because you designed it or it’s just in your possession?
Huh no, I am certainly not experienced enough to do such a big board 
It is just b/c I bought one! And it is a pity I did not put it to use so far… I’ve edited the post
… Thanks for the clarification. It happens that I know the person (and the portuguese company that did the board). I just wasn’t sure if you were somehow involved. On another topic, I also filled your questionnaire on a possible new 3D printer. Please read it, and maybe we should talk… 
@Jeremie_Francois I don’t remember that anybody ever got it to work, though I don’t remember any major problem, except the weird choice of pins the R2C2 guys made.
+Peter van der Walt yep I read 32BIT NPC LPC1768 ARM. But the R2C2 is a 1758. Now I understand this is not really the problem, unless some sort of grouped io via port management is done deep in smoothieware.
Just for reference, main specs here
http://reprap.org/wiki/R2C2_RepRap_Electronics and schematics here https://github.com/bitboxelectronics/R2C2_Hardware/blob/master/v1.2/R2C2_v1.2_Schematics.pdf
@Michael_Memeteau thanks! This board deserved more visibility, but I think what killed it is that it was “too early” on the market, what a pity! BTW, yes, I kept an eye on the quadrap community, even though our goal with the printer is not reprap. People seem to agree, as 75% of answer is “highest quality whatever the price”.
@Jeremie_Francois I agree with “too early” on the market, but that’s what innovators do… If you need any additional support from them, I can probably help. Check also the approach tinyG has on acceleration and jerk, that can be decisive on getting proper quality at decent speed on 3DP.
Regarding the printer you’re working with, I understood that you’re going for a commercial product, not doubt about this… It does not prevent you to incorporate some innovation done by the reprap community if the license agreement match. Some of the technical solution found there are worth looking at them.
Hi +Jeremie Francois! It’s good to meet owners of R2C2 board
We are making some tests on porting Smoothieware to R2C2.
What is your application for R2C2?
@Francisco_Mendes hey great news! My R2C2 stands idle with some of my other boards (SM1, Replicape2, AZSMZ… I did not buy the Azteeg though - yet!).
I bought them mostly out of curiosity and to test them for a “serious” coreXY I am building with a sponsor (we are going with the SM if production is not a bottleneck).
In fact I have no special use for the R2C2 so far, mostly because it is commercially dead. Personnaly I would definitely beta test your port and use it, say, on my CNC in place of the highly usual annoying parallel port setup.
BTW I see you are working at @BEEVERYCREATIVE ? I talked a bit with Aurora at the last Paris 3D print show (as a moderator, I had not enough free time). Looked like very nice people & company to work at! Hope you’re all doing well
@Jorge_Pinto and I joined in 2010 to develop electronic products. The first was R2C2 that came to the market in 2011 and the company was named bitBOX back then.
In 2012 we decided to focus only in 3DP products and the company grow and changed name for BEEVERYCREATIVE.
I’m going to add a reminder to contact you if we go farther and need beta testers.
@Marcos_Gomes
Hello, at BEEVERYCREATIVE github you will find a port from both bootloader and firmware. They are both functional but it is not expected to have any kind of support. You may also find some features missing.
@Marcos_Gomes great & thanks! I understand and I won’t annoy you with support, I know how to code