This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VH-Q1: Tresos Dio MCAL configuration (WKUP_GPIO0_69) leads to Det error when used for writing

Part Number: TDA4VH-Q1

Dear TI Support,

We encountered an issue with the Dio Mcal config which is generated in Tresos for our custom hardware and needs. The issue is, that the even though the port for WKUP_GPIO0_69 is configured correctly as 2 (Bank4/5, Tresos wouldn't let any other value to be configured anyway), when using this pin to wake up the CAN transceiver (just like in the J784S4 Evaluation kit), we receive a DET error with the following IDs (--> Dio invalid channel):

From the call stack we can see that this happens when Dio_isReservedPin() is called and returns TRUE, which means the pin is reserved and can't therefore be used.

However, this Dio_ReservedPinList structure is generated by Tresos and is part of Dio_Lcfg.c. The condition that leads to the return value being TRUE is Dio_ReservedPinList[i].reservedPinStart <= pinNum where pinNum is our pin which we want to write --> 69 and reservedPinStart being 32. Obviously this condition is true so no wonder that this is the behavior we see.
The condition before (Dio_ReservedPinList[i].regNum == regNum) is true because regNum is 0.

I compared the DioReservedPinList from our generated Dio_Lcfg.c and the demo config from mcuss_demos:
(Left is the demo Mcal config, right is our generated config for our hardware)

Basically the difference that is the reservedPinStart being 84 in the demo config and 32 in our generated config, this is where the above mentioned 32 comes from.
When we test the same code with the demo config instead, then the Det error is not thrown and the GPIOs are written as they should, because the reservedPinStart values from the demo config seem to be "more correct".

Now the question is, how can those values be influenced from Tresos to be generated in a way that we don't get Det errors anymore? I tried to modify the SOC variant and many other things in Tresos but it seems that no setting will change those reservedPinStart values.

Is this a problem in the Tresos generator? Or is there maybe a newer version of the xdm files we are not aware of? We use Tresos 24.0.

Please help to understand and resolve this issue. Thank you very much in advance!

Best regards.