We found that the "Reserved There is a problem with the area "for customer/application usage". When we tested, we wrote data to 0x1B000050~0X1B000058, and the program ran normally. However, when we tested writing the same data to 0x1B000048~0x1B00004F, the program worked abnormally and a periodic reset occurred. After testing, it was necessary to add a delay of several tens of milliseconds before the clock was initialized to run normally. In this regard, we believe that writing data to 0x1B000048~0x1B00004F will have an unknown impact on the operation of S32K3. So what addresses in the UTEST area can our users use at will? Can you give some suggestions? Thank you!
The UTEST area(0x1B00_0048-0x1B00_007F) is programmable by the Application. Hence the description in HSE_b RM is incorrect and it will be updated in the upcoming version v2.4.
According to the latest feedback from HSE team, they speculate that another HSE write operation was executing when APP was programming data at 0x1b00_0048 - 0x1b00_004f simultaneously would cause this issue.
So the customer can try to add below check and also wait for HSE_STATUS_INIT_OK, before writing into the UTEST area.
