Value Line Discovery Board

I would not be able to tell just by looking, I’d have to run your whole setup on my machine to have a chance it finding the problem

Also mind the VL possess only 8kB ram..

Hi friends!
STM32 VL Discovery working fork for old Maple IDE

maxxir wrote:Hi friends!
STM32 VL Discovery working fork for old Maple IDE

Thanks to maxxir’s link, I think I have sorted out the variant except the ldscript for F100RB.
Any help on this is welcome.

Roger,
The link you provided is for the HAL version isn’t it?
How stable is the HAL version of STM32duino?

Phisatho wrote:Roger,
The link you provided is for the HAL version isn’t it?
How stable is the HAL version of STM32duino?

At last, I got the LEDs blinking.
I have not tested any other peripherals yet.
If anybody is interested, I can share the files.

Are you using the latest version from github ?

If you meant Arduino_STM32, yes.

I mean, from here

https://github.com/stm32duino

No, I did not.
I took the files from Maxxir’s link, and stitched up an ldscript using files from two different sources.

OK

Rick Kimball has the same board and did some initial tests using the new repo (modified version of STM’s own official code), and he reported that it worked OK

I’d recommend you give the official repo a try.

Instructions to install are here

viewtopic.php?f=16&t=1553

I faced a few problems with it.
1) The port-pin way of addressing is not available. Pins are addressed the Arduino way (1,2,3..).
2) Even with Pin# way, all pins are not included.
3) Some of the pins are marked as ARDUINO_PIN_EXT / GPIO_PIN_MORPHO_ONLY. I don’t know how to access these pins.
4) MAX_DIGITAL_IOS is defined as 22 which is incorrect. (actual count is 51).
5) LED_BUILTIN is defined as 13 which is incorrect. (this board has 2 LEDs – PC8 and PC9).
6) The board pins are marked in the PXYY format and it does not have the arduino way of pin labeling. Hence Port/pin way of addressing (PA1, PA2..) would make more sense.

1) The port-pin way of addressing is not available. Pins are addressed the Arduino way (1,2,3..).

When did you download the core ? The pin mapping was updated yesterday

2) Even with Pin# way, all pins are not included.
See answer to 4

3) Some of the pins are marked as ARDUINO_PIN_EXT / GPIO_PIN_MORPHO_ONLY. I don’t know how to access these pins.
See answer to 4

4) MAX_DIGITAL_IOS is defined as 22 which is incorrect. (actual count is 51).

OK. Looks like this is a mistake in both the BluePill and the Value Line, however we can’t simply change this number, because of the way Wi6Labs wrote the code it is very wasteful and puts loads of constant data into RAM, and changing that count from 22 to 51 would mean it consumes more RAM than is available in the F100

We already have an issue logged for this, but its not that easy to fix, as it requires a lot of changes to the code

5) LED_BUILTIN is defined as 13 which is incorrect. (this board has 2 LEDs – PC8 and PC9).
Easy to fix. I’ll push a fix for this now.

6) The board pins are marked in the PXYY format and it does not have the arduino way of pin labeling. Hence Port/pin way of addressing (PA1, PA2..) would make more sense.
See answer to question 1 (fixed already)

I made the variant for the legacy(?) version of STMduino – not HAL. I am yet to get a grip on the HAL version.
I downloaded only an hour ago.
I am getting the error < ‘PC9’ was not declared in this scope >

Phisatho wrote:I made the variant for the legacy(?) version of STMduino – not HAL. I am yet to get a grip on the HAL version.
I downloaded only an hour ago.
I am getting the error < ‘PC9’ was not declared in this scope >

Update.

Fixed some but not all issues in the HAL version.

I can’t fix the issue with not all pins being available at the moment as its a serious underlying problem with the STM code

Update. STM Core.

I was able to fix the MAX PINS issue because it didnt impact RAM usage as the number of analogue pins did not change, just the number of digital pins.

However it revealed that the are yet more problems with the way the analogue config is handed as you will be limited to using only 7 specific pins as analogue, which is probably not correct.

The F103C spec is for 2 ADC’s with 10 analogue channels,
F103R and F103V have 16 analogue channels

I can’t see from the spec any limitation for which pins can be used as analog, but I will post a separate question about this

RogerClark wrote:maxxir wrote:Hi friends!
STM32 VL Discovery working fork for old Maple IDE