ChibiOS Free Embedded RTOS

You were, of course, correct. It turns out that my board had the boot0 pin pulled low by default, instead of high. The programming utility would write to flash and verify, but complete process would fail. I fixed this in hardaware, and now everything behaves as it should (including the oscillator ...

It looks like the STM32F373 eval board does use an external clock. The mcuconf.h files for that demo, and the stm32f303 discovery board demo look very similar. I believe the relevant defines for clock configuration are:

#define STM32_NO_INIT FALSE
#define STM32_PVD_ENABLE FALSE
#define STM32_PLS ...

It appears that you are correct! I tested the same code, using my work computer, and qstlink2 doesn't have the same "LIBUSB_ERROR_TIMEOUT" that I was experiencing last night. It successfully programs on my work computer, using the syntax: "qstlink2 -cli --write --verify ./build/ch.bin."

Regarding ...

It's taken me a while to get an STLink V2 debugger setup with GDB - I've had final exams with grad school to contend with. Fortunately, I've had some time today to revisit this (I also switched to the STM32F303CCT6, for more flash memory)

I've found that I can get example programs for the F3 ...

Thank you for your response.

I've created new board directory with modified versions of board.c, board.h, and board.mk. I've also verified that the clock settings match. So far my changes will still run on the F3-discovery board, but not the F303CBT6.

Perhaps there is a problem in the HAL ...

Hello!

I'm working on a ChibiOS application for the STM32F303CBT6, but thus far I haven't been able to get a binary to run on the microcontroller. The CBT6 is a 48-pin variant of the F303, with 32K of RAM, rather than 40K.

I've begun by using the demo under /ARMCM4-STM32F303-DISCOVERY/, testing on ...