You don't need any additional library. Virtual EEPROM is in STM32 core and it's written to work like standard Arduino EEPROM library: https://www.arduino.cc/en/Reference/EEPROM
For variables/objects bigger than 1B (8b) you need to use put()/get() methods.
write() / read() work only for 1B of data.
Search found 505 matches
- Mon Jan 10, 2022 9:17 pm
- Forum: General discussion
- Topic: FlashStorage STM32 - How to save, update and read data for beginner
- Replies: 3
- Views: 15390
- Wed Jan 05, 2022 7:58 pm
- Forum: STM32 HID bootloader
- Topic: This HID bootloader does not load the Arduino sketch, why
- Replies: 13
- Views: 46424
Re: This HID bootloader does not load the Arduino sketch, why
If you do not enable CDC or HID for USB then it will be unrecognizable because you haven't put any USB support in the program.
To fully use HID bootloader you need to enable CDC so your board will be recognized as a COM port.
Without CDC support you need to manually reset board into bootloader.
To fully use HID bootloader you need to enable CDC so your board will be recognized as a COM port.
Without CDC support you need to manually reset board into bootloader.
- Sun Jan 02, 2022 11:29 am
- Forum: General discussion
- Topic: GPIO analog not working
- Replies: 5
- Views: 4018
Re: GPIO analog not working
First, MCU datasheet is your friend.
There you have all information, and it clearly specifies which pins are ADC input: PA0-PA7, PB0-PB1, PC0-PC5.
Analog, doesn't mean ADC. There are analog comparators, analog outputs (DAC), OPAMPS, and probably more.
There you have all information, and it clearly specifies which pins are ADC input: PA0-PA7, PB0-PB1, PC0-PC5.
Analog, doesn't mean ADC. There are analog comparators, analog outputs (DAC), OPAMPS, and probably more.
- Sat Jan 01, 2022 9:59 pm
- Forum: General discussion
- Topic: GPIO analog not working
- Replies: 5
- Views: 4018
Re: GPIO analog not working
So it's working fine.
PB4 is not an ADC input on L433.
PB4 is not an ADC input on L433.
- Wed Dec 29, 2021 5:48 pm
- Forum: General discussion
- Topic: Serial communication not working unless Serial monitor is opened/closed
- Replies: 24
- Views: 18324
Re: Serial communication not working unless Serial monitor is opened/closed
select HID for your keyboard
Ok, so that would mean using 2 USB cables wouldn't it? Or could I use dongle to do both the HID part, and the serial? I'll give that a go and see what happens :D
Yes, it means using 2 USB cables.
For now, there's no easy way of using keyboard and serial on USB ...
- Wed Dec 29, 2021 5:31 pm
- Forum: General discussion
- Topic: Serial communication not working unless Serial monitor is opened/closed
- Replies: 24
- Views: 18324
Re: Serial communication not working unless Serial monitor is opened/closed
So, is it at all possible to edit some of the core files to make this happen? It would appear that I need to set the board to HID so that I can make use of the Keyboard.h library, so what core file to I need to edit? What do I need to look for within that file?
It is possible, but it's much ...
- Tue Dec 28, 2021 4:52 pm
- Forum: General discussion
- Topic: Serial communication not working unless Serial monitor is opened/closed
- Replies: 24
- Views: 18324
Re: Serial communication not working unless Serial monitor is opened/closed
No. For serial communication you need CDC mode set and for keyboard you need HID. You cannot have both.
So you'll need to use UART and TTL/USB converter if you want keyboard functionality.
So you'll need to use UART and TTL/USB converter if you want keyboard functionality.
- Mon Dec 27, 2021 7:59 pm
- Forum: General discussion
- Topic: Serial communication not working unless Serial monitor is opened/closed
- Replies: 24
- Views: 18324
Re: Serial communication not working unless Serial monitor is opened/closed
I have no problems with USB Serial but you need to initiate it properly (open COM port) in your program on PC, otherwise it won't work.
And in your case it looks like you haven't done it properly, otherwise you wouldn't been able to open serial monitor.
COM ports cannot be shared, so only one ...
And in your case it looks like you haven't done it properly, otherwise you wouldn't been able to open serial monitor.
COM ports cannot be shared, so only one ...
- Mon Dec 27, 2021 5:51 pm
- Forum: General discussion
- Topic: Sending Keyboard.h to Serial1
- Replies: 5
- Views: 3163
Re: Sending Keyboard.h to Serial1
If you need open Serial monitor at start, then program is written like this.
With USB you can check if connection is active (e.g. serial monitor opened and connected). It's often done in setup() and ppl often put there also a while loop to wait for serial monitor to connect:
while( !Serial ...
With USB you can check if connection is active (e.g. serial monitor opened and connected). It's often done in setup() and ppl often put there also a while loop to wait for serial monitor to connect:
while( !Serial ...
- Sun Dec 26, 2021 11:57 pm
- Forum: General discussion
- Topic: Sending Keyboard.h to Serial1
- Replies: 5
- Views: 3163
Re: Sending Keyboard.h to Serial1
Keyboard works only on USB as it's an USB device.