Matrix user forums

I am using the nucleo 446re target currently but you only brought out the Arduino pins and not the others.
You have a 446ZE but that is the 100 pin version.

Thanks!

Chad

So I spent most of a day comparing the 446 STARM various targets with the intention of making my own.
Only to find out that I can't modify a target nor can I make a new target. FC doesn't see them if they are changed.

Will you PLEASE generate a 446RE full chip and fix the the Nucleo 446RE target to 1) Clock it to 180 Mhz 2) Bring out all of the pins.
I Tried to do it But FC won't let me.

thank you
chad

Hi Chad,
I'll see what I can do about creating an RE version when we are back in the office later in the week.
I don't think we have any intention of changing the Nucleo format, an RE should suffice for you.
The clock versus crystal frequency I've explained before, unless I'm misunderstanding your request.
Thanks,
Leigh

An RE version would be wonderful!
I would be happy to share the clock settings that cube MX came up with to get it to default to 180mhz if you are interested.
Thank you.

chad

Hi Chad
Here is an FCD for the 32F446RE (to go into \ProgramData\MatrixTSL\FlowcodeV8\FCD\ARM)
It's a temporary file until it gets into the auto update system.
Leigh

Thank you much! I will give it a try!!
*edit
I put it into the flowcodev8>Defaultdata>flowcodev8>FCD>ARM.
It doesn't show up in the arm list.

thanks,

Chad

Hi Chad,
If Flowcode was running when you added file, Try refreshing:

Never mind. I didn't see the hidden folder 'program data' I was putting it in the program files folder. What can I say, I am a moron.
I do now have one other little problem: It isn't programing the nucleo.

CHad

The chip versions use the ST-LINK by default,
please try attached FCD file instead,
this will use the Nucleo virtual drive.
Leigh

I figured that was it. I am a long way to having a bare chip on the board...

I tried it and It says "The file cannot be copied onto itself. And doesn't program. The nucleo 446 has NODE-F at the end, whatever that means.

thanks
chad

Hi Chad
When you plug the 446 Nucleo board into your PC, what name is given to the virtual drive that appears?
Did this (the programming) previously work when you used the "32F446Nucleo64" as the selected target device in Flowcode?
Thanks
Leigh

HI, yeah the nucleo64 compiles and programs great. It shows up as "NODE_F446RE" in computer. The nucleo 303k8 works fine also.

aah, that is the NODE_F...

chad

Ah, right, my mistake, here we go again

Hallelujah! We have light! And more pins and stuff!

That did it. I'll hang on to the st-link version for the future..

Thank you very much Leigh!

Chad

Hi,

I ran into a problem the other day. I tried to assign uart 3 and it wouldn't compile. I think there might be something funky going on..

Thanks,

chad

Hi Chad,
Thanks for the post, but USART3 compiles OK for me, did you assign the Rx, Tx pins etc?
If you see it again and could post an example? that would be very useful.
Thanks
Leigh

My bad, Try uart 4 pa0,pa1.

thanks,
chad

Hi Chad,
Thanks for the spot!
Fixed FCD attached. This will hopefully also go out on the update system soon.
Cheers
Leigh

Cool, arm just got a little bit better.

BTW, I did an FC update and it broke the 446re target. I can't select it in the build options and it broke my program. When it updated it it said it was not genuine.
I haven't tried to drop in the file you sent yet.

chad

The files I've sent will appear as non genuine, the update system should now have the latest version that I fixed.
But if it gives problems, you could overwrite with the one I posted.
The two should have the same contents as far as the project is concerned.

Good to go now! thanks

chad

Spoke too soon. It defaulted to the nucleo version. I deleted it and re-installed from the FC updater. When I go to select it I get this error.
I also tried to install the one that you posted and it gives me the same error..

Chad

Hi Chad,
That is very odd, same happens on my home PC.
File contents seem OK to me, maybe something to do with the update.
I'm out of the office for a while, hope Ben can fix this Monday.
Leigh

Glad It isn't just me! Ok, i'll wait for ben to debug this...
Thanks,
Chad

Hi Chad,

We are currently investigating what's gone wrong here. Hopefully we can have the problem resolved for you very soon.

Edit: Hopefully all fixed for you now. Fingers crossed.