Advanced Search

Hi,

using the prepared OS image "rpi-4-debian-bookworm-6.12.11-arm64-ext4-2025-01-27-0404.img.xz" from linuxcnc.org on a Pi4/4GB, I have no luck talking to my 7c80 board, which is connected with a 20cm ribbon cable to my RPi:

$ mesaflash --spi --device 7c80 --addr /dev/spidev0.0 --readhmid
Unexpected cookie at 0100..0110:
00000000 00000000 00000000
No 7C80 board found

This is both for the system-wide installed mesaflash as well as a separate build straight from github sources as of today.

I am (now) aware that cable length might be an issue here as SPI runs at a swift 20 MHz.

If possible (as replacing the cable with a much shorter one would involve quite a bit of mechanical disassembly and rework of my controller box) I would like to try the SPI connection first at slower speeds.

Is it possible to test (maybe bitbang even?) the SPI connection to the 7C80 FPGA to test whether the whole setup is working in principle? If so, are there any major problems expected then running everything with a reduced data rate (I am only planning to drive two steppers with this setup, so hopefully not a lot of bandwidth is needed)?

Can the FPGA be accessed slowly or are there timeouts preventing this?

I brazenly tried to reduce the SPI speed in spi_boards.c down to various rates, down to 100kHz, but that didn't help.

scotta wrote:

1. Convert an ST-Link to a CMSIS-DAP probe by using a a second ST-Link and the ST-Link utility to flash the CMSIS-DAP firmware.

mvdlande.wordpress.com/2015/10/05/cmsis-...ink-v2-mini-adapter/

2. Use pyOCD with the newly flashed CMSIS-DAP probe to flash the firmware to the controller board

python -m pip install -U pyocd
pyocd flash .\remora-rt1052-3.1.3.bin --target mimxrt1050_quadspi

github.com/scottalford75/Remora-RT1052-c...ora-rt1052-3.1.3.bin
Hello, I'm coming back to the charge on my RT 1052 card, I'm trying to flash with the CMSIS-DAP firmware but I have an error message the card is not detected?

 

 

Today i reran the PnCConf and the Startup Error didn't show.
But the WLAN Problem still persists.

I am running Debian on my Thinkpad T420
The mesa is connected to the Ethernet port and when I connect to WLAN the connection to the MESA Card fails, it happens both with 10.10.10.10 and with 192.168.1.121.

Network:
IP 192.169.1.10 Mask: 255.0.0.0 Gate: 0.0.0.0
IP 10.10.10.11 Mask: 255.0.0.0 Gate: 0.0.0.0

Yes, I had the Ohmic sensing into the B encoder input on TB2.

That's OK with 7i96dpl.bit firmware (that has three separate encoder 'A' pins)

Ok then.

I will use the existing toroidal tranformer (3 isolated windings each 28.5VAC) and run the DM556 on 38.5VDC from my rectifier and run the 2 DM860 drivers on 57VAC.

Thanks.

Change quotes around D3 (note the different appearance when you try to open the attached XML):

 

Could you post your hal files (IE the one that uses caxis.comp and the one with the orient.comp)?

I made a new xml with only the beckhoff EK1100. Now i get a new error

Another way to fix that is to chose the output polarity of the PWM
so its 0V at startup or watchdog bite (the STEP- pin) and then invert
the PWM in the hal file.

Its still a good idea to disable the spindle when LinuxCNC is not running
If the enable is an optocoupler input, a single resistor (R1)  will do
If its a 5V logic input, you need R2.

Safest would be to implement both (0 PWM at startup which is just a
wiring and hal change) and drive enable.

For some reason, the negative lead of the original rectifier was connected to ground.

I do not know why.

i got my 32 relay card today and changed something in the setup, i will test everything again later.

you can now use func:6 and set the datatype (new option) to bool, as register the 112 (0x70) and Values = 16

 

Soldering Iron or Wood Burner temps will melt skin. Had a friend when I was 9 or 10 who picked up his mum's Wood Burner Iron. Old Greg was a built different to everyone else. Pretty sure when he was working on a trawler he just pulled the tuna in with his bare hands, bet he would of tried to bite the heads off a few as well.

Actually I've just had another thought, what version of RPi imager are you using and what particular OS ?
I'm not a windows user and some people have had issues with RPi imager ?
Do you uncompress the downloaded file or just point RPi imager to the compressed file ?

Cheers
Rob

The images are not Raspbian based, so any pre imaging before writing to SD card will not work. This is mentioned in the sticky regarding the RPI images:

forum.linuxcnc.org/9-installing-linuxcnc...the-rpasberry-pi-4-5

Yeah I haven't really been happy with the way locales are setup. I would really like to come up with a solid solution and add that to the sticky mentioned above.

Regarding wireless:
wiki.debian.org/WiFi/HowToUse#Using_ifupdown_and_wireless-tools

I'm thinking network-manager and gnome network tools would make setting up networks somewhat easier.