HY-LPC1788 GPIO Problem

Have you asked HAOYU Electronics ?

Why would that be necessary? It's highly unlikely to be the board at fault.

And it's obviously not the coder.

More likely to be the alignment of the planets.

Like to try to help but am a little afraid to download the code.

P3[0] to P3[31] I/O Port 3: Port 3 is a 32-bit I/O port with individual direction controls for each
bit. The operation of port 3 pins depends upon the pin function selected via
the pin connect block. Pins 0 through 24, and 27 through 31 of this port are
not available.

P2[13] / EINT3 /
I2STX_SDA
50 - I/O P2[13] — General purpose digital input/output pin. 5 V tolerant pad with 5
ns glitch filter providing digital I/O functions with TTL levels and hysteresis.
I EINT3 — External interrupt 3 input.
I/O I2STX_SDA — Transmit data. It is driven by the transmitter and read by
the receiver. Corresponds to the signal SD in the I2S bus specification.

I would say there are only about 14 P2 pins nothing greater than P2[13]
and Onl a few P3 pins can be used looks like P3(25) may only be available.

UM10360
Chapter 7: LPC17xx Pin configuration

Hello again and thank you for your Help.
yes i read the "UM10470" first .
Pin 81 is P2.21 [on Board Red LED]
pin 195 is p3.22
this is my code ....

    int main(void)
    {
    PINSEL_ConfigPin(0,21,0);
    PINSEL_ConfigPin(2,21,0); //on Board red LED
    PINSEL_ConfigPin(3,17,0);
    PINSEL_ConfigPin(3,21,0);
    PINSEL_ConfigPin(2,15,0);
    GPIO_SetDir ( 0 , (1<<21) , 1) ;
    GPIO_SetDir ( 2 , (1<<21) , 1) ; //on Board red LED
    GPIO_SetDir ( 3 , (1<<17) , 1) ;
    GPIO_SetDir ( 3 , (1<<21) , 1) ;
    GPIO_SetDir ( 2 , (1<<15) , 1) ;
    while(1)
    {
    FIO_SetValue( 0 , (1<<21));
    FIO_SetValue( 2 , (1<<21)); //on Board red LED
    FIO_SetValue( 3 , (1<<17));
    FIO_SetValue( 3 , (1<<21));
    FIO_SetValue( 2 , (1<<15));
    Delay(0xfffff);
    FIO_ClearValue( 0 ,(1<< 21) ) ;
    FIO_ClearValue( 2 ,(1<< 21) ) ; //on Board red LED
    FIO_ClearValue( 3 ,(1<< 17) ) ;
    FIO_ClearValue( 3 ,(1<< 21) ) ;
    FIO_ClearValue( 2 ,(1<< 15) ) ;
    Delay(0xfffff);
    };
    }

.
P2.15 Blinking
P2.21 Blinking
P0.21 Remain High without any change
P3.17 Remain Low without any change
P3.21 Remain High without any change

But you still haven't posted any indication that you have read the schematics and verified if there are external hardware connected to "problematic" pins.

The photos of the board linked above - which you haven't confirmed is the correct board - shows headers for P1 and P2. But I don't see any headers for P0 or P3. Only by reading the schematics would you know if the board manufacturer intends you to be able to play with the pins you are having troubles with. I notified you about this in my first post - but all you have returned back with is defending the use of the pin that controls the red LED - a pin that you do not have problems with...

I didn't see anything colliding with P0.21.

But P3.17 and P3.21 are data lines, and needed when interfacing with K4M563233G/K4M513233E. Are you really sure you should try to play with them as GPIO outputs, when they are in some situations driven by other chips? Exactly why did you select these pins to try to "blink"?

yes about the Port3 you right .
according to the schematic the P3.17 and P3.21 connected to the K4M563233G But what about the P0.21 ?
P0[21] — General purpose digital input/output pin see Page 92 at "UM10470".
and Dude you can find P0.21 in "HY-LPC1788-Core_SCH.pdf" by searching P0.21.

looks like P0.21 is wired to pin 57 of P2 from your schematic. What test equipment are you using
to see the signal on pin 57 of P2 connector. Maybe it is difficult to see the toggle using
a Digital Voltage meter.

according to the code ... I Think because of similar function of P2.21 and P0.21, The blinking of the Pins can be seen by eyes and Voltmeter.
I tested the code and only P2.15 and P2.21 blinking. :|
* I increased the Delay time for sure.