GD32F130C8T6 STM32F103xx STM32F1xx ???

[davhal]

Hi,

New user to Flowcode8 (last used Flowcode3- a long time back)!

Can not find any STM or GD 1xx series ARM Cortex M-3 chip support.

Are these chips supported in any way?

Or, is there a viable work-around of sorts?
((my "C" knowledge/experience is poor at best))

We have a number of PCBs populated with GD32F130C8T6
but our "super" coder was unable to complete the project before
becomming a Mom {congratualtions, and all best wishes}!

Anyway, Flowcode might be the most efficient "solution" at this point
[project: integrated BLDC motor controller - Roof Repair Rover Pod].

Thanks - all technically constructive help is appreciated!

davhal

[davhal]

Brief update #1 > encouraging!

Flowcode8 chip resource contains an STM32F303CB (ST):

- LQFP48 package with the same pin layout as the populated GD32F130 (GD)
- GD is Cortex M3; ST is Cortex M4 [appears M3 & M4 are similar but M4 also includes DSP]

So, maybe two (possible) solutions here;

1. Pull the GD and replace with this ST part,
the added DSP may provide for a better low speed motor performance.
2. Figure a way to modify the "Flowcode chip header file" (CMSIS?) to "create" this GD chip.

After digging into the program a bit deeper - Flowcode appears to be an impressive piece of work!

Well, back to working this "fix."

davhal

[davhal]

Brief update #2 > mild setback!

It appears the PCB layout does not follow filed schematic:
- reasons provided from fab include -> GD port pins/functions can be moved around to suit routing, etc.;

Initially this caused concern when checking and pseudo reverse engineering, however, with the help of:
- Flowcode's "C" to Flow Chart combined with
- ST's STM32CubeMX tool, things are slowly falling into place.

A definite learning curve for those unfamiliar but the process is quite interesting to say the least.

davhal

[Romanlog]

Can you really move those pins around and have the PCB work normally?

[davhal]

Brief update #3> Completed workaround

Replaced the GD's with more powerful ST's (DSP capabilities, etc.).

Also, reviewed ST's recent BLDC development information (excellent). Worked Flowcode through several "new"
motor driver ideas (using flow chart - I'm not at all familiar with "C") and it appears (tests varify) a "fix" to the original
problem PLUS some major improvements to the original design!

So, thanks to Martix Flowcode and ST we are now back "on course."

This, IMHO, is a very nice, easy to use and understand, well done development approach.

All the best to everyone as we move through these trying times - stay safe...

[davhal]

Brief Update #4>
Attempting a reply to Romanlog - "Can you really move those pins around and have the PCB work normally?"
Sorry for the delay - I could not really find a good way to explain it - still can't! But maybe this will shed some light...

RE: Changing pin functions... a complex "thing" to describe, but here is some related info -

[youtube=]https://www.youtube.com/watch?v=exyhh9rw1VE[/youtube]
in particular at around the 11:50 mark.

https://www.youtube.com/watch?v=exyhh9rw1VE in particular at around the 11:50 mark.
Hope this will help explain the "moving functions to different pins during the PCB layout."

BTW - Just purchased all the Flowcode 8 Modules and Chips - thank you Matrix for the super deal!