Stuck in NAIrqHandler()

Embedded Devices NET+OS
1

Hi,

I have a problem with my NET+OS 7.3 project (my first one) on ConnectME:

My code never get out of an NAIrqHandler(), and I don’t know the reason. My app do the following :

  • Configure serial port B as dialog port instead of port A, which I use to communicate with another uC.
  • Start another thread (I don’t know if I can use the root thread for all my stuff, but as every example seem to use thread, so did I) who will use serial to poll data from the other uC and toggle some GPIO pin through NAsetGPIOpin().

As I didn’t configure anything particuliar for the interrupt, I don’t undestant which interrupt cause the problem. Can the GPIO things or serial communication be the cause?

Any help realy welcomed !
And if need more information is need, just tell it :slight_smile:

2

update :

After some research, I found that my problem come from the DCD line of the UART.
I use the UART in two wire mode (only tx-rx) by defining BSP_GPIO_MUX_SERIAL_A to BSP_GPIO_MUX_SERIAL_2_WIRE_UART in gpio.h.
I use the GPIO0 (DCD) for controling a reset line by defining BSP_GPIO_INITIAL_STATE_PIN_A0 to BSP_GPIO_INITIAL_STATE_OUTPUT_DRIVER_LOGIC1. But it seem that the pull up on this line make the UART interrupt because of a break condition. Does anyone know how to desactivate this behaviour ?

3

I got a problem looking very similar (output GPIO not working as it would be).
I resolved it setting explicitly the GPIO level with NasetGPIOpin(). I got doubt on the fact that the INITIAL_OUTPUT_STATE is taken in account.

let to know if it helps.

Colin