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.
Tool/software:
I'm trying to use GIOB[2] as an output on pin 38 (100 pin PZ package), but it doesn't seem to work. HALcoGen will provide code based on using it as an output but the pin remains in a high state.
Hi Scott,
Can you please refer below thread once:
And i also noticed if i enable below check box in special muxing:
Then i could see that GIOB_2 functionality enable on the pin 38:
But i don't have this board to test actual functionality, can you please test it from your end once?
--
Thanks & regards,
Jagdish.
Hi Jagdish,
I tried your suggestion. It changed one line in pinmux.c from;
PINMUX_GIOB_DISABLE_HET2_ENABLE(OFF);
...to;
PINMUX_GIOB_DISABLE_HET2_ENABLE(ON);
...but otherwise, pin38 remains high at all times.
I have also tried mapping it to AD2EVT and forcing the EVT pin low with adcSetEVTPin(adcREG2, 0) but that also fails. It seems like pin 38 is only an input (pulled high) and not capable of being an output.
Thanks,
Scott
I'm giving up on this. It just doesn't seem possible to make pin 38 an output no matter what pinmux settings I use. I've had our technician blob solder between pins 38 and 37 and now I can use N2HET[31] instead. That works.
TI should be looking in to this, both documentation and HALcoGen. I see lots of issues with GPIOB[2] in other packages and Hercules parts being discussed in this forum, and it's obvious that there some issue common across all the parts.
Thanks,
Scott
Hi Scott,
I'm giving up on this. It just doesn't seem possible to make pin 38 an output no matter what pinmux settings I use. I've had our technician blob solder between pins 38 and 37 and now I can use N2HET[31] instead. That works.
I don't have this board to test and provide an example project, even i had RM42x board but it doesn't have GIOB[2].
Can you do one thing, we can also use MIBSPI pins as GIO, i could see this pin has MIBSPI functionality and you can find this procedure in below FAQ. Can you try to configure it in MIBSPI functionality and can you try to use it as GIO?
If you face any difficulty in doing this, then let's setup one live debugging session to guide you.
--
Thanks & regards,
Jagadish.
Hi Jagdish,
That did appear to solve my problem. I can now drive pin 38 as GIO. As I had mentioned in my earlier post, I had tried something similar by mapping pin 38 to AD2EVT but that attempt was unsuccessful. According to the manual, MIBSPI3nCS[0] is actually the default pin muxing -- is it that the pin only connects to MibSPI3 and no other peripheral?
Thanks for your help,
Scott
Hi Scott,
s it that the pin only connects to MibSPI3 and no other peripheral?
This pin does have other functionalities like AD2EVT (ADC2 Event Trigger) and EQEP1I (Enhanced QEP1 Index) functionalities as well.
--
Thanks & regards,
Jagadish.
Yes, I realise that pin 38 has other pin muxing possibilities, but as far as I can tell they don't work, certainly not when trying to use them as an output.
In any event, both the user manual and HALcoGen are incorrect in regards to the muxing capabilities of this pin. Wouldn't you agree that TI should clarify this?
Thanks,
Scott
Hi Scott,
Yes, I realise that pin 38 has other pin muxing possibilities, but as far as I can tell they don't work, certainly not when trying to use them as an output.
In any event, both the user manual and HALcoGen are incorrect in regards to the muxing capabilities of this pin. Wouldn't you agree that TI should clarify this?
The other functionalities should also work.
As i discussed before i don't have the board to provide working examples to you.
Is it possible to setup one live debugging session from your end, i just want to verify how exactly you are trying to configure this pin.
--
Thanks & regards,
Jagadish.
Hi Scott,
I will be available from 10AM to 8PM IST (Indian Standard Time),
Based on your availability, you can setup one meeting. Let's setup a meeting on tomorrow (Friday)
--
Thanks & regards,
Jagadish.