Search

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 14 Nov 2014 11:25 AM by  Adam Ford
FPGA and DM3730
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Sergey Brandis
New Member
New Member
Posts:79


--
30 Oct 2014 04:25 PM
    Hi ! Thanx for all you answers. I want to connenct DM3730 and FPGA. I want to write driver . Where can I find physicall adress up_nWe, up_nOE,up_nCS1. ?My system is Windows Ce . Can you give me usefull advices about driver between FPGA and DM3730(Windows Ce) . Thanx beforehand.
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    31 Oct 2014 07:40 AM
    The pins for uP_nOE, uP_nWe and uP_nCS1 are part of the GPMC. The most detailed information about the GPMC is found in TI's DM3730 Techincal Reference Manual (http://www.ti.com/lit/pdf/sprugn4) and that includes the various memory addresses for accessing it.

    If your project is only going to use a few IO lines as GPIO, we have AN527 which describes how to use individual GPIO pins. http://support.logicpd.co...rtalid=0&EntryId=698

    Without knowing anything about your FPGA or schematic, it's difficult to offer much assistance, but we do offer both a support contract (http://support.logicpd.co...upportPackages.aspx) where we could offer schematic reviews and offer suggestions on how to best wire it electrically.

    If you wanted software help in writing the drivers, we also have a services contract (http://www.logicpd.com/se...oduct-development/).

    If you are interested, I can have someone from sales contact you.

    adam
    Sergey Brandis
    New Member
    New Member
    Posts:79


    --
    31 Oct 2014 09:18 AM
    Can I adress to GPMC ? Give me ,please , example ! Thanx beforehand !
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    31 Oct 2014 10:41 AM
    Unfortunately, we don't have any template examples, but the SMSC LAN9221 controller and the ST Ericsson ISP1763A USB controller both use the GPMC bus.

    You should be able to look at those drivers to see how they interact with the GPMC bus. Just make sure you use a different chip select to avoid contentions.

    adam
    Sergey Brandis
    New Member
    New Member
    Posts:79


    --
    13 Nov 2014 03:29 PM
    Can I use DCLK (GPIO_8),DATAO (GPIO_130) ,NCONFIG(GPIO_131),GetNStatus (GPIO_134) I found some functions in gpio.cpp . Is it true ?
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    14 Nov 2014 11:25 AM
    I don't fully understand what you are application is, but there is a difference between the GPIO and GPMC. If you want to just manually control individual GPIO pins, I would suggest you look at our App Note on Selecting and Using GPIO signals. http://support.logicpd.co...rtalid=0&EntryId=698

    Each GPIO pin shares functions with peripherals, so if you choose to use a certain pin as GPIO, the associate peripheral may cease to function. Our schematics found on http://support.logicpd.co...M3703TorpedoSOM.aspx under the

    If you are planning on using the GPMC bus which it seemed like you wanted to use, you'll have to use the pins that are associated to the bus.

    My suggestion would be to setup a support contract where we could look at your schematic and a block diagram of how your FPGA interfaces to the SOM, and we could make suggestions on how to connect it: http://support.logicpd.co...SupportPackages.aspx


    adam
    You are not authorized to post a reply.