[chaaalyy]

Thanks for the Bugfix 🙂

I will try, as soon, as possible and report the results, when the “theoretical trial period” has expired within the fully activated Software.

Regards, Charly

[chaaalyy]

Thank you for the Information 🙂

I think, i can wait until the BSP gets released. Until now i work with MBed and imported the BSP-Part (not HAL and/or LL…) manually. Especially, when working with SD-Card on the stm32f746-Disco, i ran into many Problems, using DMA instead of Polling Mode. So i had to rework some Parts of the HAL Libs as well, as some MBed Files. My actual BSP-Files from FW 1.8.0 (stm32f7xx_discovery_xx.x) also contain some Bugfixes / Workarounds, which are more or less fixed in the new FW (1.9.0).

The most interesting Part in MBed would be the new “LittleFS” and it´s wear leveling abilities. But until the new ST Lib(FW 1.9.0) is not integrated in MBed too, i fear, the problems of 1.8.0 still remain.

To be honest: I´m just too lazy to do all that work manually just to reinvent the wheel shortly before a “professional” rework is available 😉

[chaaalyy]

Hi 🙂

I´m just curious… What do you mean with “using STM32 HAL to erase Sectors…” ?

I also work on the stm32f756-Disco and for debugging i just use the OpenOCD-Stuff provided with VisualGDB. St-Link v2.1, Frequency at 2000 and i just program, when rebuilt since last Load. Works perfectly out of the Box for me 🙂 Of course, also the whole Flash Memory gets completely erased, before reprogramming.

The resulting command Line (under VisualGDB-Settings -> Debug Settings, when opening “advanced Settings” )is:

-f interface/stlink-v2-1.cfg -f target/stm32f7x.cfg -c init -c “reset init”

Startup GDB Commands are:

set remotetimeout 60
target remote :$$SYS:GDB_PORT$$
mon halt
mon reset init
load

Regards, Charly

[Author]

Posts