- Posts: 46
- Thank you received: 0
Mesa 7i43 (2port parallel) 400K with bitfile SVST2_4_7i47 using PnCConf
i ordered a 7i43 card and want to use the pin file SVST2_4_7i47 because it fits best to my project.
Found some information here.
linuxcnc.org/docs/2.6/html/drivers/hostmot2.html
My system:
LinuxCNC/AXIS version 2.7.14
Linux linuxcnc 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686 GNU/Linux
For testing purposes i used SVST4_4 to see if my card is working. And it is working.
In PnCConf is no SVST2_4_7i47 selectable. I downloaded 7i43.zip file from mesa.
Used the bit file "SVST2_4_7I47S.BIT" and copied it to /lib/firmware/hm2/7i43-4/
Copied the pin file "SVST2_4_7I47.PIN" to /usr/share/doc/hostmot2-firmware-7i43-4
But the file is not selectable in PnCConf.
Attachment not found
Is this the right bit file (4Encoder/2PWM/4StepGen/24GIPO) as discribed in the documentation above?
And what do i have to do to make this file selectable in PnCConf?
Many thanks
Manfred
Please Log in to join the conversation.
pncconf does not automatic get the Bit and Pinfile
PLEASE ask cmorney if he got it inside
it is under constand Development
you can also ask in the Live Chatroom on IRC
PCW will help you Calafornia Timezone
Please Log in to join the conversation.
pl7i92 wrote: loading the 7i43 with a 7i47 Bitfile is not in general a good idee as it is not build for this
The 7i47 is just a 50-pin daughter card. There is no reason that it wouldn't work perfectly well with the 7i43.
Please Log in to join the conversation.
hal/ini file set for a similar configuration (say SVST4_4) and edit the hal file to make any 7I47 specific changes.
Note that since stepgens, pwmgens, and encoder hardware is accessed in hal by number, not pin, there is very little difference in configurations for different daughtercards that have have basic stepgens, encoders, pwmgens etc
Please Log in to join the conversation.
PCW wrote: I dont think pncconf supports that configuration but you can use pncconf to create a working
hal/ini file set for a similar configuration (say SVST4_4) and edit the hal file to make any 7I47 specific changes.
Note that since stepgens, pwmgens, and encoder hardware is accessed in hal by number, not pin, there is very little difference in configurations for different daughtercards that have have basic stepgens, encoders, pwmgens etc
I don´t really understand, sorry.
Let´s say i use SVST4_4 configuration and use only 1Encoder, 1PWM, 4StepGen. Will this result in some GPIO?
Please Log in to join the conversation.
FPGA card or firmware. The only difference would be any GPIO pins used as plain GPIO,
or inversion of PWM/Stepgen pins referenced by GPIO pin number (and the base FPGA card name)
That is if you just have 1 PWM generator, its always going to be referred to as PWM 0
in the hal file not by the pins its connected to.
Likewise, if you have 4 Stepgens, they will be accessed in hal as stepgen 0 to stepgen 3
Please Log in to join the conversation.
Used SVST4_4 bitfile and created only 3 step generators. On the tabs for IO connector 3 and 4 i have now many unused inputs.
After starting my configuration i listed the pinout with
But the pins are not as expected. There are PWM, Encoder but no GIPO.
Attachment not found
Please Log in to join the conversation.
All pins are available as GPIO if they are not claimed by an _enabled_ secondary function (Sec. func)
Edit
Also you should not run mesaflash when LinuxCNC is running ( notice the bad data on GPIO23?, this is likely due to a access collision )
To check available hardware pins, run
halcmd show pin hm2*
or
for gpio:
halcmd show pin *gpio*
Please Log in to join the conversation.
mane wrote: Today i tried to make a very basic configuration with PnCConf.
Used SVST4_4 bitfile and created only 3 step generators. On the tabs for IO connector 3 and 4 i have now many unused inputs.
After starting my configuration i listed the pinout with
Code:sudo mesaflash --device 7i43 --epp --addr 0x378 --readhmid
Mesaflash lists the firmware pinout, not the pinout that is active in your configuration.
If you start LinuxCNC from the command line you should get the actual pinout that your config is using listed on the screen.
Please Log in to join the conversation.
andypugh wrote: Mesaflash lists the firmware pinout, not the pinout that is active in your configuration.
If you start LinuxCNC from the command line you should get the actual pinout that your config is using listed on the screen.
Tried to start from command line, but nothing listed on the screen.
Please Log in to join the conversation.
