EMC2 running on Raspberry Pi?

Hi,

You can also use KL25Z-FRDM board.
image missing http://img854.imageshack.us/img854/9866/ppim.jpg

Cheers!

Thanks for the tips and for the warning,

  I've had experiences where the performance of Raspberry was not enough, then I migrated to Cubieboard and works well. Knowing their recommendations I will be more cautious and more confident in porting to Cubieboard.

   KL25Z-FRDM is interesting, especially because it simplifies Jr Board PICnc for driver only. Now, ever wondered about using drivers with SPI interface like A3981, L6470?

  I am running LinuxCNC from an ssh-X. I'm wondering how to configure the Hal to use SPI. What would be correct to raise linuxCNC with RPI + Jr Board PICnc por exemplo?

Best Regards

ADBensi wrote: Thanks for the tips and for the warning,

  I've had experiences where the performance of Raspberry was not enough, then I migrated to Cubieboard and works well. Knowing their recommendations I will be more cautious and more confident in porting to Cubieboard.

   KL25Z-FRDM is interesting, especially because it simplifies Jr Board PICnc for driver only. Now, ever wondered about using drivers with SPI interface like A3981, L6470?

  I am running LinuxCNC from an ssh-X. I'm wondering how to configure the Hal to use SPI. What would be correct to raise linuxCNC with RPI + Jr Board PICnc por exemplo?

Best Regards

The A3981 would need a dedicated SPI channel per axis; implementing a driver would be a bit complicated.

If you want to port to Cubieboard then you'll need to modify src/hal/drivers/hal_spi.c (from unified-build-candidate-3). I'll be updating this driver to handle both PIC32 and KL25Z-FRDM boards.

Here's my printer controlled by RPi using the FRDM-KL25Z board:



Cheers!

Hello Kinsa,

May be a bit complicated, but it´is fast too and more peaceful to GPIO Control
I think MOSI (pin 10), MISO (9), SCLK (12) and more n GPIOs to SS (enable/disable) slave drivers.

Can you help me with the first steps: To change the control mechanism the LinuxCNC just compile - with-platform = X where X is the new HAL file? I am in doubt about the LinuxCNC API and the keys of configuration.

Ps: Great job with 3D printer

ADBensi wrote: Hello Kinsa,

May be a bit complicated, but it´is fast too and more peaceful to GPIO Control
I think MOSI (pin 10), MISO (9), SCLK (12) and more n GPIOs to SS (enable/disable) slave drivers.

Can you help me with the first steps: To change the control mechanism the LinuxCNC just compile - with-platform = X where X is the new HAL file? I am in doubt about the LinuxCNC API and the keys of configuration.

Ps: Great job with 3D printer

Thanks!

I would prefer to minimize the usage of GPIO's so that the board could be easily used for other ARM boards.

For compiling LinuxCNC, the --with-platform switch only adds the built-in HAL drivers for that board. I've used the instructions here to build the latest LCNC.

It is easy to compile out-of-tree drivers using the comp command. Here's the example SPI driver for RPi: code.google.com/p/picnc/source/browse/#g...FHAL%2Ftest%20driver

I've moved over to plain C for the HAL driver as I have more control over the HAL pin naming.

Cheers!