• State TI Thinks Resolved
  • Locked Locked
  • Replies 21 replies
  • Answers 7 answers
  • Subscribers 33 subscribers
  • Views 422 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IWR6843ISK: Start Chirp digital pulse

Larry Koudele
Intellectual 310 points
Part Number: IWR6843ISK
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Guys,

I have asked for a signal that shows me a Start Chirp pulse.  After looking at the 6843 spec, this signal can be outputted on the BGA ball N8, K13, or P9 just by setting up a mux register properly.

It appears to me the MSS binary does this.  I have no way to easily write or understand how to make this binary code.  From looking at the hardware, the easiest place to look at this signal is the K13 ball.  It is 

currently configured as GPIO-2 I think.  I can get to that place easily.  Any idea how to get a version of MSS code that configures this ball, or one of the others for me.  The spec tells exactly what mux address to 

use, and what configuration to set it to.  

Here is a screen shot of the spec where this is identified:  

Notice on the far left, ball K13.  Going right, all parameters to make it output Start Chirp are there.  

Can someone help me on how to get this done.  If that is a bad ball to use, as stated above, N8 and P9 can also output that signal.

Thanks!

Larry

  • 0
    TI__Mastermind 21231 points

    Hi Larry, 

    We are looking int your question and will get back to you soon. Thank you for your patience. 

    Best regards,

    Josh

  • 0 in reply to Josh Dye
    TI__Mastermind 19840 points

    Hello Larry.

    You can find examples of this in the mss_main.c file for the 6843 out of box demo.  Please see the snippet below for an example to do the pinmux configuration.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Thanks, but when I look for that file, there is no source code for 6843ISK, only for 6843ODS.  However, even if I had the correct source code, you mean I must modify the code (I guess in the include file "pinmux") and then compile the c code to a binary to then download to the part?  That is beyond my normal skill level.  I would need a c code expert to do all that.  What I need is a simple external test program to modify the mux register, maybe using teraterm?  Does that exist? If not, I will need help in doing the c code mod.  I did look at the pinmux.h file.  It looks like even though there is a mux address and configuration for the BGA ball I want to mux the signal out on, this include file stops before the Start Chirp pulse is identified.   Hmmm.  Could anyone there compile the c code for me, and give me the binary?   

    Thanks,

    Larry

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Hello.

    That code that I provided a snippet of is not ODS or ISK specific, it is generic to the 68xx platform.  All you need to do is switch out the pin mux addresses for the pins you want which are provided in the datasheet and TRM.  However, we have projects that import all the required software based on the EVM/device variant, and we have some resources in the toolbox for how to import a project and build a project in CCS, so you can make these modifications and compile your own binary.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Santosh,

    Sorry for the late reply.  I found in the mss_main.c code, some of the pinmux settings.  However, when I look at the pin N8, which is defined as MCU_CLKOUT, i cannot find where this BGA ball is setup.  However, if I scope it (N8) during running mmWave Studio, I see a 20 Mhz clock.  I tried adding code in the mss_main.c that changes the N8 to put out Start_Chirp instead, but after compiling the code and running it, the same clock remains.  For now, I just need to find where in the code N8 is set up to output the MCU_CLKOUT.  Help!

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Hello Larry.

    Please see the attached code from the pinmux_xwr68xx.h file.  You just use the SOC_XWR68XX_PINN8_PADAY and the SOC_XWR68XX_PINN8_PADAY_MCU_CLKOUT in the Pinmux_FuncOverride function in the mss_main.c code.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Santosh,

    I had already found the PINN8 in the pinmux_xwr68xx.h file.  I cannot find any programming of that PINN8 in the mss_main.c code  It doesn't exist in that code using CSS find.  What line do you see it in?  When running mmWaveStudio, the clock turns on when just after I load the xwr68xx_masterss download code.  Where can I find the source code of that?  It must be in there, because it's not in mss_main.c.  Thanks. 

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Hello Larry.

    You will have to add it in yourself.  You can copy the examples for other pins in the mss_main.c code in platformInit() and replace the values with the Pin N8 values.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Santosh,

    I did add it myself in the mss_main.c code.  I made an addition for the PINN8 to send out StartChirp.  Then I compiled it, and nothing changed.  The 20 Mhz clock was still there.  I need to know where that 20 Mhz clock is setup in the first place.  Thanks.  

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Larry,

    Apologies for the confusion, I thought you wanted the MCU_CLKOUT to be pinmuxed to that ball.  If you want the chirp start, you should program the value 2 instead of SOC_XWR68XX_PINN8_PADAY_MCU_CLKOUT.  You can refer to the datasheet to know which mode value needs to be set for what output.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Santosh,

    I already did exactly what you just said above to pinmux N8 to send Chirp_Start  out instead of MCU_CLKOUT out.  The mode value for Chirp_Start is 2U.  However, after doing that, compiling and loading the code into the part, MCU_CLKOUT was still there.  So, please help me here.  I need to find the actual code that sets up N8 to send the MCU_CLKOUT.  I can then modify that code.   It is not in mss_main.c.   So where is it?  I need the source code to modify.  

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Larry,

    It is not something that is configured by default in the out of box demo.  You will need to add SW to enable this pin.  Can you share the exact snippet of code that you have added to your code so that I can take a look?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points
     In this case, I tried to configure both K13 and N8 for Chirp_Start.  Neither came out.  I did setup the Chirp_Start in the pinmux.h file first.  It recognized the new Chirp_Start values in both cases.  You can see I made a note LJK configure pin N8 on 030725 for the N8 case.  Then I compiled the code, loaded the binary into the part, and ran it.   No change.  The same clock came out.  I need to know where that clock is setup?  It is not in the mss_main.c I modified.
    * - GPIO Output: Configure pin K13 as GPIO_2 output  ljk 030725 WAS PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL
         **********************************************************************/
        Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINK13_PADAZ,PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
        Pinmux_Set_FuncSel(SOC_XWR68XX_PINK13_PADAZ, SOC_XWR68XX_PINK13_PADAZ_Chirp_Start);


    /**********************************************************************
         * Setup the PINMUX:
         * - LJK configure pin N8 for Start Chirp 030725
         **********************************************************************/
        Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINN8_PADAY,PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
        Pinmux_Set_FuncSel(SOC_XWR68XX_PINN8_PADAY, SOC_XWR68XX_PINN8_PADAY_Chirp_Start);




        /**********************************************************************
         * Setup the PINMUX:
         * - for QSPI Flash
         **********************************************************************/
        Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINR12_PADAP, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
        Pinmux_Set_FuncSel(SOC_XWR68XX_PINR12_PADAP, SOC_XWR68XX_PINR12_PADAP_QSPI_CLK);
  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Hello.

    I am looking into this and will provide a response by the end of the day tomorrow.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Mastermind 19840 points

    Hello Larry.

    Larry Koudele said:
    SOC_XWR68XX_PINN8_PADAY_Chirp_Start

    Is this value set to 2?  Moreover, if you are modifying the pinmux_xwr68xx.h file, you will need to rebuild the pinmux driver library and then rebuild your project for the changes to take place.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Santosh,

    Yes, prior to changing the code in mss_main.c to add the code SOC_XWR68XX_PINN8_PADAY_Chirp_Start, I did also modify the pinmux_xwr68xx.h file so that Chirp_Start is recognized and set to the value 2.  Where is the pinmux driver library?  

    Thanks,

    Larry

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    It is in SDK 3.6.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    I am not a C code guy, so I'll need a little more info on the library driver.  Is is a .c code file, or a .h file, or what?  Note that I modified two files already, the mss_main.c file (adding N8 stuff) and the pinmux.h file (adding the Chirp_Start and value).  I need to change another file I think you are saying.  What is the exact name of that file?  Thanks!  

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Hello.

    You do not have to modify anything else.  First, navigate to mmwave_sdk_03_06_02_00-LTS\packages\scripts\windows and run the setenv.bat file.  Then, in the same terminal window, navigate to mmwave_sdk_03_06_02_00-LTS\packages\ti\drivers\pinmux and run gmake drv or gmake all to rebuild the driver.  Then rebuild your project(you will need to rebuild as opposed to normally build) for the changes to take effect.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 310 points

    Santosh,

    I followed all your directions.  After doing the rebuild, I found the correct new .bin file, loaded it into the part using Uniflash, then ran mmWave Studio.  Again, the 20 Mhz clock was on ball N8 (R62 on the 6843ISK board).  No change.  I am at a loss.  I think the problem is that I have never found where N8 is first configured.  I just added the a new configuration for N8 (as I showed you) to the mss_main.c file, and the pinmux_xwr68xx.h file.  Then did all the other stuff you told me to do, and no change.  If I can find where the N8 is configured, that is the key now.  Thanks.

    /Larry

  • 0 in reply to Larry Koudele
    TI__Mastermind 19840 points

    Hello Larry.

    As I stated earlier, N8 is not normally configured by default in our OOB demo, so it something you will have to add in manually.  However, could you show me the output from when you tried to rebuild the pinmux library?  I just want to confirm that it successfully built, and then you rebuilt your out of box demo code in CCS.

    Sincerely,

    Santosh