Advanced Search

Cant do this anymore bye all wrote:

No but it has been mentioned multiple times in multiple places (pretty sure I have mentioned it myself in this thread, maybe my posts are too long), why it isn't enabled by default is only something those that produce the images can say. I was a advocate for enabling it by default and disabling BT & sound

Or at least this should be mentioned on the download page, but people being people they can be lazy and only want the goodies or they only follow links to the actual downloads.

As you can see there is only one spi device interface that the 7c80 will respond to without a custom cable.

PCW wrote:

You need to enable spidev0.0 by turning SPI on in the boot/broadcom/config.txt file

(I have no idea what pins spidev10.0 connects to)

 

pi@linuxcnc:/dev$ ls spi*
spidev0.0  spidev0.1  spidev10.0

pi@linuxcnc:~$ sudo mesaflash --device 7c80 --addr /dev/spidev1.0 --spi --readhmid
open: No such file or directory
No 7C80 board found
pi@linuxcnc:~$ sudo mesaflash --device 7c80 --addr /dev/spidev10.0 --spi --readhmid
Unexpected cookie at 0100..0110:
ffffffff ffffffff ffffffff
No 7C80 board found
pi@linuxcnc:~$ sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid
Configuration Name: HOSTMOT2

General configuration information:

  BoardName : MESA7C80
  FPGA Size: 9 KGates
  FPGA Pins: 144
  Number of IO Ports: 2
  Width of one I/O port: 27
  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

Cant do this anymore bye all wrote:

blazini36 wrote:

Yeah Tommy is pretty much correct in the fact that 1.5Mbaud does not equal 1.5Mbit because there are wasted bits.....start, stop, parity, address, etc
 
That will affect the overall byte rate, not the overall bit rate. If fact Tommy's definition made no mention of of protocols, which stop-start-parity etc would be part of.
When designing hardware for the transmission of serial data any control bits or bytes don't come into the equation.
 

ccatlett1984 wrote:

PCW wrote:

If you can reliably access the card on the RPI4, you would

sudo mesaflash --device 7c80 --spi --addr /dev/spidev0.0 --write 7c80d.bit
sudo mesaflash --device 7c80 --spi --addr /dev/spidev0.0 --write 7c80fall.bit --fallback

(7c80d.bit and 7c80fall.bit are in the 7c80.zip file in /configs/hostmot2/)
the zip file is available from the store in the card specification tab

 
From Pi4, dump of mesaflash BEFORE flashing: pastebin.com/kf8iUXQY
dump of mesaflash AFTER flashing: pastebin.com/5xm8FHpq

I forced a --reload in between each flash cmd, to validate the card took the firmware before moving on.

If this looks correct, I will proceed to swapping the pi5 back into the machine.

Update: Post flashing, with the Pi5 - halcmd sees the card.

pi@linuxcnc:/$ sudo mesaflash --device 7c80 --addr /dev/spidev0.0 --spi --readhmid [sudo] password for pi: open: No such file or directory No 7C80 board found
in /dev/ only a single spi entry exists "spidev10.0"
running mesaflash (using the above spi entry) results in the following

pi@linuxcnc:/$ sudo mesaflash --device 7c80 --addr /dev/spidev10.0 --spi --readhmid
Unexpected cookie at 0100..0110:
ffffffff ffffffff ffffffff
No 7C80 board found
pi@linuxcnc:/$