TMS320F28379S: Continuing with my custom board, same issue.

Hi,

Please allow me to get back you about this tomorrow.

Best Regards,

Ben Collier

Thank you very much!

Hi,

OLEG KOBRIN said:

So, any call to SysCtl_enablePeripheral() leads to board reset

This is not expected under normal conditions

Can you check the RESC and NMISHDFLG registers to see what caused the XRSn 

Thanks

Of course.

Tomorrow will check.

RESC register has TRSTn_pin_status and XRSn_pin_status bits set

NMISHDFLG is zero

Okay that means you dont have any NMIWD reset

Can you put snapshot of RESC register here ? There is no WDRSn ?
Are you sure your voltages are stable and no Brownout reset is possible ?

Thanks

I cannot now, sorry, the device is busy. But I am sure only 2 bits is set. Voltages are ok, I checked it out.

Hi,

In case of XRSn we should see at least one of those bits set unless the device is power cycled then only it would get erased.
We would need to get this info for further debug.

When you are bale to get the info next time for RESC capture also make sure you monitor voltage on scope with trigger so we are sure no power cycle has occurred intermediately 

Thanks

Ok, I see, I had trigger on XRSn pin, and no voltage drop was seen in the same time. I should set trigger on core voltage then. I will submit results.

So, yes, there is a drop. But question is, why it is happening on any write to peripheral enable register? Even then the particular periferal is already enabled!

Hi,

If the peripheral is already enabled, I dont expect the drop.
But if the peripheral is not enabled and you turn it on that will increase current consumption and subsequently if the voltage supply is not able to supply the current then it can cause voltage drop.

Thanks

The first call to SysCtl_enablePeripheral()  enables CLA. When I check the register content before this call I see the bit for CLA in the register is already 1. But when I step over the call, resset occurs.

Let me try this on my end and get back.

Thanks.