On Thursday 03 November 2016 16:57:26 Gene Heskett wrote: > On Thursday 03 November 2016 12:55:49 Gene Heskett wrote: > > Greetings all; > > > > My G0704 is at the moment, precluded from my bringing a rotary table > > down from the shop and just plugging it in when I need it, which is > > how I have it configured on the toy mill, which, while I have > > the5i25's to do it, is still running software stepping o the > > parport. But because I needed some home switches on the G0704, that > > 4th stepper was removed from the loadrt line to get me usable I/O > > for homeing. > > > > My Bad, as I should have built the 3nd, cable & bob for P2 on the > > 5i25. I can change it of course but the big box has no remaining > > room for the 4th driver anyway without mounting it and a supply > > externally. I will probably do it eventually, but its going to be a > > major PIMA to get it all rebuilt. > > > > As I initially setup the 7i90HD, my thoughts are that what gpio I do > > use should probably start at the last available pins on the 3rd 50 > > pin connector, and grow downward from there, so that if, in the > > future, I add another encoder, pwmgen or stepgen to run some > > accessory (toolpost grinder for instance) to the controlled items, > > they will presumably be grown across the 1st 50 pin connector to 2 > > 2nd, and eventually meeting the gpio in the middle, but at no point, > > given time and imagination limits remaining for me, will I be forced > > to re-write my hal file, and rewire a boatload of stuff to get it > > out of the way when another stepgen or whathaveyou is added. > > > > Is this a realistic target? > > Connectors are here & programming cable made. > > ?Apparently no. Reading between the lines of some of the non-bit > files, its apparent that the stepgens are all on the 50-72 connector > which I'd have to assume is the third one, on the end of the card. > And that all outputs are present in true an complement on adjacent > pins, so CAN be used as differential drive sources. Not 100% > confirmed but it looks as if the other stuff follows a similar pattern > but not all start at that individual connectors pin 1, or first active > pin as the case may be. > > Since separating out the 7i90 *.bit files into just the 7i90_spi > family, I still have not heard which is the best one to load with > mesaflash when starting out with a 2 axis+spindle+1encoder lathe. So, > unless someone has a better idea, I am going to put the > 7i90_spi_svst8_4.bit file in it, and see what comes up in dmesg. At > loadrt time in the hal file, I'll ask for an extra one of each so I > have a spare already allocated. > > I am drowning in a lack of human readable docs here folks, doesn't > anyone have a life preserver? > > I'd say my cable is good, a query:gene@sheldon:/lib/firmware/hm2/7i90$ > sudo mesaflash --epp --device 7i90HD > [sudo] password for gene: > > EPP device 7I90HD at 0x0378:0x0778 > > Next question, ISTR useing the --write option, but I see in the --help > output, a --program option, so which is it? > > Humm, I just had it do a --readhmid, and it looks to be already > programmed. But does not identify what bit file it might be. > > From the readhmid printout, I have 8 stepgens, 4 pwmgens and 4 > encoders. > > Must be time to rig a psu for it, and see if I can hook it to the pi. > Damn I wish I had a monitor on the pi. But that connector/adapter is > in a bag, someplace in the USPS system. And in a separate order, a > $16 swinging wall mount for the monitor so I can mount it well above > the spindle end of it, on a stick of now rusty 1.5" square tubing. > > And I'll have to jury rig a small router to imitate a hub too, so this > will take the rest of the day unless I table this till I can monitor > it direct. I need earlier in the day mail deliveries, this 15:30ish > sucks. I think I'll table it and go see what I am to get for dinner. > > Thanks everybody. > > Cheers, Gene Heskett Continued. I thought I would confirm the program in it by verifying it, but now I think its not programmed for spi, but possibly for epp, as I am getting the same verify error, and I've tried 2 of the spi files.
That error is: gene@sheldon:/lib/firmware/hm2/7i90$ sudo mesaflash --epp --device 7i90HD --verify 7i90_spi_svst4_8.bit Checking file... OK File type: BIT file Boot sector OK Verifying EEPROM sectors starting from 0x100000... | Error at 0x1000EB expected: 0x1 but read: 0x8 So, I get brave, and --write the 7i90_spi_svst8_4.bit file to it That appeared to work, but said I had to reload or power cycle it to take effect. 7i90 cannot reload, so power cycled it. Now mesaflash can't find it. Now, that x86 computer I did that from hasn't a clue w/t/heck an spi is, so, time to bring the board back, along with a psu, and see if I can get the pi to recognize it. This out to be fun, so I'll close this and get to it. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
