Create Account
Search
You are here: TDG Forum  >>  NXP SOMs and Development Kits  >>  LH7A404 Card Engine and Development Kit  >>   About Fast Peripherals bus accsess Error using PCMCIA Card

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 25 Jan 2006 04:08 AM by  hashimoto
About Fast Peripherals bus accsess Error using PCMCIA Card
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
hashimoto
New Member
New Member
Posts:


--
28 Dec 2005 06:51 PM
    Hi,everyone.
    We are developing the network device using IEEE802.11x with PCMCIA Card.
    Our app board has single slot PCMCIA and some devices(RTC , VOCODER LSI, etc...).
    PCMCIA is mapped on the address space starting at 0x5000.0000,
    Another devices that except PCMCIA is mapped based on 0x7300.0000 as Fast Peripherals area available for user.
    The fast Peripherals devices has 16-bit wide bus data.

    Wireless PCMCIA Card is controled by ORiNOCO driver Ver 0.11b and running the task alternately fast Peripherals devices on linux thread.
    When PCMCIA is not controled, Fast Peripherals can be normally accessed.
    but PCMCIA driver begins running, Fast Peripherals access error often occurs.
    In PCMCIA, the error doesn't occur.

    We investigated all sorts of things including hardware factor and had follwing matters.

    1. Immediate cause of error is LH7a404 CPLD didn't generate nIOWR and nIORD.
    The other signal(uP_MA, uP_MD,FAST_nMCS) is not problem.

    2. It is not the collision by the each devices peculiarity delay.

    3. Incidence of access error increases when PCMCIA Access and Hold Time is short relative to fast Peripherals Wait State.


    Why is not the nIOWR and nIORD signal generated using PCMCIA Card?
    Do know some thing about this?

    thanks.
    kurtl@logicpd.com
    New Member
    New Member
    Posts:


    --
    29 Dec 2005 11:33 AM
    Please be sure you are using the latest CPLD code, version 3.2 is the latest on the web. You can download from this link if you have registered your kit.
    http://www.logicpd.com/do...oads/387/1001776.upd

    Signals uP_PCC_nIORD and uP_PCC_nIOWR must be used for PCMCIA accesses. Devices using the Fast_nMCS should use uP_nMWR and uP_nMRD for read and writes.

    The CPLD nIOWR, nIORD outputs are qualified by nCS6, nCS7, nRD, nWE0. Make sure the RBLE bit is set in BCR6 and BCR7 for proper nWE0 assertion.

    Good luck.
    -Kurt
    hashimoto
    New Member
    New Member
    Posts:


    --
    15 Jan 2006 11:18 PM
    Hi Kurt.Thank for your reply.

    We implemented the latest CPLD code(Ver3.2) and changed WR signals connect to uP_nMWR,
    RD signal connect to uP_nMRD.
    Wired LAN and Peripherals bus can be access on LoLo shell.
    But using ARM Linux boot Loader(Blob) is Impossible.

    Both LoLo and Blob can use Wired LAN and Peripherals in CPLD Ver 3.0.
    Why only Blob Failed using CPLD Ver 3.2 ?
    Blob Loader is Metrowerks BDK Distribution for LogicPD Sharp LH7A400/LH7A404 Zoom Starter Development Kits.

    Please Tell me what kind of influence on Changing CPLD Ver 3.0 to 3.2.
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    16 Jan 2006 08:34 AM
    If you look under the PCN (Product Change Notifications), you will find documents that describe each hardware change, including CPLD code that we make.

    http://www.logicpd.com/auth/downloads/LH7A404/#changes

    You will find two docs, one for CPLD code 3.1 and one for 3.2 that discuss what has changed in each.

    PCN 285 LH7A404-11 CPLD Change v3.1
    PCN 287 LH7A404-11 CPLD Change v3.2

    I believe the changes documented in PCN 287 are likely your culprit here.

    Thanks,
    -Mike
    hashimoto
    New Member
    New Member
    Posts:


    --
    24 Jan 2006 09:12 PM
    Thanks to your advice.
    We have resolved the problems by implementing CPLD Ver3.2 and letting NAND_nCE (GPIO Port C bit) de-assert with unusing flash memory.

    Former advice say...
    "Devices using the Fast_nMCS should use uP_nMWR and uP_nMRD for read and writes"
    But uP_nMWR somtime doesn't assert in write access.
    On this account,We are using nIOWR and nIORD for Fast Peripherals bus.
    Does We have anything considering about this?
    I wonder how of case uP_nMWR and uP_nMRD should be using.

    Thanks.
    hashimoto
    New Member
    New Member
    Posts:


    --
    25 Jan 2006 04:08 AM
    Hello.
    Wired LAN's IRQ don't assert sometimes using PCMCIA Card.
    The trouble was settled by setting IDCY is 0x0f on BCR7 registers.
    Is it necessary timing condition to use Wired LAN ?

    Dump out messages are as follows.

    NETDEV WATCHDOG: eth0: transmit timed out
    eth0: transmit timed out, IRQ conflict?
    -----smc_dump-----
    -----BANK0-----
    TCR = 0001
    EPH = 0000
    RCR = 0300
    CNT = 0000
    MIR = 0004
    RPC = 0880
    -----BANK1-----
    CFG = b0b1
    BAS = 1801
    GPR = 0000
    CTL = 1210
    -----BANK2-----
    ARPN= 0303
    RXTX= 8080
    PTR = 0000
    ISR = b30c
    -----BANK3-----
    REV = 3391
    ERX = 001f
    =====

    Thanks.
    You are not authorized to post a reply.

    Forums NXP SOMs and Development Kits LH7A404 Card Engine and Development Kit