30KB Blue-Pill USB Binary testing image.

[techman-001]

Did the flash test but forgot to post it.   They both passed!

top (decimal id)

Code: [Select]

Testing 64kB Flash block: 0x10000 - 0x1FFFF
Erasing
Flash with 1010101010101010 (0xAA)
Testing for 0xAA - OK
Erasing
Flash with 0101010101010101 (0x55)
Testing for 0x55 - OK
Erasing
~~~~~ ALL TESTS PASSED ~~~~~

bottom (hex id)

Code: [Select]


Testing 64kB Flash block: 0x10000 - 0x1FFFF
Erasing
Flash with 1010101010101010 (0xAA)
Testing for 0xAA - OK
Erasing
Flash with 0101010101010101 (0x55)
Testing for 0x55 - OK
Erasing
~~~~~ ALL TESTS PASSED ~~~~~


I'll be sure to grab the new tool once its out.

Thanks for the update 

I think you have two STM32F103C8's there as the hidden and working 2nd 64kB block seems to be a feature of that chip only.

Your STM32F103C8 chip below is the first I have seen with a Alpha character in the Lot Numbers which means that my theory that STM32F103C8's don't have alphanumerics in their Lot Numbers is now BUSTED!

Die xy coords: 107872310
Wafer Number: 49
Lot_num ascii encoded  [23:0]: 0x0031304B  | 1 0 K

Not handling the "0x00" character was a BUG I have fixed in the upcoming V2 release, so yours should have read:
Lot_num ascii encoded  [23:0]: 0x0031304B  | . 1 0 K    (where the "." means "non-printable ASCII character") . "4B" is the (hex) ASCII code for "K".

Those with a Linux/*bsd pc's can type "man ascii" for a nice chart showing octal,decimal and hex ASCII tables to see what I mean.

[westfw]

So, real stm32s don’t match their datasheet (they have the extra 64k flash), but the fake ones do?

[iMo]

..that is because STM is faking their own chips..

[techman-001]

So, real stm32s don’t match their datasheet (they have the extra 64k flash), but the fake ones do?

lol. It's only the STM32F103C8 that has the 'hidden' Flash as far as I know, and that chip is ancient.

I expect that even ST Micro isn't immune to the whims of sales and marketing droids.

[techman-001]

..that is because STM is faking their own chips..

If you can't beat em, join em!

[JensG]

Hello,

unfortunatley some of my cheap bluepills are the ones with the 3 notches on the mcu.

the wrong pullup resistor was not the cause for no usb connection.

this mecrisp testing image is working fine.  the fake bluepill connects as virtual com port.

i have a image for a hid controller and with it the fake bluepill has no usb.

does this fake bluepill have the ability working as hid controller  or   only as com port ?

[techman-001]

Hello,

unfortunatley some of my cheap bluepills are the ones with the 3 notches on the mcu.

the wrong pullup resistor was not the cause for no usb connection.

this mecrisp testing image is working fine.  the fake bluepill connects as virtual com port.

i have a image for a hid controller and with it the fake bluepill has no usb.

does this fake bluepill have the ability working as hid controller  or   only as com port ?

That may depend on the actual MCU ?

Have you tried my new image stm32f103xx-diagnostics ?

It has better detection of the actual chip, and more accurate information, plus produces a XML output of all the data if desired.

https://mecrisp-stellaris-folkdoc.sourceforge.io/stm32f1xx-diagnostics.html#stm32f103xx-diagnostics

[JensG]

i tried the latest image:



<?xml version='1.0' encoding='UTF-8'?>
<DEVICE xs:noNamespaceSchemaLocation='STM32F103_DIAGNOSTICS_V2.0.XSD'>
 <DEBUG>
   <IDCODE>$20036410 </IDCODE>
 </DEBUG>
 <DERIVED>
   <DUID>01684E26 </DUID>
   <FLASH-SIZE>65536 </FLASH-SIZE>
 </DERIVED>
 <EXTERNAL-MARKINGS>
   <STM32F103C8>0 </STM32F103C8>
   <STM32F103CB>0 </STM32F103CB>
   <CS32orAPM32>0 </CS32orAPM32>
   <GD32F103>0 </GD32F103>
   <OTHER>0 </OTHER>
 </EXTERNAL-MARKINGS>
 <FLASH>
   <SIZE-REGISTER>$FFFF0040 </SIZE-REGISTER>
   <SECOND-64KB-BLOCK>1 </SECOND-64KB-BLOCK>
 </FLASH>
 <SCB_CPUID>
   <BITS-31:24>$41</BITS-31:24>
   <BITS-23:20>$2 </BITS-23:20>
   <BITS-19:16>$F </BITS-19:16>
   <BITS-15:4>$C23 </BITS-15:4>
   <BITS-3:0>$1 </BITS-3:0>
 </SCB_CPUID>
 <UNIQUE-DEVICE-ID-REGISTER>
   <BITS-95:64>
     <HEX>$160707E2 </HEX>
     <ASCII>....</ASCII>
   </BITS-95:64>
     <BITS-63:32>
     <HEX>$13003118 </HEX>
     <ASCII>..1.</ASCII>
   </BITS-63:32>
   <BITS-31:0>
     <HEX>$046F78DC </HEX>
     <ASCII>.ox.</ASCII>
   </BITS-31:0>
 </UNIQUE-DEVICE-ID-REGISTER>
</DEVICE>

[techman-001]

i tried the latest image:



<?xml version='1.0' encoding='UTF-8'?>
<DEVICE xs:noNamespaceSchemaLocation='STM32F103_DIAGNOSTICS_V2.0.XSD'>
 <DEBUG>
   <IDCODE>$20036410 </IDCODE>
 </DEBUG>
 <DERIVED>
   <DUID>01684E26 </DUID>
   <FLASH-SIZE>65536 </FLASH-SIZE>
 </DERIVED>
 <EXTERNAL-MARKINGS>
   <STM32F103C8>0 </STM32F103C8>
   <STM32F103CB>0 </STM32F103CB>
   <CS32orAPM32>0 </CS32orAPM32>
   <GD32F103>0 </GD32F103>
   <OTHER>0 </OTHER>
 </EXTERNAL-MARKINGS>
 <FLASH>
   <SIZE-REGISTER>$FFFF0040 </SIZE-REGISTER>
   <SECOND-64KB-BLOCK>1 </SECOND-64KB-BLOCK>
 </FLASH>
 <SCB_CPUID>
   <BITS-31:24>$41</BITS-31:24>
   <BITS-23:20>$2 </BITS-23:20>
   <BITS-19:16>$F </BITS-19:16>
   <BITS-15:4>$C23 </BITS-15:4>
   <BITS-3:0>$1 </BITS-3:0>
 </SCB_CPUID>
 <UNIQUE-DEVICE-ID-REGISTER>
   <BITS-95:64>
     <HEX>$160707E2 </HEX>
     <ASCII>....</ASCII>
   </BITS-95:64>
     <BITS-63:32>
     <HEX>$13003118 </HEX>
     <ASCII>..1.</ASCII>
   </BITS-63:32>
   <BITS-31:0>
     <HEX>$046F78DC </HEX>
     <ASCII>.ox.</ASCII>
   </BITS-31:0>
 </UNIQUE-DEVICE-ID-REGISTER>
</DEVICE>

I see you didn't select the external markings, what markings are on the chip, what does it claim to be ?

[techman-001]

i tried the latest image:



<?xml version='1.0' encoding='UTF-8'?>
<DEVICE xs:noNamespaceSchemaLocation='STM32F103_DIAGNOSTICS_V2.0.XSD'>
 <DEBUG>
   <IDCODE>$20036410 </IDCODE>
 </DEBUG>
 <DERIVED>
   <DUID>01684E26 </DUID>
   <FLASH-SIZE>65536 </FLASH-SIZE>
 </DERIVED>
 <EXTERNAL-MARKINGS>
   <STM32F103C8>0 </STM32F103C8>
   <STM32F103CB>0 </STM32F103CB>
   <CS32orAPM32>0 </CS32orAPM32>
   <GD32F103>0 </GD32F103>
   <OTHER>0 </OTHER>
 </EXTERNAL-MARKINGS>
 <FLASH>
   <SIZE-REGISTER>$FFFF0040 </SIZE-REGISTER>
   <SECOND-64KB-BLOCK>1 </SECOND-64KB-BLOCK>
 </FLASH>
 <SCB_CPUID>
   <BITS-31:24>$41</BITS-31:24>
   <BITS-23:20>$2 </BITS-23:20>
   <BITS-19:16>$F </BITS-19:16>
   <BITS-15:4>$C23 </BITS-15:4>
   <BITS-3:0>$1 </BITS-3:0>
 </SCB_CPUID>
 <UNIQUE-DEVICE-ID-REGISTER>
   <BITS-95:64>
     <HEX>$160707E2 </HEX>
     <ASCII>....</ASCII>
   </BITS-95:64>
     <BITS-63:32>
     <HEX>$13003118 </HEX>
     <ASCII>..1.</ASCII>
   </BITS-63:32>
   <BITS-31:0>
     <HEX>$046F78DC </HEX>
     <ASCII>.ox.</ASCII>
   </BITS-31:0>
 </UNIQUE-DEVICE-ID-REGISTER>
</DEVICE>

Excellent 

It looks like one of these chips to me, but with a different REVID, and 128kB flash
GD32F130C8T6:   CPUID:0x412FC231     DevID:0x0410 RevID:0x1303
GD32F150C8T6:   CPUID:0x412FC231     DevID:0x0410 RevID:0x1303

If this is the case then you can download the User Manual (inc USB capabilities) at https://www.gigadevice.com/microcontroller/gd32f130c8t6/

[JensG]

the chip has 3 notches 
stm32
F103C8T6
991ka 93
MYS 807