Electronics > Beginners
CS32F103C8T6 datasheet and tests (was:"UNEXPECTED idcode" flashing bluepill)
<< < (7/10) > >>
ak634:
The format of these registers is in CoreSight Architecture Specification Section B2.2.2 PIDR0-PIDR7, Peripheral Identification Registers

0xfec PIDR3
0xfe8 PIDR2
0xfe4 PIDR1
0xfe0 PIDR0
0xfdc PIDR7
0xfd8 PIDR6
0xfd4 PIDR5
0xfd0 PIDR4

JEDEC, PIDR2 bits[3]  Must be 0b1 to indicate that a JEDEC-assigned value is used.

DES_0, PIDR1 bits[7:4] JEP106 identification code bits[3:0].
DES_1, PIDR2 bits[2:0] JEP106 identification code bits[6:4].
DES_2, PIDR4 bits[3:0] JEP106 continuation code.

PART_0, PIDR0 bits[7:0] Part number bits[7:0].
PART_1, PIDR1 bits[3:0] Part number bits[11:8].

JEP106 code seems to be a placeholder: JEDEC = 0 (must be 1), continuation code 0x5, ID code 0x55.
Part number is 0x29b, which is different from 0x410 in STM32.

Macbeth:
Looks like I missed the last words, FWIW they are the same as yours:

0xE00FFFF0:  0000000D  00000010  00000005  000000B1
ak634:

--- Quote from: Macbeth on October 08, 2019, 03:27:59 pm ---Looks like I missed the last words, FWIW they are the same as yours:

0xE00FFFF0:  0000000D  00000010  00000005  000000B1

--- End quote ---

Thanks, the previous dump actually was enough to read the identification info. I'm not sure if the chips are the same, but it appears in both cases they do not bear stm identification.

I am trying to make my USB stuff work on the clone with the "991KA" marking, and after a couple of nights debugging, it appeared USB does not receive setup packets correctly.

If anyone has USB communication working on this kind of clone or on the CS32, I would appreciate any pointers.
Macbeth:
I haven't had a chance to do any further USB testing, but I did get this version of mecrisp Forth with USB serial console working on the "991KA". See if that works and if so perhaps there is a clue in the source code.
ebastler:

--- Quote from: Macbeth on October 02, 2019, 05:20:03 pm ---I replaced the set _CPUTAPID 0x1ba01477 as suggested by tsman in the ...\resources\openocd\st_scripts\target\stm32f1x.cfg file and also had to set the generator options to connection speed 4MHz and reset mode to software. Debugging is now working with STM32CubeIDE  :-+
[...]
The dodgy bluepill boards purport to have proper STM32 chips. See attached.

--- End quote ---

I am just running into the same problem: Bought a BluePill board (even from a local seller, since I was impatient); the µC claims to be a proper STM32 chip; but it has the 0x2ba01477 ID. Ready to edit the config file -- but I seem unable to even find it.  :-[ 

I am using STM32CubeIDE, version 1.02. Where would the .cfg files live? In my project folder? In the "STM32CubeIDE" program folder hierarchy? I can't even find the "resource" folder which Macbeth helpfully gave as a starting point... Thanks for pointing me in the right direction!

EDIT: Ahh, got it now. For me, it's in C:\ST\STM32CubeIDE_1.0.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.debug_1.0.2.201907120816\resources\openocd\st_scripts\target. For whatever reason, the file search didn't find it when asking for the full "stm32f1x.cfg" name, but would find "*.cfg" right away. Grmpf...
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod