Search found 15 matches

by TwoArmsTwoLegs
Wed Jun 17, 2020 12:35 pm
Forum: General discussion
Topic: U8G2.begin() takes 2.1s to start - Is this the same for everyone else?
Replies: 3
Views: 1182

Re: U8G2.begin() takes 2.1s to start - Is this the same for everyone else?

Wow. What a pull. Outstanding advice.
back down to 1.3s with the i2c speed defined in.
Perfect. Thank you.

It makes sense to that the rest is in the library loading (as you said Ray), but the load time improved as it is is much less obtrusive.
Many thanks fpiSTM. As usual.
by TwoArmsTwoLegs
Thu Jun 11, 2020 6:03 pm
Forum: General discussion
Topic: U8G2.begin() takes 2.1s to start - Is this the same for everyone else?
Replies: 3
Views: 1182

U8G2.begin() takes 2.1s to start - Is this the same for everyone else?

HI All. I'm using the U8G2 library to run a little SH1106 screen on my STM32L07 variant board. When I turn on the board, There's a boot screen to let some internals load and some values settle. However, before the boot logo appears on the screen, there's a very uncomfortable 2.1s delay. Peppering th...
by TwoArmsTwoLegs
Fri May 08, 2020 5:01 pm
Forum: General discussion
Topic: STM32L07 Simple EEPROM read and write without the example code.
Replies: 3
Views: 1184

Re: STM32L07 Simple EEPROM read and write without the example code.

Thanks for taking a look at it man. After trying out various bits of scavenged code without success, I've got the example code snippets off the ST website. Surprisingly hard to find from google. The reference manual has a phrase to search for on the ST website which opens the secret door behind the ...
by TwoArmsTwoLegs
Thu May 07, 2020 8:45 am
Forum: General discussion
Topic: STM32L07 Simple EEPROM read and write without the example code.
Replies: 3
Views: 1184

Re: STM32L07 Simple EEPROM read and write without the example code.

I've only just realised that STM32 Cube programmer allows you to view the data from whatever memory location you like. Very useful. EEPROM address (0x08080000) is all 0s, so my suspicion that the write was going through was also wrong. No read or write protection bits seem to be set, so, back to rea...
by TwoArmsTwoLegs
Wed May 06, 2020 4:10 pm
Forum: General discussion
Topic: STM32L07 Simple EEPROM read and write without the example code.
Replies: 3
Views: 1184

STM32L07 Simple EEPROM read and write without the example code.

Hi Folks, Following on from the bug bug detailed here (https://github.com/stm32duino/Arduino_Core_STM32/issues/1016) , the example code for EEPROM read and write wont operate on the internal EEPROM, but instead on an emulated EEPROM. The advice on the bug note says that the HAL API can be used direc...
by TwoArmsTwoLegs
Tue May 05, 2020 10:17 am
Forum: General discussion
Topic: STM32L072CZ misreporting EEPROM size?
Replies: 4
Views: 1309

Re: STM32L072CZ misreporting EEPROM size?

Ah, many thanks.
Apologies for the duplicate.
by TwoArmsTwoLegs
Tue May 05, 2020 9:28 am
Forum: General discussion
Topic: STM32L072CZ misreporting EEPROM size?
Replies: 4
Views: 1309

Re: STM32L072CZ misreporting EEPROM size?

Is the EEPROM size something I have to set in CubeMX maybe? I can't find any reference to it, so I'm thinking that's not it.
by TwoArmsTwoLegs
Tue May 05, 2020 9:27 am
Forum: General discussion
Topic: STM32L072CZ misreporting EEPROM size?
Replies: 4
Views: 1309

STM32L072CZ misreporting EEPROM size?

Hi Guys, L072CZ contains 6KB onboard EEPROM. Loving all that this chip has to offer. https://www.st.com/content/st_com/en/products/microcontrollers-microprocessors/stm32-32-bit-arm-cortex-mcus/stm32-ultra-low-power-mcus/stm32l0-series/stm32l0x2/stm32l072cz.html# EEPROM.Length(); is throwing out 128....
by TwoArmsTwoLegs
Sat May 02, 2020 2:45 pm
Forum: General discussion
Topic: Some confusion around the ordering/mapping of the pins in the variant.cpp PinName array
Replies: 10
Views: 2089

Re: Some confusion around the ordering/mapping of the pins in the variant.cpp PinName array

Ah! So actually it *is* working as expected?
And for most situations I'll be addressing with pin number (PXY) not pin name (PX_Y)?

I don't know why I got it into my head that the correct way to address pins is via pin name.
Probably just unlucky with my choice of example code.

Go to advanced search