Advanced Search

Oh ok, some users have reported issues with other images with RPi imager.

works now! thanks yeah the RPi imager can be used with a custom image and works like balena then.

cnc
cnc

These images aren't based on the raspios, they are based on Debian bookworm.
I'm actually surprised the RPi imager worked with the image. Usually balena etcher or some other utility is required.

@cornholio I'm sure I'm just stupid... but I can't seem to get past the first login/pw check? No matter what I setup in the rpi imager, it always tells me that the password is wrong.. I have also tried all default passwords (like root/root & pi/raspberry..) any idea?

andypugh wrote:

pncconf does call mesaflash so if you don;t have mesaflash that might explain why discovery is not working.

Does "sudo apt-get install mesaflash" work?

Did you manage to create a config in Debian 12? If you did, then that same config should work in 11.
 

Hi Vector, tommylight and andypugh,

Thank you for the trouble-shooting discussion on Unspecified Error with Discovery option.

My computer is Raspberry Pi 4, Debian 12 Bookworm, the Kernel is Linux picnc 6.6.59-rt45-v8-behai-rt-build+ #1 SMP PREEMPT_RT Sat Nov  2 10:20:46 AEDT 2024 aarch64 GNU/Linux.

I am also able to ping it at 10.10.10.10, and I did have the same error when used Board Discovery.

Failing discovery, I selected:

[
Board name = 7i96s-Internal Data
Firmware = 7i96s_d
]

It appears to work, since I can move to other screens... I was not able to proceed any further, because I don't know what to do next yet.

Then I retry by running sudo apt-get install mesaflash, and afterward Board Discovery works:

[
Board name = Discovered: 7i96s
Firmware = ~/mesa0_discovered.xml
]

I am happy, this is a progress for me. I have read the configuration the HAL parts of the manual. But it still not registered yet... I have to do some more reading.

And also I have to learn how to connect the CL57T-V4 closed-loop motor driver the 7i96s.

Thank you and best regards,

...behai.

 

Hi,

I have just received my Mesa 7i96s today from Mr. Andrew Beck of BECK CNC.

I left W4 and W5 at their default setting ( I can't see jumpers ) And I have followed the instructions given in this thread, and I am able to ping it.

This is what I have done:

With the Ethernet cable connected between Mesa 7i96s and Raspberry Pi4

[
behai@picnc:~ $ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether d8:3a:dd:25:8c:37 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether d8:3a:dd:25:8c:38 brd ff:ff:ff:ff:ff:ff
]

I notice that eth0 shows <BROADCAST,MULTICAST,UP,LOWER_UP>

With the Ethernet cable disconnected:

[
behai@picnc:~ $ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether d8:3a:dd:25:8c:37 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether d8:3a:dd:25:8c:38 brd ff:ff:ff:ff:ff:ff
]

I notice that eth0 shows <NO-CARRIER,BROADCAST,MULTICAST,UP>

So I guess my hardwired ethernet is eth0.

Then I log into my home router to verify that 192.168.1/24 is not in used as per the official manual instruction.

I then added the following lines into /etc/network/interfaces:

[
auto eth0
iface eth0 inet static
address 192.168.1.121
hardware-irq-coalesce-rx-usecs 0
]

Then I ran sudo ifdown -a followed by sudo ifup -a, both ran successfully. I.e. they produced no output.

Then finally: ping 192.168.1.121

The response is continuous until I pressed Control + C to interrupt.

I HAVE A QUESTION, PLEASE:

While the pinging was running, I disconnected the Ethernet cable, I expect the response to stop or at least to halt, but it did not. It continues to produce pinging notifications. Is this normal, please?

Thank you and best regards,

...behai.




 

Thank you! Will try it out on friday.

Ok I’ll make a note of that.
Thanks for testing.

No image appeared on the screen, not working

Much appreciated Sir.

ok I'm trying right now

ok cool.

I've just built a new image could you give it a whirl if it doesn't work I'll say that its not recommended for the 5 with 16GB only tested with 4GB.

drive.google.com/file/d/1MEgxQ1IrdI2hnnw.../view?usp=drive_link

rpi-5-debian-bookworm-6.6.44-rt39-arm64-ext4-2024-08-12-2032.img this image worked

Ok, the 16GB board was only released at the beginning of the year, maybe you were thinking of the 8GB boards rod. So I don't think it's a Linuxcnc issue but a kernel issue.

What I would suggest you do is load up an sd card with an Raspberry Pi image, boot it up and relay the output of
I'm thinking it may require a 6.13.x or 6.12.x kernel. As the 6.6.y branch is active that keren may work but can't certain.

I think linuxcnc only works on 2-4-8gb,right?