Search found 133 matches

by Mangy_Dog
Thu Jun 05, 2025 2:32 pm
Forum: General discussion
Topic: USART3/Serial3 outputting garbage... U575
Replies: 6
Views: 3684

Re: USART3/Serial3 outputting garbage... U575

WOOHOO! adding the define worked :)
#define HSE_VALUE 8000000UL
Thank you
by Mangy_Dog
Thu Jun 05, 2025 2:27 pm
Forum: General discussion
Topic: USART3/Serial3 outputting garbage... U575
Replies: 6
Views: 3684

Re: USART3/Serial3 outputting garbage... U575


Simply redefine it in your variant*.h file
Example for NUCLEO_F722ZE:
https://github.com/stm32duino/Arduino_Core_STM32/blob/449839ea1b493a3fac6396826dc7afffbaf2568a/variants/STM32F7xx/F722Z(C-E)T_F732ZET/variant_NUCLEO_F722ZE.h#L224


Looking in the file that used to be called variant_generic.h ...
by Mangy_Dog
Thu Jun 05, 2025 2:06 pm
Forum: General discussion
Topic: USART3/Serial3 outputting garbage... U575
Replies: 6
Views: 3684

Re: USART3/Serial3 outputting garbage... U575

Im using HSE as the main clock in the clocks setup I have the uarts connected to SYSCLK which is derived from HSE through PLLM /1 X23 /6 to give a target of 32mhz main clock.

Its a 8mhz source.

In what file does "#define HSE_VALUE 16000000UL /*!< Value of the External oscillator in Hz */" go ...
by Mangy_Dog
Thu Jun 05, 2025 12:24 pm
Forum: General discussion
Topic: USART3/Serial3 outputting garbage... U575
Replies: 6
Views: 3684

USART3/Serial3 outputting garbage... U575

Hi again new issue so new thread. we have USART3 on PC10/PC11 for debug output. But for some reason its outputting garbage.

I created a hello world in cubeIDE and it works fine there.
I am using the same clock config as cubeIDE so I know its not some strange clock sync issue.

The output is bad ...
by Mangy_Dog
Thu Jun 05, 2025 9:48 am
Forum: General discussion
Topic: Warning: The core is locked up U575
Replies: 5
Views: 3554

Re: Warning: The core is locked up U575

Just to add, there was also a mistake in my OG variant that was causing the lock up... but reworking the whole thing after fixing that, it was step 5 that was the final thing breaking stuff :D
by Mangy_Dog
Thu Jun 05, 2025 9:45 am
Forum: General discussion
Topic: Warning: The core is locked up U575
Replies: 5
Views: 3554

Re: Warning: The core is locked up U575

FIXED IT!!!
Ok managed to get building and working on my IDE, the main issue is step 5 of the make a varient...
/* Memories definition */
MEMORY
{
- RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 144K
- FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 512K
+ RAM (xrw) : ORIGIN = 0x20000000, LENGTH = LD_MAX ...
by Mangy_Dog
Thu Jun 05, 2025 7:52 am
Forum: General discussion
Topic: Warning: The core is locked up U575
Replies: 5
Views: 3554

Re: Warning: The core is locked up U575

Hi all update on the situation ....
its nothing to do with the clock config, and more to do with the variant I've built.
Ether something is missing from the basic core files that is required or I made a mistake or missed something...
Im going to go through it again to see what I could have missed ...
by Mangy_Dog
Wed Jun 04, 2025 4:00 pm
Forum: General discussion
Topic: Warning: The core is locked up U575
Replies: 5
Views: 3554

Re: Warning: The core is locked up U575

clock.jpg
clock.jpg (89.16 KiB) Viewed 3553 times
Even trying a basic internal clock setup at low speeds and still getting the warning and no led blinky....

Im starting to think its not the clock setup itself but something else wrong in the variant build up.
by Mangy_Dog
Wed Jun 04, 2025 3:41 pm
Forum: General discussion
Topic: Warning: The core is locked up U575
Replies: 5
Views: 3554

Warning: The core is locked up U575

We recently moved out project over to the U575 based chip.
But I'm running into a big issue that I cant seem to figure out.
Firstly as far as I can tell I got the power pins correctly wired up
575wireup.JPG

But even after configuring cubeides clock setup and putting that into the variant clock ...
by Mangy_Dog
Wed Dec 18, 2024 1:40 pm
Forum: General discussion
Topic: Difference in pin defines?
Replies: 1
Views: 1029

Difference in pin defines?

Hi I've ran into a strange issue.
When wanting to read an analogue value from PB0 or PB1. I've had to use the defines PB0/1 but PB_0 and PB_1 will always return 0...

While PA_4 and PA_5 will return analogue values.

I'm trying to understand why that's the case, and if that could be a bug?

I had ...

Go to advanced search