New wiki

Vassilis wrote:The screenshots were extracted from STM32CubeMX.

@WereCatf I don’t want to disagree with you. Perhaps, some 103 supports 36 Mbps but according to the manual and the STM32CubeMX I cannot verify that the SPI works at higher speed than 18 Mbps

Vassilis wrote:The screenshots were extracted from STM32CubeMX.

@WereCatf I don’t want to disagree with you. Perhaps, some 103 supports 36 Mbps but according to the manual and the STM32CubeMX I cannot verify that the SPI works at higher speed than 18 Mbps

WereCatf wrote:Vassilis wrote:The screenshots were extracted from STM32CubeMX.

@WereCatf I don’t want to disagree with you. Perhaps, some 103 supports 36 Mbps but according to the manual and the STM32CubeMX I cannot verify that the SPI works at higher speed than 18 Mbps

SPI_CLOCK_DIV_2 should actually be SPI_CLOCK_DIV2. I always seem to make the same mistake.

Vassilis wrote:Ok, I will try that

I have made some tests a few minutes ago on STM103C8T6 + Atollic IDE + Oscilloscope. My oscilloscope is not fast enough to catch in detail the 36 Mbps stream but I saw clearly that it was a difference on the pulses duration between SPI_BAUDRATEPRESCALER_4 (18 Mbps on SPI 1) and SPI_BAUDRATEPRESCALER_2 (36 Mbps).

It seems that the SPI1 works at 36 Mbps but I suspect that ST was limited the SPI speed upto 18 Mbps either because there were problems during the transmit/receive process (unstable communication on F103 die) or the speed is limited to force us buy the next level STMs with higher SPI speed. I guess the first reason is more logical than the second one.

Vassilis wrote:I guess the first reason is more logical than the second one.

ahull wrote:Vassilis wrote:I guess the first reason is more logical than the second one.

ahull wrote:Vassilis wrote:I guess the first reason is more logical than the second one.

WereCatf wrote:I suppose the wiki could be edited to mention that 36Mbps-speed is overspec but should work fine, if you kids feel it’s important?

Vassilis wrote:WereCatf wrote:I suppose the wiki could be edited to mention that 36Mbps-speed is overspec but should work fine, if you kids feel it’s important?

I just added a page for the HAL MX Core

Vassilis or Sheepdoll, please feel free to update this page, any information is better than nothing. Spelling and punctuation can easily be fixed later

http://wiki.stm32duino.com/index.php?title=HAL_MX_core

Guys

I have started to update the pages that list the boards, to include photos, as most of the boards dont have proper product codes etc, so an additional way that people would be able to locate a board is visually.

I dont have all boards, so Im taking images from the web and giving credit where necessary e.g The original Maple Mini images are from Sparkfun, who allow reuse of image if there is attribution.

I have yet to work out a good standard template for the boards, but I think its important to put key information at the top, which will allow people to get their board up and running as quickly as possible.

Specifically…

Link to the correct bootloader binary
Details of any hardware changes that are required (usually the USB pull up resistor)
Details of any physical modifications, e.g Put glue on the micro usb connector to prevent it breaking off.
Details of which pin the LED is connected to ( if the board has one, or more LEDs connected to GPIO)
Details of any other built in hardware on the board, e.g. What pin the button is on , if it has one, or more, buttons, details of connected SD card or external RAM or EEPROM etc, and whether these external hardware items are supported (a lot of boards have SD but its connected via SDIO which we dont have a library for)

The full technical spec of the MCU can be linked on a separate page to save duplication

Edit.
And a link where to buy the board. E.g. link to eBay search or Aliexpress search, unless there is only one vendor (e.g Olimex)

@roger
a while back i got some boards that i thought were 103 based which had a nrf24 8 way header.
turned out they were in fact 107 based.

was the consensus at the time that programming them as though 103’s worked?

really question if the answer above was yes, then should they be added and flagged as potentially having either 103 or 107?
ok, i’ll go find them anyway and try blinky

stephen

Hi Stephen

It would be good to know if other F1 series MCU’s work with libmaple

I’m pretty sure I managed to upload a sketch onto a STLink dongle which had a STM32F101C8T MCU in it, and also that the bootloader worked.
(Though in the end I converted it back to a STLink, as it has so few pins available, it was more useful to me as a STLink than as a MCU board)

RogerClark wrote:I just added a page for the HAL MX Core

Vassilis or Sheepdoll, please feel free to update this page, any information is better than nothing. Spelling and punctuation can easily be fixed later

http://wiki.stm32duino.com/index.php?title=HAL_MX_core

Thanks

sheepdoll wrote:RogerClark wrote:I just added a page for the HAL MX Core

Vassilis or Sheepdoll, please feel free to update this page, any information is better than nothing. Spelling and punctuation can easily be fixed later

http://wiki.stm32duino.com/index.php?title=HAL_MX_core

BTW.

I’ve updated the Baite Maple mini page

http://wiki.stm32duino.com/index.php?ti … Maple_Mini

I’m hoping that this format of page will be easy for people with no STM32 experience to understand and will get them up and running as quickly as possible

I know I still need to write a far more detailed installation section

Can you create an account on the wiki for me? I’d like to add some notes to the “Ugly Board” page