cancel
Showing results for 
Search instead for 
Did you mean: 

stm32l152V8t6 pb4-lcdseg8

dhutchison1945
Associate II
Posted on May 24, 2012 at 10:56

Hi,

I'm using the emdedded stm32l lcd driver on the stm32L152V8t6 (lqfp 100pin)

 

all segments work well,but on the pb4-lcdseg8 I see a fixed voltage level(about 2.9V)

very near to the vdd voltage.

the lcd glass is ok.

or the stm32l152v8t6 has the pb4-lcdseg8 driver broken or there is an error on the datasheet.

Can someone confirm me that this pin is working as lcd seg driver ?

the following is the port initialization:

/* GPIO PB4 LCDSEG8 */

GPIO_InitStructure.

GPIO_Pin

= GPIO_Pin_4;

GPIO_InitStructure.

GPIO_Mode

=

GPIO_Mode_AF

;

GPIO_Init(GPIOB, &GPIO_InitStructure);

GPIO_PinAFConfig(GPIOB, GPIO_PinSource4,GPIO_AF_LCD) ;

Thanks in advance

5 REPLIES 5
Posted on May 24, 2012 at 11:26

Probably more dependent on the board, on the STM32L152-EVAL it is jumpered either between the JTAG and LDR via JP10

I'll take a peek at the jumper if I get a chance.

RCC_AHBPeriphClockCmd(RCC_AHBPeriph_GPIOB, ENABLE);
GPIO_PinAFConfig(GPIOB, GPIO_PinSource4, GPIO_AF_LCD);
GPIO_InitStructure.GPIO_Pin = GPIO_Pin_4;
GPIO_InitStructure.GPIO_Speed = GPIO_Speed_40MHz;
GPIO_InitStructure.GPIO_Mode = GPIO_Mode_AF;
GPIO_InitStructure.GPIO_OType = GPIO_OType_PP;
GPIO_InitStructure.GPIO_PuPd = GPIO_PuPd_NOPULL;
GPIO_Init(GPIOB, &GPIO_InitStructure);

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
dhutchison1945
Associate II
Posted on May 24, 2012 at 11:47

Good morning Mr. Clive1,

Thanks in advance for the fast reply.I'm using an empty prototype board without connections on the gpio pins.

I tried also to configure the port as input pu-pd or output pp-od,I moved the output state high or low, but I always see about 2.9V.

I will try to use another free segment driver or I will replace the mcu.may be that this port is broken(I agree,strange but possible)

I don't think that is an issue related to an old library release that I'm using (1.0.0) I hope.

regards,

spectre

Posted on May 24, 2012 at 12:39

I don't think that is an issue related to an old library release that I'm using (1.0.0) I hope.

 

Merging to V1.1.1 wouldn't take much time would it? A quick diff would at least highlight if much had changed

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
dhutchison1945
Associate II
Posted on May 24, 2012 at 13:29

I did a comparison on the gpio.c and on the gpio.h,I don't see differences for the package I'm using.So I'll replace the mcu with a working one.

regards

spectre

dhutchison1945
Associate II
Posted on June 15, 2012 at 14:28

Yes, I confirm you that it was a faulty(damaged) gpio port :)

regards

Spectre