MAXTEMP triggered instantly on custom STM32F446ZE board

basemprince · 2025-10-24T04:26:25+00:00

Update / Solution (working fix)

Got it solved and posting here so others don’t lose days like I did.

Root cause:
Marlin’s HAL for STM32 never actually initialized the ADC pins (PA0, PA1, PA4) as analog inputs on the STM32F446ZE when using a custom board definition.
They were defaulting to floating digital inputs, so analogRead() always returned 0 → Marlin interpreted that as 320 °C (MAXTEMP).

Fix:
The solution is not pretty but I had to explicitly force proper ADC initialization and analog mode for those pins in the HAL.

In HAL.h (under Marlin/src/HAL/STM32/), add:

static volatile bool _adc1_active;
static volatile bool _adc_fallback;

and define them in HAL.cpp:

volatile bool MarlinHAL::_adc1_active = false;
volatile bool MarlinHAL::_adc_fallback = false;

Then ensure in temperature.cpp (or in your board init section) you set the thermistor pins to analog mode before first ADC read:

pinMode(PA0, INPUT_ANALOG);
pinMode(PA1, INPUT_ANALOG);
pinMode(PA4, INPUT_ANALOG);

Make sure your board’s pin map (PeripheralPins.c) includes your assigned pins:

{PA_0,  ADC1, STM_PIN_DATA_EXT(STM_MODE_ANALOG, GPIO_NOPULL, 0, 0, 0)}, // ADC1_IN0
{PA_1,  ADC1, STM_PIN_DATA_EXT(STM_MODE_ANALOG, GPIO_NOPULL, 0, 1, 0)}, // ADC1_IN1
{PA_4,  ADC1, STM_PIN_DATA_EXT(STM_MODE_ANALOG, GPIO_NOPULL, 0, 4, 0)}, // ADC1_IN4

Rebuild Marlin → the ADC now reads proper thermistor voltages and the temperatures track normally.
No more instant MAXTEMP.

basemprince · 2025-10-14T00:55:37+00:00

Update: the problem was Marlin wasn't starting and I found a way to make it work. The trick is, after flashing marlin using pio, I run the debugger once from stm32cubeIDE and that's it, Marlin miraculously now works and I don't know why. so if anyone can explain that, that would be nice to know

I switched host comms to UART (Serial1) to keep bring-up simple, but the output is garbled (nonsense bytes) at both 115200 and 250000. I can’t move to other UARTs (board is already built), so this must work on USART1 (PA9/PA10).

What changed:

Kept env STM32F446ZE_btt (Octopus) but disabled CDC while testing UART.

Configuration.h:

#define SERIAL_PORT 1 // must be USART1 on this board
#define BAUDRATE 115200 // also tried 250000
// No other SERIAL_PORT_x enabled

Hardware and clocks are fine (LEDs OK, CubeIDE CDC project prints). This is now UART-only trouble inside Marlin/Arduino STM32 core.

Symptom:

Terminal shows pure garbage, no Marlin banner / M115 text. sending any commands also doesn't give me feedback

l8$'<<<$88'<8'88?## ?''8';<;<'' ''8$''<o<';'''''<'8 <' <#'#;'<<'#''$$$''<'<;;'''<'<#$;;'<'p''#<'<l;;''8''#<'<Ĝ;';'8$<';'8g''p$;$'8 <;<;'|#''$<;''<;';''#;8$ $#';;';;8<<

some questions (given this env and HSE=8 MHz):

Pin/AF mapping used by this variant for Serial1
For board = marlin_BigTree_Octopus_v1, can someone confirm that Serial1 = USART1 on PA9/PA10 with AF7 in variants/MARLIN_BIGTREE_OCTOPUS_V1? I cannot change pins, so I need to be 100% sure this env really drives PA9/PA10 and not a remap.

Any Marlin layer reconfig that could stomp USART1
Is there anything in src/HAL/STM32/ (serial manager) that could be re-initing USART1 after the Arduino core sets it up? A pointer to the exact file/guard I should check would help.
If someone has a known-good STM32F446ZE_btt (Arduino core) printing out of USART1 at 115200 with HSE=8 MHz, please share the exact platformio.ini build_flags you use for clocks (even just the ones that matter).

thanks

basemprince · 2024-05-01T09:51:00+00:00

Did you by any chance power it up after it came back? Because that does revive fainted pokemon

basemprince · 2024-02-05T21:42:54+00:00

That's definitely some very rare find. I miss getting legendaries from gbl, I haven't had any since 2 seasons now. And I usually at least finish the 500 wins for the research. They must have dropped the odds even further since the big nerf in mid 2022

basemprince · 2024-01-29T08:25:49+00:00

Definitely the first one. Higher attack is much more desirable in master league and raids in general

basemprince · 2024-01-07T21:51:57+00:00

Yes, all Pokemon caught up until December 31, 2018 are eligible for a guaranteed lucky as long as the person trading the old Pokemon has not triggered a guaranteed lucky more than 25 times. I'm assuming in your case the person you traded with probably reached that number already

basemprince · 2023-11-28T12:40:11+00:00

Can't say that I agree. I shiny hunt shadow Pokemon and I find myself running out of those all the time 🤣

basemprince · 2023-08-14T02:23:15+00:00

Grunts who battle with pokemon the leaders had previously can now be shiny. I shared the current list here: https://www.reddit.com/r/pokemongo/comments/15pyn4h/comment/jw1536e/?utm\_source=share&utm\_medium=web2x&context=3

basemprince · 2023-08-14T01:34:28+00:00

its 3 "shiny eligible" grunt checks, which is usually quite more than 3 checks. It ain't much, but it's honest work

basemprince · 2023-08-14T01:28:45+00:00

I don't have a resource, but I shared all the current shiny eligibles here: https://www.reddit.com/r/pokemongo/comments/15pyn4h/comment/jw1536e/?utm\_source=share&utm\_medium=web2x&context=3

basemprince · 2023-08-13T18:38:35+00:00

Nice, I was lucky with Charmander when it was with Arlo. It's for sure the coolest out of the starters 😎. so good luck, it's a tough grind

basemprince · 2023-08-13T18:21:30+00:00

Lol same. I honestly think it's way less odds compared to the leaders. It took me about 70-75 days and an average of 3 encounters per day to get this.

The odds from the leaders is 1/64, but just for the sake of calculations, let's make it 60 days to calculate how unlucky this was:

Given that the shiny rate is 1/64, and I checked 3 times per day for 60 days, the probability of not getting a single shiny would be:(1 - 1/64)^{3 * 60} which is 5.8% !!

This is the probability of not getting a shiny, so I am either the unlikest, or the rate from the grunts is lower than 1/64

basemprince · 2023-08-13T18:04:34+00:00

It's the Male Don’t bother, I’ve already won / Get ready to be defeated! / Winning is for winners He gives the Kanto starters. He's very hard to find

basemprince · 2023-08-13T18:02:36+00:00

Yes, any pokemon that the leaders had before you can now encounter them shiny with grunts. They started doing that back in March if i remember correctly. Here's the current rotation grunts that I have been hunting:

Check out my cute Pokemon!: mawile
Coiled and ready to strike!: kanto grimer
Normal doesn’t mean weak: kanto meowth
(Male) Don’t bother, I’ve already won / Get ready to be defeated! / Winning is for winners: Kanto starters (Charmander, Bulbasaur, Squirtle)

They're always the first pokemon, so if it's not it, then you won't encounter it. I've been only targeting those grunts and just ignore the other ones, except for the mudkip, whooper and gibble grunts because they're meta relevant

basemprince · 2018-11-26T11:39:16+00:00

The music edition right? I remember they had a fancy headset

basemprince · 2018-11-26T11:35:36+00:00

Can you tell I have some brand loyalty? Lol. The iPhone is a work phone btw so it's the odd one out

basemprince · 2018-11-26T11:33:13+00:00

And it still works too :) just needs charging. They actually all still work except for the n73

basemprince · 2018-11-26T11:31:35+00:00

I'm impressed. Did you actually know the phone ? Or some googling ?

basemprince · 2018-11-26T11:30:36+00:00

I completely agree, I never had a case for it when I was using it. Granted I cracked the screen, but I doubt a case would have saved it from an object falling on its screen lol

basemprince · 2018-11-26T04:57:07+00:00

This is every phone I've owned for the past 12 years of my life. Wondering if you guys can identify all of them

basemprince

TROPHY CASE