Update Bluepill wiki data

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

PLease may you update the wiki and add the fact that many(probably all) C8 Mcu version have 128KB.
You maybe can explain that for this reason you have added a two generic F103C8 board in the core, the 64KB and the 128KB

Thanks

Anyone can create an account on the wiki and the edit the pages

st say it is a 64k device.
they seem to use a process yielding 128k.

if you choose to use 128k, it is not a certainty that it works.
it has legal aspects.

stephen

I updated the Bluepill wiki page, i added the bootloader message output also
@RogerClark do you like it ?

@zmemw16
Seems that all the F103C8 work on 128KB, for now nobody come here for tell that he have a board that do not work on 128KB
Probably it is only a commercial requirement put the C8 in the ST catalogue whit 64KB specification.

There is in fact other ST model that have undocumented Peripheral also, like some MCU whit two Timer on datasheet but instead it have TIM 0,1,2 working

For the people that want use only the 64KB for legal reason on his project, he can use the 64KB upload setting, but it is important that the 128KB upload board setting remain inside the core.

testato wrote:I updated the Bluepill wiki page, i added the bootloader message output also
@RogerClark do you like it ?

@zmemw16
Seems that all the F103C8 work on 128KB, for now nobody come here for tell that he have a board that do not work on 128KB
Probably it is only a commercial requirement put the C8 in the ST catalogue whit 64KB specification.

There is in fact other ST model that have undocumented Peripheral also, like some MCU whit two Timer on datasheet but instead it have TIM 0,1,2 working

For the people that want use only the 64KB for legal reason on his project, he can use the 64KB upload setting, but it is important that the 128KB upload board setting remain inside the core.

if i market a product with a 103c8 in it using more than 64k of flash and as a result, someone gets hurt or dies.
just how long do you think it would before the court date for damages?

if i do it solely for myself say to use in a competitive robot and again someone etc.
same question.

if i do it solely for myself and again someone, a relative maybe etc.
same question or maybe not.

if i do it solely for myself and i get hurt, you’ll hopefully be able to call yourself some names, mutter some words and fix the ’cause’

it would not be ST in court.
this line remains for all the above if i don’t use 64k

stephen

zmemw16 wrote:if i market a product with a 103c8 in it using more than 64k of flash and as a result, someone gets hurt or dies.
just how long do you think it would before the court date for damages?

if i do it solely for myself say to use in a competitive robot and again someone etc.
same question.

if i do it solely for myself and again someone, a relative maybe etc.
same question or maybe not.

if i do it solely for myself and i get hurt, you’ll hopefully be able to call yourself some names, mutter some words and fix the ’cause’

it would not be ST in court.
this line remains for all the above if i don’t use 64k

stephen

if i market a product with a 103c8 in it using more than 64k of flash and as a result, someone gets hurt or dies.
just how long do you think it would before the court date for damages?
You will be liable, as almost all MCUs (and other components) manufacturers have put a Disclaimer at the end of their Datasheets, saying they are not liable when somebody uses that component for that kind of application..

and if i add the same disclaimer?
without opening a bag of worms isn’t that in the gpl; v2 & v3

re 10K – just lack of reading or understanding on their part?

stephen

zmemw16 wrote:and if i add the same disclaimer?
without opening a bag of worms isn’t that in the gpl; v2 & v3

re 10K – just lack of reading or understanding on their part?

stephen

i was referring to the usage of 4k7 or 10k, not usb.
however in order for usb host system to re-enumerate the usb, experience suggests a better value to use would 1k5 or 1k8 in parallel with the 10k, the value for use with a 4k7 is left as an exercise for the reader.
i don’t know what the usb specification says.
stephen

zmemw16 wrote:i don’t know what the usb specification says.

testato wrote:
Seems that all the F103C8 work on 128KB, for now nobody come here for tell that he have a board that do not work on 128KB

michael_l wrote:
Well, I guess to me it is not clear what ‘usb to work properly” means. But that’s just me..

I think the point to note is that the correct value is 1.5k, but some PCs are tolerant of incorrect value

ok, i changed the last line to :
It is also true that some PCs are tolerant of incorrect value so, before you change the resistance, you can try if it works in your case.

sounds good

While we are dusting and cleaning, I threw in a pinout picture and pdf link.

Thanks

FYI: Not sure if I just got lucky but I got 3 of these and all of them had the standard ST serial boot loader present. All the review I have seen state that these do not have the boot loader on them so not sure why mine did. Great little boards.

It is unfortunate but the ST system bootloader embedded in every ST chip, and the custom flash bootloader both have the same name “bootloader”. You probably refer to the former.

@visinet
yep, on every ST MCU is there a factory bootloader, on some model is there many bootloaders, for example a serial BL and a I2C BL inside the same mcu.
The Bluepill have only the Serial BL inside, but you can manually install the stm32duino USB BL if you want upload new fw by usb.

the Software Installation section should be completely rewrited,
I think this Perpetual mode, is an old procedure ?
place the board into “perpetual bootloader” mode before you can upload a sketch; place resistor between pin PC14 and 3.3V, then reset the board

testato wrote:the Software Installation section should be completely rewrited,
I think this Perpetual mode, is an old procedure ?
place the board into “perpetual bootloader” mode before you can upload a sketch; place resistor between pin PC14 and 3.3V, then reset the board

testato wrote:the Software Installation section should be completely rewrited,
I think this Perpetual mode, is an old procedure ?
place the board into “perpetual bootloader” mode before you can upload a sketch; place resistor between pin PC14 and 3.3V, then reset the board

I can confirm the bootloader does not take any RAM after its finished running. I think it used to take 3k.

Victor

BTW.
Anyone can register on the wiki and update it

RogerClark wrote:Victor

BTW.
Anyone can register on the wiki and update it

OK

There have not been too many changes to the bootloader over the last year.

There was a fix for newer versions of GCC and also some experimental code to use the battery backed registers to hold the bootloader in DFU (aka perpetual mode) but I think thats about it apart from new variants (but those are just #defines in the config file)