I've run into a snag getting my 7i43-P talking to my EMC machine.. This is a new setup, so I assume I've got some stupid configuration issue. Any assistance would be appreciated..
I've got a AT5NM10-I set up with LiveCD install with an on board parallel port attached to a 7i43-P. It's the 200K model. Rev C. the parport modules are blacklisted in an attempt to isolate my problem. The 7i43 is powered by an external power supply (+5V) in P1. P2 is connected to a IDC ribbon cable <-> DB25F <->DB25M to M adaptor <-> PC. The whole assembly is about 4 inches long. As far as I can tell, the ribbon cable assembly rings out true. P3/P4 have nothing connected yet. I've got a couple 7i40s to connect once I get over this hump. Powering everything up, (in EPP mode) all three lights come on. I load hostmot2 and then attempt a firmware load. The INIT light goes out and I get an "invalid module" parameters error. dmesg indicates that the driver thinks I've got a 400K board (I think this is actually the driver reading FFs instead of a 0 or 1). I haven't determined if the data displayed by debug_epp is actually what's the bus or not. I hooked up an O-Scope in an attempt to determine what was going across the port, but need to spend some time looking at the source code to make heads or tails of it. I thought someone here might have a shorter path. If I set the board to load from EEPROM, the lights flash on and then INIT and DONE go out. I'm not sure what's on the EEPROM and haven't done enough research to determine what to transmit to test the board in this state. Also, I attempted to use the DOS utilities (under WinXP) from mesa for the 7i43. Those didn't work either, but the cable assembly was common between my two setups & the Parallel port was on a laptop docking station. I got the same results as if I gave it a bad port address (all 0xFFs); so I take those results with a grain of salt. Hopefully this weekend I'll have access to a DOS box with more standard hardware for another test. (and some more parts to make another cable). Here's some initial debug info: uname -a: Linux CNC 2.6.32-122-rtai #rtai SMP Tue Jul 27 12:44:07 CDT 2010 i686 GNU/Linux Jumper configuration: W1 UP W2 UP W3 UP W4 DOWN W5 DOWN W7 UP bash> halrun halcmd: loadrt hostmot2 halcmd: loadrt hm2_7i43 config="firmware=hm2/7i43-2/SV8.BIT" debug_epp=1 insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/emc2/hm2_7i43.ko': -1 Invalid parameters <stdin>:6: exit value: 1 <stdin>:6: insmod failed, returned -1 See the output of 'dmesg' for more information. dmesg output: [ 300.294207] hm2_7i43: loading HostMot2 Mesa 7i43 driver version 0.3 [ 300.296964] hm2_7i43: wrote control 0x04 [ 300.296973] hm2_7i43: read status 0xD6 [ 300.296983] hm2_7i43: selected address 0x7F7F [ 300.296990] hm2_7i43: wrote data 0x5A [ 300.296998] hm2_7i43: selected address 0x7F7F [ 300.297004] hm2_7i43: wrote data 0x5A [ 300.297011] hm2_7i43: selected address 0x01 [ 300.297017] hm2_7i43: wrote data 0x00 [ 300.297026] hm2_7i43: wrote data 0x01 [ 300.299047] hm2_7i43: read data 0xFE [ 300.299054] hm2_7i43: selected address 0x00 [ 300.299060] hm2_7i43: read data 0xFF [ 300.299099] hm2_7i43.0: firmware: requesting hm2/7i43-2/SV8.BIT [ 300.312780] hm2/hm2_7i43.0: board has FPGA '3s400tq144', but the firmware in hm2/7i43-2/SV8.BIT is for FPGA '3s200tq144' [ 300.312797] hm2_7i43.0: board at (ioaddr=0x0378, ioaddr_hi=0x0778, epp_wide ON) not found! ------------------------------------------------------------------------------ Forrester recently released a report on the Return on Investment (ROI) of Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even within 7 months. Over 3 million businesses have gone Google with Google Apps: an online email calendar, and document program that's accessible from your browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
