An issue with p2.6 in msp430f2013.

I'm sorry but I'm really struggling to solve this problem.  I dont see a solution

Thanks

Are you sure P2.6 is not driven by something other than the F2012? Try the following code:

void main(void)
{
  WDTCTL = WDTPW | WDTHOLD;
  P2SEL = 0;
  While (1) {}
}

Is P2.6 high or low?
If high, temporally pull it low with a 1K resistor. Any change?
If low, temporally pull it high with a 1K resistor. Any change?

p2.6 is high or to be more accurate 3V

when i pull it to high with 3k its level becomes 1V;

It looks like something other than the F2013 is driving P2.6 high. You need to check your circuit board and other component to find out what went wrong before you can program F2013 to drive P2.6..

I unsoldered the chip to find out is there still a high voltage level. But there is no voltage without MCU. So MCU drives it

Alexandr Vaigachev said:

I unsoldered the chip to find out is there still a high voltage level. But there is no voltage without MCU. So MCU drives it

 Hi, your code is in a picture but I see you are enabling interrupt before initializing registers. No interrupt source is selected but a spurious one can be in place locking your code.

 Try comment out _interrupt enable clause and recompile to see if code run to toggling while, from scope image I see it can be oscillating free run with watchdog jitter superimposed.

 On interrrupt service at almost clear P2IFG, from your listing IFG is set, IE is not set so no interrupt are from otherwise this service trap CPU: it execute IRQ then reenter just after returning due flag still are set.

Are the DE and RE pins of the ADM3485 left floating in your board? I could not find any truth table in the data sheet of ADM3485 for the condition where DE and RE are floating. P2.6 seems to be connected to the DI of this chip and just wanted to ensure that nothing went wrong because the DE and RE are floating.

Rakesh

To eleminate any interference from ADM3485 I unsolderded it too.But there is still high voltage on this pin. (to say in other words writing to p2.6out doesnt affect the state of the pin)

I have not checked yet what  Roberto Romano suggested and I think that there is a clue.

Alexandr Vaigachev said:

I have not checked yet what  Roberto Romano suggested and I think that there is a clue.

 Also try the simnplest code suggested by OCY, it can isolate all trouble from code or hardware.