> -----Original Message----- > From: Peter C. Wallace [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 16, 2008 10:02 AM > To: Enhanced Machine Controller (EMC) > Subject: Re: [Emc-users] hm2_7i43 hostmot2 loading - invalid cookie? > > On Thu, 16 Oct 2008, Keil Hillman wrote: > > > Date: Thu, 16 Oct 2008 00:55:01 -0700 > > From: Keil Hillman <[EMAIL PROTECTED]> > > Reply-To: "Enhanced Machine Controller (EMC)" > > <emc-users@lists.sourceforge.net> > > To: emc-users@lists.sourceforge.net > > Subject: [Emc-users] hm2_7i43 hostmot2 loading - invalid cookie? > > > > I can't get hm2_7i43 and hostmot2 modules to init 7i43 card > following > > firmware load. Been working on this for past month thinking the > > problem was hardware parallel ports, however the error > seems to be the > > same "invalid cookie, got 0xBCFE80FE, expected 0x55AACAFE". > The "read data" > > or "got 0xBCFE80FE" does change depending on paraport and firmware > > loading method used, but the end result is always "invalid > cookie" and > > "-1 Invalid parameters" command line error. > > > > In addition to loading firmware with hm2_7i43, I've tried other > > variations of commands, like loading firmware first with bfload > > followed by hostmot2 and hm2_7i43 (without firmware), but no luck. > > Firmware loading seems to go well, INIT and DONE off, but hm2_7i43 > > module insmod fails. > > > > Also, tried to connect to 7i43 using tools from > > mesa7i43-linux-utils-0.2.tar.bz2, but no luck either. Found the > > correct > > ieee1284 and python debs. Couldn't figure out parport > config stuff in > > python scripts. > > > > Here's the hardware: > > 0x378,0x0778 parport0 > > 0xd000,0xb800 parport1 (on-card port) > > 0xb400,0xb000 parport2 (ribbon cable port) > > 7i43 powered from USB, no USB drivers in kernel. > > > > software: > > debian sid > > Linux x2 2.6.22.081012.1 #1 PREEMPT Sun Oct 12 13:16:18 PDT > 2008 i686 > > GNU/Linux > > kernel /vmlinuz-2.6.22.081012.1 root=/dev/mapper/debian-root ro > > acpi=off pnpbios=off isapnp=off > > RTAI 3.6-cv (closure version) > > Emc2 trunk current > > > > Commands: > > /etc/init.d/realtime start > > sudo echo 4 > /proc/rtapi/debug > > halcmd -V loadrt hostmot2 debug_idrom=1 debug_module_descriptors=1 > > debug_pin_descriptors=1 debug_modules=1 halcmd -V loadrt hm2_7i43 > > ioaddr=0x378 ioaddr_hi=0x778 epp_wide=1 > > 'config="firmware=hm2/7i43/SV8S.BIT num_encoders=3 num_pwmgens=3 > > num_stepgens=0"' debug_epp=1 Or /etc/init.d/realtime start > sudo echo 4 > > > /proc/rtapi/debug halcmd -V loadrt hostmot2 debug_idrom=1 > > debug_module_descriptors=1 > > debug_pin_descriptors=1 debug_modules=1 sudo halcmd -V loadusr -w > > bfload 7i43:0x378,0x778=/lib/firmware/hm2/7i43/SV8S.BIT > > halcmd -V loadrt hm2_7i43 ioaddr=0x378 ioaddr_hi=0x778 epp_wide=1 > > 'config="num_encoders=3 num_pwmgens=3 num_stepgens=0"' debug_epp=1 > > > > Note: Double quotes in hm2_7i43 command took me some time to figure > > out, as the config modparam single quotes were getting stripped by > > Bash. This might be something to add to "man hostmot2". > > > > Commands http://pastebin.com/m512c5e55 dmesg > > http://pastebin.com/m59f40709 > > > > Regards, > > Keil > > > > Could be any number of things, but looks like maybe a signal > integrity issue or incorrect bitfile to me. > > 1. What length and kind of cable connects the 7I43 to the PC? > (cable should be IEEE-1284 compatible or flatcable, other > printer cables may not have enough > grounds) > > 2. You are using a bitfile for a 200K 7I43, is the 7I43 a > 7I43-2?. The 200K > 7I43s are a bit rare. > > 2A. If you do indeed have a 7I43-2, I will check the SV8S > bitfile here. I dont > think the 200k bitfiles have been tested as thoroughly > as the 400K ones > > 3. The FPGA's EPP interface is more tolerant of bad > end-of-cable signal > integrity than the CPLDs EPP interface (due to CPLD space > limitations) > The FPGA bitfiles are CRC checked, but we have seen > download problems that > the CRC checking misses. > One thing you might try to do to narrow down the problem > is to load the > FPGA via the local EEPROM instead of from the host. This > will require using > a windows machine and USB > > > Peter Wallace > Mesa Electronics >
1. I'll work on a better cable. I've got IDC26F connectors and some spare 26 flat cable and will crimp up something shortly. 2. Yes. My 7i43 has FPGA XC3S200 (3s200tq144), I think this equates to 7i43-2, card part# 7I43-U. I've noticed your updates mesanet 7i43.zip and will re-download and check md5sum's for 200K bitfiles. 3. Fine. Do I use sc7i43w.exe to load USBIOPR8 to FPGA (ram?) and scm7i43w.exe for firmware SV8S.BIT to serial eeprom? Will hostmot2 still allow for GPIO of un-initialized functions, when booting from eeprom? I'd think hostmot2/hm2_7i43 would init the same regardless of boot image source (host or eeprom). Only need servo stuff and possibly some general IO, so SV8 on eeprom would be great. Additionally, I've made JTAG connectors before for satellite boxes, what is DB25 to P6 pinout? I realize this is probably all google-able, since 7i43.pdf lists pin functions. Just curious. Thanks, Keil ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
