STM32L0538-DISCO Demo program

[Daitec.1]

I recently bought the STM32L0538-DISCO board. I have seen the following video in youtube where you can see the functions of this board in full. Where can I find the source code for STM32Cube?

On the info page of the board I have not found one that works for STM32Cube.

Thank you very much

[Tesla DeLorean]

The materials might well predate the auto-generated stuff.

The CubeL0 directories should have project files for assorted tools (KEIL, IAR), with applications and demos under the board's directory.

STM32Cube_FW_L0_V1.11.3\Projects\32L0538DISCOVERY\Demonstrations\readme.txt

[Daitec.1]

In the D:\ST\en.stm32cubel0_v1-12-0\STM32Cube_FW_L0_V1.12.0\Projects\32L0538DISCOVERY\Demonstrations\ directory I find a project. This I can import and compile with the Cube without error, but I load it and it doesn't do anything.

I have previously made a bilnk program and it works without problem. If I load the demo project, it loads without error, but it never overwrites the blink project. It's very strange.

[Tesla DeLorean]

You could try debugging it, or use the free Keil licence.

I'd suspect the issue with importation relates to the linker script, or GNU/GCC specifics. Precompiled .HEX files are provided.

[S.Ma]

Check the board user manual for revisions. Maybe BOM has changed without Demo SW update and may not be working anymore. Not all components in a disco have the same longevity or SW compatibility.

[Daitec.1]

I have managed to compile and load the demo project, both with the Cube and Keil. The result is the same, the two leds blink, the screen shows nothing and the buttons and the touch do not react.

A demo and evaluation kit is not supposed to have these problems.

[Daitec.1]

Finally I have contacted ST directly and they have confirmed that they have changed components and that they have not modified the project.

I have been told to contact the manufacturers by and adapt the code myself. Thing that I see inadmissible because for that you buy a plate with the ST support behind.

I have contacted one of the manufacturers and the code and documentation they have provided is terrible.

[SStew]

Do you know what components changed? I have two brand new boards with the same problem, even when downloading the demo binary.

I found a newer version of the user manual that includes board revisions (we have B-03):

Board revision history: MB1143 revision B-03 The revision B-03 of the MB1143 board corresponds to:

• E-paper display U4 replaced with impact on firmware

• Several part references updated due to obsolescence (such as transistors or others, see bill of materials for details)

Board known limitations: Revision B-03

• No demonstration software is provided from this revision.

[Daitec.1]

Hi SStew,

It looks like they changed the screen to GDEY0213B74, but I don't have the BOM.

They told me that they updated the BSP. I'll pass you the link:

https://github.com/STMicroelectronics/STM32CubeL0/tree/master/Projects/32L0538DISCOVERY/Examples

We tested it and it gave us some problem, so we ended up discarding the demo board and continue the project on our own. A pity for the board, really.

I hope you have more patience and luck.

Best regards

[SStew]

Thank you very much for the update!

[Daitec.1]

We won't be able to resume testing the board until the middle of next year.

If you are lucky and get it up and running, let us know.

Good luck to you

[Walid ZRELLI]

Hello,

We have updated the BSP drivers to support the new GDEY0213B74 E-paper display component.

Here is the link to the BSP example that supports both E-paper display components (DEY0213B74 and GDE021A1):

• https://github.com/STMicroelectronics/STM32CubeL0/tree/master/Projects/32L0538DISCOVERY/Examples/BSP

The BSP example provides 2 project configurations:

- STM32L0538-Discovery RevB03 : Board contains the GDEY0213B74 E-paper display component.

- STM32L0538-Discovery : Board contains the GDE021A1 E-paper display component.

So, you should select the configuration to be used according to the revision of your board.

Otherwise, the demo software has not been updated. However, you can be inspired by the BSP example.

BeST Regards,

Walid

[JCard.3]

Oh, wow! I just found this thread after losing one afternoon getting the demo app working. First, the pre-compiled binaries mentioned in the documentation are nowhere to be found. Compiling the project from scratch just results in a binary that blinks LEDs but no display. This is pretty disappointing... I guess I'll think twice before buying another discovery board in the future...

[Daitec.1]

Hello JCard.3,

We had exactly the same problem as you, we lost a lot of time on something that should be working the first time. When you start testing it and nothing works, you feel a bit ripped off, that's why you buy these kind of demo boards.

I think ST is not taking good care of these products and that could be a good differentiating factor from the competition. For future projects, we are also considering if it is really worth this kind of boards.

[JCard.3]

I finally got the demo program running on a RevB03 board. :rocket:

Sharing this for my future self or for others in the same situation:

1. Clone the repo linked by @Walid ZRELLI​ : https://github.com/STMicroelectronics/STM32CubeL0.git
2. From the root of that repo: cp -r ./Drivers/BSP/Components/gdem0213b74 ./Projects/32L0538DISCOVERY/Demonstrations/SW4STM32/STM32L0538-Discovery/Drivers/BSP
3. From STM32CubeIDE, open project ./Projects/32L0538DISCOVERY/Demonstrations/SW4STM32/STM32L0538-Discovery
4. Right click project -> Properties -> C/C++ Build -> Settings -> GCC Compiler -> Preprocessor Change USE_STM32L0538_DISCO to USE_STM32L0538_DISCO_REV_B03

5. Build and flash

The dimensions of this display must be different from the original, because the GUI looks truncated but otherwise it works as documented in the readme.txt

 

[Daitec.1]

Thank you very much for sharing your work. When we can, let's look at reviving the board. :grinning_face: