This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MMWAVE-DFP: Some details about mmwave-devpack and the ftdi chip on it

Part Number: MMWAVE-DFP
Other Parts Discussed in Thread: AWR1243, AWR1243BOOST, MMWAVE-STUDIO

Does TI have any information about mmwave devpack, especially for the configuration program of the 4 mpsse serial ports of the ftdi chip or the dll dynamic link library? In this way, I can implement soc combining 1243 chip with mmwave devpack function in subsequent products.Thank you.

  • Please refer to the mmwave DevPack schematic and assembly file for detailed info. It will help you to define your custom board (AWR1243+FTDI).

    http://www.ti.com/lit/df/sprr252/sprr252.zip

    Regards,

    Jitendra

  • Thank you for your reply.

    Is there any program example about the FTDI chip on mmwave-devpack? As far as I know, the ft4232h chip used by mmwave_devpack is an MPSSE port, and the default conversion is usb to uart. So it has to be a program to configure the ftdi chip in usb to spi MPSSE mode. Would you mind providing some information about this? Thank you!

  • Hello,

    Are you are using your own SW to communicate to the FTDI? You can find the standard drivers on the FTDI webpage that can be used to operate it in SPI mode.

    Regards,
    Vivek 

  • Hi,Vivek

    Thank you for your reply. :)

    Do I have to use my own SW to communicate to the FTDI? If not,I prefer to using TI's mmwave example of DFP. So if I‘ve connected all the I/Os or interfaces(spi,IRQ,nreset,nerror,SOP......)correctly between AWR1243 and FTDI-FT4232H(the chip which TI use on the mmwave-devpack) like what mmwave-devpack did, could I run mmwave example succesfully?

    Regards,
    Junzhe

  • Hello Junzhe,

    You are right, if you keep the same pin mapping , same utilization, you can just use the FTDI drivers available in the mmwave DFP package and the run the mmwave DFP example.

    Regards,

    Vivek

  • Hi,Vivek

    Thank you for your reply. 

    I tried to connect all the interfaces that ftdi can export to AWR1243,then ran mmwave_example.exe ,it got 4 devices connected but  still shows mmwave device is not connected at first,return error-8 and couldn't call Poweron API. I listed my steps, did I miss anything?

    1.I have an AWR1243BOOST and an FTDI development board with an FT4232H chip onboard. The development board has all the pins of the ftdi chip.

    2.I found the position of the functional pins corresponding to ftdi according to the schematic of mmwave-devpack. For example, the SPI pins are ADBUS0 ~ 3, and the SOPs are DDBUS2 ~ 4. . .Then I connected all FTDI pins to J5 and J6 20-pin LaunchPad connectors on the back of AWR1243BOOST,including SPI,nreset,nerror,IRQ,SOPs,5V/3.3V VIO,and any other like what the FT4232H on the mmwave-devpack did.

    3.I ran mmwave_example_nonos.exe,and it shows the error I mentioned above(also tried mmwave_example and mmwave_monitoring)

    Regards,

    Junzhe

  • Hello Junzhe,

    Have you used the FTDI drivers we have provided? These are available in the mmwave studio package, under the FTDI folder.

    Regards,

    Vivek

  • Hi,Vivek

    Thank you for your reply. 

    I'm using the FTDI drivers provided by FTDI downloaded from their webpage,are they different from ones TI provided?

    Regards,

    Junzhe

  • Hello Junzhe,

    You need to define the FTDI port usage for SPI, GPIO etc. So the inf file should have the configuration accordingly. Please the package available in the mmwave studio .

    Regards,

    Vivek

  • Hi,Vivek

    Thank you for your reply. 

    I've tried delete FTDI drivers and update them to ones mmwave-studio 02_00_00_02 provided. Devices are listed like this

    But when I ran mmwave example,it still showed mmwave device is not connected like this:

    Regards,

    Junzhe

  • Hello Junzhe,

    if you are using the DFP example then the FTDI ID also needs to be set to what the library is looking for. This can be done by flashing the attached xml to the FTDI using the FT prog tool available on the FTDI website.

    Regards,
    Vivek

      

    <?xml version="1.0" encoding="utf-16"?>
    <FT_EEPROM>
      <Chip_Details>
        <Type>FT4232H</Type>
      </Chip_Details>
      <USB_Device_Descriptor>
        <VID_PID>2</VID_PID>
        <idVendor>0451</idVendor>
        <idProduct>FD03</idProduct>
        <bcdUSB>USB 2.0</bcdUSB>
      </USB_Device_Descriptor>
      <USB_Config_Descriptor>
        <bmAttributes>
          <RemoteWakeupEnabled>false</RemoteWakeupEnabled>
          <SelfPowered>false</SelfPowered>
          <BusPowered>true</BusPowered>
        </bmAttributes>
        <IOpullDown>false</IOpullDown>
        <MaxPower>100</MaxPower>
      </USB_Config_Descriptor>
      <USB_String_Descriptors>
        <Manufacturer>FTDI</Manufacturer>
        <Product_Description>AR-DevPack-EVM-012</Product_Description>
        <SerialNumber_Enabled>true</SerialNumber_Enabled>
        <SerialNumber />
        <SerialNumberPrefix>FT</SerialNumberPrefix>
        <SerialNumber_AutoGenerate>true</SerialNumber_AutoGenerate>
      </USB_String_Descriptors>
      <Hardware_Specific>
        <TPRDRV>0</TPRDRV>
        <Port_A>
          <VCP>true</VCP>
          <D2XX>false</D2XX>
          <RI_RS485>false</RI_RS485>
        </Port_A>
        <Port_B>
          <VCP>true</VCP>
          <D2XX>false</D2XX>
          <RI_RS485>false</RI_RS485>
        </Port_B>
        <Port_C>
          <VCP>true</VCP>
          <D2XX>false</D2XX>
          <RI_RS485>false</RI_RS485>
        </Port_C>
        <Port_D>
          <VCP>true</VCP>
          <D2XX>false</D2XX>
          <RI_RS485>false</RI_RS485>
        </Port_D>
        <IO_Pins>
          <Group_A>
            <SlowSlew>false</SlowSlew>
            <Schmitt>false</Schmitt>
            <Drive>4mA</Drive>
          </Group_A>
          <Group_B>
            <SlowSlew>false</SlowSlew>
            <Schmitt>false</Schmitt>
            <Drive>4mA</Drive>
          </Group_B>
          <Group_C>
            <SlowSlew>false</SlowSlew>
            <Schmitt>false</Schmitt>
            <Drive>4mA</Drive>
          </Group_C>
          <Group_D>
            <SlowSlew>false</SlowSlew>
            <Schmitt>false</Schmitt>
            <Drive>4mA</Drive>
          </Group_D>
        </IO_Pins>
      </Hardware_Specific>
    </FT_EEPROM>