UART PROBLEM ARM lpc1769

Are you making fun of us?

Did you think your code looked good? No indentation?

Do you _really_ write code looking like:

if (nn==280) { break;

}

Not even:

if (nn==280) {
    break;
}

Or did you just copied the already broken code (resulting from you not caring about my first post suggesting how to post source code) and reposted it again - without noticing that it still looked like a mess?

One issue with your code - having a single loop to receive all data over UART takes time. During that time, you don't service the TCP/IP stack.

You really should consider having interrupt-based UART communication that can happen concurrently with other things and then make the TCP communication when you have performed a correct transfer from the camera.

Another thing - why do you love global variables so much. The code is full of assigns to variables that are neither local or parameters to the function. Variable scope was invented because it greatly increases the readability and maintainability. Maintainability - the ability to see what code does and modify code without breaking it.

Your code don't do any error handling.

    ...
    // *** How do you know this function, that you say will send, really will send???
    transmit();//Here is a function to send the data from the camera to the computer via LAN

    return;
}

void transmit(void) {
    if (SocketStatus & SOCK_CONNECTED) {
        if(SocketStatus & SOCK_TX_BUF_RELEASED) {
            memcpy(TCP_TX_BUF,pdata,nn);
            TCPTxDataCount=nn;
            TCPTransmitTxBuffer();
            free(pdata);
        }
    }
}

Notice that transmit() have two if statements. Only if you pass them will you get into the code that seems to transmit - how is your UART code (that allocates a buffer for the incomming data) take this into account?

Start looking at the TCP/IP examples.
Then start trying to "unmess" your code a bit.
Keep track of the current state.
Make sure that functions returns error results if they may fail.
Make sure that you always check error results.
Try some debugging, to compare where you assumptions deviates from what the program actually do.

And when you post code next time - make sure it does look readable.

Are you making fun of us?

Did you think your code looked good? No indentation?

Do you _really_ write code looking like:

if (nn==280) { break;

}

Not even:

if (nn==280) {
    break;
}

Or did you just copied the already broken code (resulting from you not caring about my first post suggesting how to post source code) and reposted it again - without noticing that it still looked like a mess?

One issue with your code - having a single loop to receive all data over UART takes time. During that time, you don't service the TCP/IP stack.

You really should consider having interrupt-based UART communication that can happen concurrently with other things and then make the TCP communication when you have performed a correct transfer from the camera.

Another thing - why do you love global variables so much. The code is full of assigns to variables that are neither local or parameters to the function. Variable scope was invented because it greatly increases the readability and maintainability. Maintainability - the ability to see what code does and modify code without breaking it.

Your code don't do any error handling.

    ...
    // *** How do you know this function, that you say will send, really will send???
    transmit();//Here is a function to send the data from the camera to the computer via LAN

    return;
}

void transmit(void) {
    if (SocketStatus & SOCK_CONNECTED) {
        if(SocketStatus & SOCK_TX_BUF_RELEASED) {
            memcpy(TCP_TX_BUF,pdata,nn);
            TCPTxDataCount=nn;
            TCPTransmitTxBuffer();
            free(pdata);
        }
    }
}

Notice that transmit() have two if statements. Only if you pass them will you get into the code that seems to transmit - how is your UART code (that allocates a buffer for the incomming data) take this into account?

Start looking at the TCP/IP examples.
Then start trying to "unmess" your code a bit.
Keep track of the current state.
Make sure that functions returns error results if they may fail.
Make sure that you always check error results.
Try some debugging, to compare where you assumptions deviates from what the program actually do.

And when you post code next time - make sure it does look readable.

what is wrong in the code

global_temp1 = multiptr2_init1; route1(); DVAorIP2(); decode2bytes(); changesoutput1(); global_temp1 = configpm[glbtmpvar]; PORTD = ' '; if (multiptr2_init1<17) { PORTD = 'b'; if (multiptr2_init1 & 0x01) { PORTD = 'a'; } } ASCII_TO_LCD(); PORTD = 0xC9; dis(); J_num = 16; second_name(); PORTD = 0xDC; dis(); decode2bytes(); PORTD = 0xE1; dis(); changesoutput2(); global_temp2 = configpm[glbtmpvar]; if (multiptr2_init1 & 0x01) { global_temp1 = global_temp2 >> 4; } else { global_temp1 = global_temp2 & 0x0F; } decode2bytes(); } else if (screen_num == 26)

Dear all (helpers),

Please stop paying attention to this thread. You are genuinely wasting your time...

Thanks for the reply
..updates questions