Did you load the new values from the firmware you uploaded with M502
? If not, that might be your problem. See "M502 will reset all configurable settings to their "factory defaults", which settings are those?".
When you upload a firmware, this is done through a so-called binary hex file. In this file, stored in memory of the micro-controller, the complete "program" is stored as configured by your code editor (compiled, hence a binary file). Note that the user of the "program" is allowed to change values of certain parameters1), the changes are stored in a different part of the memory that is not overwritten when a new firmware is uploaded. You manually have to get the "set" values from your new firmware file to store these into the "working memory". Please send the M502
and the M500
G-codes to get and store the values from the firmware.
1) Do remember the inability to store custom parameters in certain older versions of Marlin in combination with certain printer controller boards (e.g. the SKR line of boards), but, this is fixed in the recent versions, storage e.g. is done on the SD card. For that reason the memory storage above is not called EEPROM but the "working memory", i.e. is doesn't have to be an EEPROM storage.
M502
? If not, that might be your problem. See "M502 will reset all configurable settings to their "factory defaults", which settings are those?". $\endgroup$