New wiki

Hi Guys

I’m in the process of setting up a wiki where we can store the wealth of information that has been posted to the forum, in a more logical and easy to find way.

If anyone can spare some time to help populate the wiki, please let me know.

It will use Mediawiki, which is the same as Wikipedia uses, as its the most stable and versatile wiki system that I know of, and I have used it before.

Top of the To Do list, is to get a list of boards into the wiki, including photos and were possible schematic.

There is a load of text in the Github wiki that I can pull into this wiki, and I can probably “borrow” some information from the old leaflabs wiki.
(Note, I’ve emailed leaflabs, several days ago, to ask if its possible to mirror their wiki page(s), but I’ve not had a response )

BTW. I don’t think I can pull your existing login information into the user database for media wiki, but I may be able to batch create new accounts and use your email addresses as the initial passwords.
However as I suspect that most people will not have the time to help with this, I will probably end up creating accounts manually.

Oooh, i’d love to help XD.

racemaniac wrote:Oooh, i’d love to help XD.

RogerClark wrote:racemaniac wrote:Oooh, i’d love to help XD.

@racemanic

Its cool.

Do whatever you feel works best, we can always make new pages later and copy the content across, and orphan (or possibly delete the old pages)

I’m just adding some info to the Blue and Red pill boards etc.

Btw, if people have suggestions of what should be documented on the wiki, feel free to post suggestions
Such a big blank sheet is intimidating XD

Ah, and another question: Do we try to link as much as possible to the forum, or do we try to duplicate the info of the forum on the wiki?

You’ve made a page for all the libraries. Will it just become an index with links to the forum?

Re: Libraries

I suspect its better to put the headlines in the wiki and perhaps link to the forum if there is a lot of detail.

Not sure about the other content, i.e whether to link or duplicate

BTW.
I enabled uploads, so images can be inserted

Looks good.

BTW when I try to log in, the wiki claims there is no user named ahull, Should I use my full name, or has my account not been created?

ahull wrote:Looks good.

BTW when I try to log in, the wiki claims there is no user named ahull, Should I use my full name, or has my account not been created?

ahull wrote:Looks good.

BTW when I try to log in, the wiki claims there is no user named ahull, Should I use my full name, or has my account not been created?

Looking good so far, I suggest for the boards pages, we try to adopt a broadly similar structure for each board, with image at the top, schematics where available, in roughly the same area of the page and so forth. Perhaps a page template and instruction for adding new boards may be a good way to ensure this.

Something like the camera details pages on the CHDK wiki for example.

Andy,

Sounds good to me

@racemaniac did start to apply some standardisation, but we will need to evolve the standard as we work out the best way to do this.

Another challenge I can see is for boards that don’t have names, e.g there are loads of larger STM32F103R series boards, as well as V and Z series.

Re: Libraries

I think @racemaniac is using the built in Category system, but the side effect appears to be that Working libraries appear last.

I think where possible we should be positive and show what works first

RogerClark wrote:Andy,

Sounds good to me

@racemaniac did start to apply some standardisation, but we will need to evolve the standard as we work out the best way to do this.

Another challenge I can see is for boards that don’t have names, e.g there are loads of larger STM32F103R series boards, as well as V and Z series.

Re: Libraries

I think @racemaniac is using the built in Category system, but the side effect appears to be that Working libraries appear last.

I think where possible we should be positive and show what works first

@racemania

No worries

I’m going to focus on getting pages for as many boards added to the Wiki as possible, with some basic details and hopefully some of the other forum members can add more detail if they have that specific board. e.g. I know @madias has the Nucleo F103RB (but no longer uses it as its a pain to use)

Upload file types

Guys. Can you give me a list of what file types need to be uploadable to the wiki?

i.e I just tried to upload a pdf of a schematic and it was not allowed, so I’ve just added pdf, sch and brd to the list.

I’m sure there will be more types that we need, but I’m not sure what they are.

So if you come across a new file type you need to upload, post here of PM me, as I need to manually add it to the PHP settings file (i.e there isnt even an Admin UI for this in Media Wiki)

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

I’m going to manually add accounts for the top 20 posters.

To login, use your normal username and request a password reset, (As I’m setting random passwords when the password is created)

Ok, wasnt here for a while (school and stuff). That explains the sudden email i got

~Straw

RogerClark wrote:I’m going to manually add accounts for the top 20 posters.

To login, use your normal username and request a password reset, (As I’m setting random passwords when the password is created)

(LOL)

Sorry guys, I wasnt aware that MediaWiki would send out emails when I created an account and specified a password.

I know it sends an email if I select that a random password should be used, and that the user must change the password by following the link, but there was no mention of the email, if I specified a password.
I assumed the accounts would just be dormant and that people could reset the password if they wanted to update the wiki.

Good job I didnt do the whole forum

Just a small thing: my take on the wiki logo

~Straw

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

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

Hi Dan

I just created an account.

You will get emailed a temporary password by MediaWiki and then need to change it when you login

I’ve also updated the page to use the most recent layout, that I’m now using on the other boards

If you want to modify the layout e.g. add more to the table at the top or to the sections, thats OK, we can revisit standardizing things later

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

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

I think this is originally my mistake.

That board has a header that looks like it accepts JTAG, but appearances as deceptive

Are we also going to start document common scenarios on the wiki of things you may want to use.
Like for example what was asked in http://www.stm32duino.com/viewtopic.php?f=3&t=1095
It may be useful to start putting basic code samples that show how to use all the features of the stm32 .

racemaniac wrote:Are we also going to start document common scenarios on the wiki of things you may want to use.
Like for example what was asked in http://www.stm32duino.com/viewtopic.php?f=3&t=1095
It may be useful to start putting basic code samples that show how to use all the features of the stm32 .

WereCatf wrote:racemaniac wrote:Are we also going to start document common scenarios on the wiki of things you may want to use.
Like for example what was asked in http://www.stm32duino.com/viewtopic.php?f=3&t=1095
It may be useful to start putting basic code samples that show how to use all the features of the stm32 .

racemaniac wrote:Then make an index in the wiki so people can quickly find the applicable example sketch (and that we can see for which features we don’t have examples yet)

The most common problem seems to be USB..

resetting to upload
driver installation
dfu-util installation
udev rules (linux) and device permissions
and
Hardware faults on usb , including the 10k resistor on the blue pill etc

For new users a link to Wiki in Quick Links would be nice. At the moment, new users are not expecting that the Wiki pages are available.