• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 944 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.

LAUNCHXL2-RM57L: N2HET as GIO

Max Hansen
Prodigy 70 points
Part Number: LAUNCHXL2-RM57L
Other Parts Discussed in Thread: HALCOGEN

I recently got a RM57Lx LaunchPad, and have gotten the GIOA and GIOB outputs to work, but right now I'm struggling to the the N2HET to work as a GIO. As of right now, I can't use the HalCoGen software to help me with creating the code, so I'm going the register manipulation and all of that myself (using the Project 1 project from the Wiki). So far I've tried setting the HET Pin ENA in the GCR register, then set the direction to output, then set the output (I've also tried setting the appropriate bit in the PINDIS register but that didn't change anything). Then in the main loop I'm toggling the output of the pin. The result is a square wave about 40mV peak to peak on the pin. I've tried making sure that the output mux is correctly set, as well as making sure that there is power going to that domain (domain 3), and making sure that the peripherals are enabled in the PCR section. Any help to solve this would be greatly appreciated.

  • 0
    TI__Guru 68950 points
    Hmm.

    A square wave of 40mV doesn't sound right.

    Which HET pin?

    You should be able to use HalCoGen for this purpose.

    There is an API in the GIO.H/GIO.C for manipulating GIO registers, and you can pass a pointer to the HET GIO register bank to this to manipulate the HET GIO registers. In HalCoGen you can initialize the GIO on HET.

    The main thing you want to do to make it simple to start is to make sure you do not have any of the HET PWMs configured to drive the HET pin you want to toggle as GIO.

    Because with HET unlike most modules, there isn't a 'switch' between GIO mode or functional mode.
    So you can set/clear a pin through the GIO register and software, and the HET can immediately flip the pin the other way if that is what the HET program is designed to do.

    It's not so straigtforward in HalCoGen to keep the HET program from running so best to point the PWMs onto different pins so you don't have the CPU code competing w. the HET program for your experiment.

    Also check the PINMUX tab in HalCoGen to make sure that the HET signal is selected for the correct BGA Ball # that you are using.

    You will have to trace the connector back to the BGA ball with the warning that sometimes signals can come from two different balls.

    So:
    - find pin # of header/connector you are looking at.
    - find net name in LaunchPad Schematic
    - find out which ball on the BGA that net name connects too
    - knowing the ball # ... look at that ball on the PINMUX tab in HalCoGen and make sure
    you have the HET selected to drive it
    (unless HET is in the left most column where it is the 'default' then it doesn't need to be
    explicitly selected in the HalCoGen GUI).
  • 0 in reply to Anthony F. Seely
    Prodigy 70 points
    The 40mV I think was from when I was originally trying to get the ECLK to a pin (just noise from the clock). It was just noise being sent to the pin

    And I ended up figuring it out. It was a stupid mistake. I think that the schematic for the LaunchPad was updated, or I clicked on the wrong LaunchPad that had a slightly different name. Realized that the printed page and the PDF of the schematic that I just got I had different header labels. Anyways, changed the signal to a different pin and got it working. Just a really stupid mistake that wastes a lot of the day....

    But, it did turn out to be easy to manipulate the N2HET pins as GIOs when not using HalCoGen (can't use HalCoGen because it's not an approved software for the work that I'm doing). Just set it up like a normal GIO pin. At least there's that.

    Thanks!
    -Max