Bitfile for 7i80HDT with 7i44 and 7i48

Hi

Can I use a bitfile for a 7i80HD(non T) in my HDT card? 
I found a thread where PCW had created one that almost matches my setup.

If it is not possible, could some kind person create one for me?
Preferrably, the 7i44 would be on P1 and 7i48 on either P2 or P3.

You need a 7I80HDT bitfile as it uses a different FPGA

I can do this sometime next week

7I80HDT with 7I44 on P1, 7I48 on P2 and GPIO+INM on P3

 
 

Thank you very much! I will try it tonight.

The bitfile works perfectly. I wonder though, is the HDT really supported by 2.8?
When trying to start, LCNC says that it found an unrecognized board and that naming might be wrong. Pins are missing (eg. hm2_7i80.0.read) so it does not want to start. But when I reduce the hal file to bare minimum for it to actually start, the pins all show up in Show HAL Configuration

Its possible to make it work with 2.8 but there would be
name issues (and the complaint at startup)
I would use master (2.10)

Thanks PCW!
That will be my first choice on the real PC. For now I just have an old 32bit laptop (to try things on).
From what I remember 2.9-> binaries don't support 32bit. Maybe it'd work if I compile myself.

Now I've got the "real" PC. I tried to install the official LCNC iso, but had no luck with it. Something about not being able to write to sda.
However I managed to install 2.9 on Mint 20.3, but I noticed that it doesn't recognize the HDT either. Guess I have to struggle a little more with 2.10pre (complaining about Python being too new (>3.8).

'Til then I am tinkering a little with 2.9. One problem I have is that it doesn't seem to find the SSerial cards I have (7i70 and 71) no matter what I do. Could this have something to do with the naming problem?

7I80HDT support has been added to 2.9 so it you get a current copy
That should work.

SSerial is not affected by any of these name changes, that is more likely
related to hardware setup. It could also be an issue with the firmware,
I will verify that it works on hardware later today.

It was a firmware issue
should be fixed here (at least works for me)