Arduino for STM32

among the things to try, after successfully flashing through st-link, try with DFU again, maybe make some changes so as to tell that that is installed from DFU. it is quite possible the flash could be write protected. But that with st-link, there is a special means connect under reset which can ove...

if you can work with fpiSTM to do a commit for a new variant for 8 Mhz (by means of a PR pull request) do help to test that. the files that are needed to be updated are a copy of that variant file with a new name, and maybe some other source files (i'm not sure but you'd need to check), e.g. the inc...

among the things to try, after successfully flashing through st-link, try with DFU again, maybe make some changes so as to tell that that is installed from DFU. it is quite possible the flash could be write protected. But that with st-link, there is a special means connect under reset which can over...

if the stm32cube programmer messages make sense, it seem your boards are actually working, otherwise cannot even program. but the blink test not working is unusual. I rebuild a blink test with some other test usb, adc, temperature reading, whetstone benchmark etc my board is 25 mhz, I've rebuild thi...

if that doesn't work, then it is unlikely to be a clock issue, because by returning in void SystemClock_Config(), before clock setting.
it is running on its internal clock, not even on the crystal

it seem you have a few boards, all of them don't work?

Fziegler_076 wrote: ↑Sun Apr 21, 2024 2:48 am

void SystemClock_Config() {

return; // <- return on entry, so no clock setting is done

....
}

Should I do this in a sketch or fix some file?

I also bought the same boards with HSE 25 MHz today, but they will arrive no earlier than in 2 weeks.

inside that variant file

for 32k RTC crystal , i've a few times it doesn't oscillate, but normally for the HSE 8, 12, 25 mhz crystals etc, seldom have problem, so it is surprising if HSE don't oscillate, but maybe sometimes that can happen.

if you really want to get to the bottom of that, the only way seemed to be to use a st-link v2 https://www.adafruit.com/product/2548 https://www.st.com/en/development-tools/st-link-v2.html https://octopart.com/search?q=st-link+v2&currency=USD&specs=0 then you can try to debug that, but that ...

The values given and used are correct, yup check the LED, try to use a led connected to a different pin manually e.g. on the headers. I've more than once used boards with a 'defective' LED, sometimes they put the LED reversed, that'd never light up. manufacturing error. no need to look at schematic....

@Fziegler_076 wrote: RCC_OscInitStruct.PLL.PLLM = 8; RCC_OscInitStruct.PLL.PLLN = 48; RCC_OscInitStruct.PLL.PLLP = RCC_PLLP_DIV4; RCC_OscInitStruct.PLL.PLLQ = 8; ^ this won't work, try RCC_OscInitStruct.PLL.PLLM = 8; RCC_OscInitStruct.PLL.PLLN = 192; RCC_OscInitStruct.PLL.PLLP = RCC_PLLP_DIV2; RCC_O...