Advanced Search

ruffle wrote:

Cornholio: That seems better in terms of general responsiveness.

dtoverlay=disable-wifi was already commented out in config.txt so WiFi was enabled but it ignored wpa_supplicant.conf and I had to setup the WiFi from menu-config.

It didn't auto-login as cnc but setting autologin-user=cnc in the "[Seat:*]" section of the /etc/lightdm/lightdm.conf does the trick.

There's still no raspi-config installed or available in the repos but maybe that's a generic bookworm change.

There's no dhcpcd installed so setting a static IP for the ethernet port (used for talking to my 7i76E in my use case) involves more Linux hackery than a Google search for setting a static IP on a Pi would suggest. A simple old school edit of /etc/network/interfaces sorts it.

When the screen is woken from screensaver, it asks for the cnc users password.

On the Good News front, running up linuxcnc worked and I could jog my steppers (I'm testing on my Lathe project which is currently just a pile of electronics and wires on the bench).

Is this feedback useful? I'm assuming the aim is to produce a RPi bookworm image that works for most folk.
 

Thanks for the feedback.
The screen saver thing is easily fixed in power settings (I can look into changing that without having to boot the image). For your Mesa card you have to give it a manual config, as the interface can't connect to a DHCP server(there should only be the motion card and computer directly connected). I thought network manager was installed for configuring the Network (It is set to install via the build config). I'll check that for sure. The setup should disable wifi & bluetooth during the build process.
I've never been a fan of auto login for Linux.
Raspberry config is a Rasp OS thing, this is based on Debian, apart from the kernel sources which are pulled from the RPi github page (the standard kernel has patches one of which is to work with the overlays), RT patches are from kernel.org. One thing that does annoy we, which I should fix, is that sudo doesn't require a user password. You might as well be running as root.

Cornholio: That seems better in terms of general responsiveness.

dtoverlay=disable-wifi was already commented out in config.txt so WiFi was enabled but it ignored wpa_supplicant.conf and I had to setup the WiFi from menu-config.

It didn't auto-login as cnc but setting autologin-user=cnc in the "[Seat:*]" section of the /etc/lightdm/lightdm.conf does the trick.

There's still no raspi-config installed or available in the repos but maybe that's a generic bookworm change.

There's no dhcpcd installed so setting a static IP for the ethernet port (used for talking to my 7i76E in my use case) involves more Linux hackery than a Google search for setting a static IP on a Pi would suggest. A simple old school edit of /etc/network/interfaces sorts it.

When the screen is woken from screensaver, it asks for the cnc users password.

On the Good News front, running up linuxcnc worked and I could jog my steppers (I'm testing on my Lathe project which is currently just a pile of electronics and wires on the bench).

Is this feedback useful? I'm assuming the aim is to produce a RPi bookworm image that works for most folk.

Omron MX2 and Hitachi WJ200 seem to be identical. Thats from the 0-10V wiring to 7i76e. I found also the setup sheet from Sorotec. I think, i had to increase 'F003' Deceleration time to avoid error when stop from max. rpm, which must be reset on the vfd. This setup running for years, only this info is left.

PCW wrote:

Can you ping the card?

ping 10.10.10.10

(if the card is set for 10.10.10.10 = W4 down W5 up and host PC setup properly)

 

 

I followed this guide with the jumpers as described (w4 down w5 up).
I got this from the ping.
I am a classic rookie on all this and this connection problem has haunted me on two different PC's, I am not sure I ever got a working connection then or now. I do now have a workable PC and a 95% built controller cabinet to test the capability of the card.
I have noticed when I am connected to the "Mesa Ethernet" connection wifi no longer works, I would like to figure out how to fix that because that makes troubleshooting all this very cumbersome.

It is possible that I changed the EPROM IP last year when I was trying to set this up on the other PC.
Would it be smart in that case to try the dn/dn jumper setting and using 192.168.1.121?
I did try that already with the same results.

ping 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
From 10.10.10.11 icmp_seq=1 Destination Host Unreachable
From 10.10.10.11 icmp_seq=3 Destination Host Unreachable
From 10.10.10.11 icmp_seq=6 Destination Host Unreachable
From 10.10.10.11 icmp_seq=7 Destination Host Unreachable
From 10.10.10.11 icmp_seq=8 Destination Host Unreachable
From 10.10.10.11 icmp_seq=9 Destination Host Unreachable
From 10.10.10.11 icmp_seq=10 Destination Host Unreachable
From 10.10.10.11 icmp_seq=11 Destination Host Unreachable
From 10.10.10.11 icmp_seq=12 Destination Host Unreachable
From 10.10.10.11 icmp_seq=13 Destination Host Unreachable
^C
--- 10.10.10.10 ping statistics ---
17 packets transmitted, 0 received, +10 errors, 100% packet loss, time 16210ms
pipe 3

 

 

This is the screenshot of the Ethernet setting page.

 

PCW wrote:

Only thing I notice is this:

setp hm2_7i76e.0.dpll.01.timer-us -50

I would change this to:
setp hm2_7i76e.0.dpll.01.timer-us -200
 

Thanks for the suggestion. What exactly does this do? 

Only thing I notice is this:

setp hm2_7i76e.0.dpll.01.timer-us -50

I would change this to:
setp hm2_7i76e.0.dpll.01.timer-us -200




 

Hi.
I have a 7i76e. Typical Ping times are 0.250ms.
Intel ethernet, so it should benefit from the coalesce mod.
File in use is /etc/network/interfaces

Attached screenshots illustrate the results of dmesg, ip, ping times and the interfaces text.

In other posts I've noticed that sometimes the "-" character is not an ANCII character. In this case I have manually typed in the last string using the "minus" key on the keyboard. I think I need a fresh pair of eyes. What am I doing wrong??
Thanks.
 
 
 
 


 

cornholio wrote:

Hey Rod does Bookworm work with SPI interface ? From memory last time I tried I couldn't for the life of me get it to work. Ended up using Raspbian based on Bullseye 64 bit.
Been messing around with a Spartan-6 FPGA dev board with modded 7c81 firmware to suit. And some of the Colorlight board based projects.

Think I've got it regarding spi & mesaflash talking to a 7c81 board
forum.linuxcnc.org/38-general-linuxcnc-q...pair?start=20#279367

Playing around with Bookworm first mesaflash is without a board connected, second is with board connected.

rmurphy@rpi4-20230612:~$ cat /etc/debian_version
12.0
rmurphy@rpi4-20230612:~$ ls /dev/spi*
/dev/spidev0.0 /dev/spidev0.1
rmurphy@rpi4-20230612:~$ sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --readhmid
sudo: unable to resolve host rpi4-20230612: Name or service not known
unable to set bpw32, fallback to bpw8
Unexpected cookie at 0100..0110:
00000000 00000000 00000000
No 7C81 board found
rmurphy@rpi4-20230612:~$ sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --readhmid
sudo: unable to resolve host rpi4-20230612: Name or service not known
unable to set bpw32, fallback to bpw8
Configuration Name: HOSTMOT2

General configuration information:

BoardName : MESA7C81
FPGA Size: 9 KGates
FPGA Pins: 144
Number of IO Ports: 3
Width of one I/O port: 19
Clock Low frequency: 100.0000 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256

Modules in configuration:

Module: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: IOPort
There are 3 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: QCount
There are 1 of QCount in configuration
Version: 2
Registers: 5
BaseAddress: 3000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes

Module: StepGen
There are 3 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: PWM
There are 2 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4100
ClockFrequency: 200.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: InM
There are 2 of InM in configuration
Version: 0
Registers: 5
BaseAddress: 8500
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P1+Serial -> 7C81_0
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

P1-01/DB25-01 0 IOPort StepGen 0 Step/Table1 (Out)
P1-02/DB25-14 1 IOPort None
P1-03/DB25-02 2 IOPort None
P1-04/DB25-15 3 IOPort None
P1-05/DB25-03 4 IOPort None
P1-06/DB25-16 5 IOPort InM 0 Input0 (In)
P1-07/DB25-04 6 IOPort InM 0 Input1 (In)
P1-08/DB25-17 7 IOPort InM 0 Input2 (In)
P1-09/DB25-05 8 IOPort InM 0 Input3 (In)
P1-11/DB25-06 9 IOPort QCount 0 Quad-A (In)
P1-13/DB25-07 10 IOPort QCount 0 Quad-B (In)
P1-15/DB25-08 11 IOPort QCount 0 Quad-IDX (In)
P1-17/DB25-09 12 IOPort None
P1-19/DB25-10 13 IOPort StepGen 0 Dir/Table2 (Out)
P1-21/DB25-11 14 IOPort None
P1-23/DB25-12 15 IOPort StepGen 2 Step/Table1 (Out)
P1-25/DB25-13 16 IOPort StepGen 2 Dir/Table2 (Out)
P5 3,6 17 IOPort SSerial 0 TXData0 (Out)
P6 3,6 18 IOPort SSerial 0 TXData1 (Out)

IO Connections for P2+Serial -> 7C81_1
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

P2-01/DB25-01 19 IOPort StepGen 1 Step/Table1 (Out)
P2-02/DB25-14 20 IOPort None
P2-03/DB25-02 21 IOPort None
P2-04/DB25-15 22 IOPort InM 1 Input0 (In)
P2-05/DB25-03 23 IOPort InM 1 Input1 (In)
P2-06/DB25-16 24 IOPort InM 1 Input2 (In)
P2-07/DB25-04 25 IOPort InM 1 Input3 (In)
P2-08/DB25-17 26 IOPort InM 1 Input4 (In)
P2-09/DB25-05 27 IOPort InM 1 Input5 (In)
P2-11/DB25-06 28 IOPort None
P2-13/DB25-07 29 IOPort None
P2-15/DB25-08 30 IOPort None
P2-17/DB25-09 31 IOPort None
P2-19/DB25-10 32 IOPort StepGen 1 Dir/Table2 (Out)
P2-21/DB25-11 33 IOPort None
P2-23/DB25-12 34 IOPort PWM 0 PWM (Out)
P2-25/DB25-13 35 IOPort None
P5 TXEN 36 IOPort SSerial 0 TXEn0 (Out)
P6 TXEN 37 IOPort SSerial 0 TXEn1 (Out)

IO Connections for P7+Serial -> 7C81_2
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

P7-01/DB25-01 38 IOPort None
P7-02/DB25-14 39 IOPort None
P7-03/DB25-02 40 IOPort None
P7-04/DB25-15 41 IOPort None
P7-05/DB25-03 42 IOPort None
P7-06/DB25-16 43 IOPort None
P7-07/DB25-04 44 IOPort None
P7-08/DB25-17 45 IOPort None
P7-09/DB25-05 46 IOPort None
P7-11/DB25-06 47 IOPort None
P7-13/DB25-07 48 IOPort None
P7-15/DB25-08 49 IOPort None
P7-17/DB25-09 50 IOPort None
P7-19/DB25-10 51 IOPort None
P7-21/DB25-11 52 IOPort None
P7-23/DB25-12 53 IOPort None
P7-25/DB25-13 54 IOPort None
P5 1,2 55 IOPort SSerial 0 RXData0 (In)
P6 1,2 56 IOPort SSerial 0 RXData1 (In)

As PCW said
"but mesaflash does require the SPI device driver "

Which you wont have if you can't load the device tree overlay.
Anyways good luck.

You seem all worried about not using the device tree. I don't believe the device tree is the only way to solve the problem.
The problem that is my immediate concern load_rt hm2_rpspi is working with spi on Bookworm. I now have a RaspberryPi OS 11 (Bullseye) disk that I can load when I need to run mesaflash.
My lower priority concern is trying to get mesaflash to run on Bookworm without device trees. I found the driver source for spi.c and spidev.c in the Bookworm preempt rt kernel that I am running.

The issue is and if you at this post forum.linuxcnc.org/38-general-linuxcnc-q...pair?start=10#279252
it explains why the device tree is not loading. CONFIG_OF_CONFIGFS=y is the important part.
Later in that post I checked the raspbian kernel config from my running RP400 for that option and it is there, but when I downloaded a RT arm64 kernel from debian and run grep on the kernel config it wasn't there. If the option was available it would have an N instead of Y.
Yep I had the kernel modules loading but no /dev entries under bookworm.

This explains the device tree far better than I could
docs.kernel.org/devicetree/overlay-notes.html

What lead me down this hole was when I was messing around with Linuxcnc-RIO which uses an ICE40 fpga and communicates via SPI. It would just not work under Debain Bookworm, but was fine with Bullseye. I don't want to recall how much time I spent.......and I only found out about the info I posted about above yesterday.

Sebastian has hm2_rpspi running under Debian Bookworm. I succeeded in getting spi-bcm2835 to load on boot but I still can't create the /dev/spi0.0 and /dev/spi0.1 devices on Bookworm. The kernel on Bookworm compiles the devices that would normally be loaded in the device tree as kernel modules. So, I am just trying to find out what piece or pieces are either missing or not loaded.
I just think it would be great to be able to run mesaflash on the 7c81 on Bookworm.

From the info I found, I could be wrong, the mainline kernel doesn’t support device tree overlays, or the mechanism required to get an spi device entry in /dev. It would seem this a patch that the raspbian team applies.
So I’m thinking that until the raspbian team has a kernel for bookworm, the Raspberry Pi will require Bullseye for any board that requires SPI to operate.
Bookworm should, in theory, be fine for Ethernet devices.
Now I could be totally wrong regarding this.

cornholio wrote:

I was under the impression that the hm2-rpspi required a entry in the dev folder for spi and the Hal gpio driver was a different beast.
 

hm2-rpspi does not require the SPI  device driver (or GPIO)
but mesaflash does require the SPI device driver