New wiki

And how about a “getting started” page? Would be neat for newcommers

~Straw

strawberrymaker wrote:Just a small thing: my take on the wiki logo

~Straw

strawberrymaker wrote:And how about a “getting started” page? Would be neat for newcommers

~Straw

Well, I did add some stuff to the F103-section, though I’ll have to prettify the wiki at a later date.

Thanks for adding those tables

I think that possibly they should be on a page of their own, but we can tidy up things later

One thing I’d like to see in the wiki is a something that tracks the current status of the Arduino-implementation for STM32, like e.g. which hardware-features are supported, if there are some missing things wrt. that hardware-feature, ie. if it is only partially supported, and whether there are some examples available for that feature — this would allow potential users to gauge a little how quickly they can get to speed using this or that feature and whether the implementation is a good choice for them in the first place, and it’d provide a sort of a roadmap for any developer who may want to fill in a missing spot here or there, like e.g. someone gets bored, checks the list and decides to write a few examples on how to use FSMC for which we don’t have any examples at all yet. (I don’t actually know if it’s even supported)

Filling the list would take some time, but the benefits are worth it, IMHO.

@wereCatf

I’m not sure if you mean core parts of the API or things like CAN bus or SDIO, or things like OneShot timer modes etc

I suspect we are missing some API functions (well possibly a lot of API functions).

Unfortunately, I don’t think there is a “test unit” sketch which attempts to call all core functions.

I noticed the other day that one of the built in examples wouldnt run because functions like isDigit were not in the core, so I figured out that we didnt have WCharacter.cpp, so I integrated it, and I also updated the string functions.

But its highly likely that other functions are also missing, but I have no way of knowing, apart from perhaps trying all example sketches, and thats slightly problematic, as the often use AVR pin names e.g A0 which we don’t have ;-(

That being said.

Please feel free to make to make a start on a page that has the information you think is useful

RogerClark wrote:I’m not sure if you mean core parts of the API or things like CAN bus or SDIO, or things like OneShot timer modes etc

RogerClark wrote:Mainly to test the image and PDF stuff I just added

http://wiki.stm32duino.com/index.php?ti … 2F103V_-EK

Layout and formatting needs to be improved

stephen,

I agree its hard to catalog these boards.

I have a F103VET and F103ZET board, but neither have any model number printed on them; they just have the manufacturer url “www.vcc-gnd.com“

I think we need the boards page to be more of a picture gallery, or perhaps have a separate page for this, which allows people to visually find their board

Or we should just collect all boards on a page for the specific Microcontroller used on it. Like a F103V page with informations about it and a section with boards available

~Straw

@strawberrymaker

We can list the boards in many different ways, but we need to add pages for the boards (with details and pictures and if possible the schematic)

It is written in wiki
1) At the default CPU-speed of 72MHz the maximum speed for SPI1 is 36MHz and 18MHz for SPI2.

The STM32F103x8 pdf writes (page 19/117)

I didn’t edit the wiki because I wanted to be sure that it was written by mistake (typo) or some 103 model supports 36 Mbps speed.

Vassilis wrote:It is written in wiki
1) At the default CPU-speed of 72MHz the maximum speed for SPI1 is 36MHz and 18MHz for SPI2.

The STM32F103x8 pdf writes (page 19/117)

I didn’t edit the wiki because I wanted to be sure that it was written by mistake (typo) or some 103 model supports 36 Mbps speed.

Vassilis wrote:I didn’t edit the wiki because I wanted to be sure that it was written by mistake (typo) or it really supports 36 Mbps speed.

I do wonder why they don’t mention that SPI1 and SPI2 run at different speeds, though. Seems kind of a silly omission. Maybe they just don’t care to update the specs anymore as the chip is getting old and they want people to move to newer ones?

APB2 runs at twice the speed of APB1, and and SPI1 is on APB2, SPI2 is on APB1.
APB1 runs at maximum 36 MHz and APB2 runs at maximum 72 MHz.
On SPI1 the minimum prescaler value is 4 that gives 18 Mbps Max
On SPI2 the minimum prescaler value is 2 that gives 18 Mbps Max also

Vassilis wrote:APB1 runs at maximum 36 MHz and APB2 runs at maximum 72 MHz.
On SPI1 the minimum prescaler value is 4 that gives 18 Mbps Max
On SPI2 the minimum prescaler value is 2 that gives 18 Mbps Max also

WereCatf wrote:Vassilis wrote:APB1 runs at maximum 36 MHz and APB2 runs at maximum 72 MHz.
On SPI1 the minimum prescaler value is 4 that gives 18 Mbps Max
On SPI2 the minimum prescaler value is 2 that gives 18 Mbps Max also

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