On Thu, 8 Oct 2009, Dave Camarillo wrote:
> Date: Thu, 8 Oct 2009 18:21:46 -0700
> From: Dave Camarillo <dave.camari...@gmail.com>
> Reply-To: "Enhanced Machine Controller (EMC)"
> <emc-users@lists.sourceforge.net>
> To: emc-users@lists.sourceforge.net
> Subject: [Emc-users] HAL setup of Mesa 4i65
>
> I'm trying to bring up a 4i65 card on a PC-104+ stack and am having a
> little trouble with the hal driver load process. When I load the
> hm2_pci driver, it doesn't seem to do anything of interest. The
> 'dmesg' output indicates it's loading a driver and what the version
> is, but when I do a "show all" in halcmd it doesn't show any pins...
> I've messed with loading some of the other hal drivers, and the
> parallel port driver and those all cause pins to start showing up, but
> not this one.
> Below is more detailed information, any ideas as to what might be up?
>
> Thanks,
> -Dave
>
>
>
> Running EMC 2.2.4-pre, latest git clone
> --------------------------------------------------------------------------------------------------------------------------------------------
> Firmwre paths:
>
> # ls -la /lib/firmware/hm2/4i65/
> total 528
> drwxr-xr-x 2 root root 4096 2009-10-08 15:20 .
> drwxr-xr-x 9 root root 4096 2009-10-08 15:20 ..
> -rw-r--r-- 1 root root 167057 2009-10-08 15:20 SV12.BIT
> -rw-r--r-- 1 root root 6645 2009-10-08 15:20 SV12.PIN
> -rw-r--r-- 1 root root 167061 2009-10-08 15:20 SVST8_4.BIT
> -rw-r--r-- 1 root root 167061 2009-10-08 15:20 SVST8_4IM2.BIT
> -rw-r--r-- 1 root root 6821 2009-10-08 15:20 SVST8_4.PIN
>
> --------------------------------------------------------------------------------------------------------------------------------------------
> Hal Commands
> halcmd: unload all
> halcmd: loadrt trivkins
> halcmd: loadrt hostmot2
> halcmd: loadrt hm2_pci config="firmware=hm2/4i65/SVST8_4.BIT
> num_encoders=2 num_pwmgens=0 num_stepgens=3"
> halcmd: show all
> Loaded HAL Components:
> ID Type Name PID State
> 5 User halcmd7206 7206 ready
> 4 RT hm2_pci ready
> 3 RT hostmot2 ready
> 2 RT trivkins ready
>
> Component Pins:
> Owner Type Dir Value Name
>
> Pin Aliases:
> Alias Original Name
>
> Signals:
> Type Value Name (linked to)
>
> Parameters:
> Owner Type Dir Value Name
>
> Parameter Aliases:
> Alias Original Name
>
> Exported Functions:
> Owner CodeAddr Arg FP Users Name
>
> Realtime Threads:
> Period FP Name ( Time, Max-Time )
> 999849 YES servo-thread ( 0, 0 )
>
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------
> Dmesg
> [ 4001.518223] hm2: loading Mesa HostMot2 driver version 0.15
> [ 4001.540869] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.6
>
>
> --------------------------------------------------------------------------------------------------------------------------------------------
> Partial output from lspci -vvnn
> 01:07.0 Bridge [0680]: PLX Technology, Inc. PCI9030 32-bit 33MHz PCI
> <-> IOBus Bridge [10b5:9030] (rev 0a)
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
>> TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Interrupt: pin A routed to IRQ 15
> Region 0: Memory at fddff000 (32-bit, non-prefetchable) [size=128]
> Region 1: I/O ports at ef00 [size=128]
> Region 2: Memory at fdc00000 (32-bit, non-prefetchable) [size=1M]
> [virtual] Expansion ROM at fdb00000 [disabled] [size=64K]
> Capabilities: [40] Power Management version 1
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0+,D1-,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [48] #06 [0080]
> Capabilities: [4c] Vital Product Data
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
Thats totally busted, there should be 6 regions (3 I/O and 3 memory) with
sizes of 128,128 (bridge access memory and I/O)
64K,256 (16 bit wide memory and I/O port to FPGA)
64K,256 (32 bit wide memory and I/O port to FPGA)
Looks like either the EEPROM is disabled (via the jumper) or its contents are
corrupted badly...
Another possibility is that theres another PCI9030 chip in the system (does
the driver skip these cards?)
Theres a DOS or Windows (Sorry no Linux) tool to reprogram the EEPROM if its
somehow gotten corrupted.
Peter Wallace
Mesa Electronics
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
