You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firmware/OCWare Describe the issue found
There's an interesting hard fault that occurs after running UpdateEMAC(). It seems that the issue is related to the system reset that occurs after the update completes. It is also very timing sensitive - you have to perform the update at just the right time (for some reason it manifests itself more frequently in the rev-c-master branch).
Unfortunately, the CCS tools are mostly useless for pinning down this bug. It's not clear to me how UpdateEMAC() resets the system, so it's possible that it's not a complete system reset, but that would be quite strange. My guess is that some interrupt doesn't get cleared up after the reset, triggers, and then wreaks havoc on the system (seems that some critical areas get overwritten). I hope that it's simply that some peripheral isn't getting cleaned up on reset instead of our code not respecting memory boundaries.
The good news is that a simple SysCtlReset() seems to fix it all up, so it's not super severe at this moment.
Please provide all necessary steps to reproduce the issue
Build Rev_C_Changes (fa51bd4)
With board off or Tiva held in reset by debugger, start EMAC update in LM Flash Programmer
Run Tiva - update will begin shortly after initializing the external battery charge controller
Update will complete (debug logs will restart with the "OPENCELLULAR" splash)
Code should fail at some point during this execution
The text was updated successfully, but these errors were encountered:
Product: (OC-SDR, OC-LTE, OC-LTE, OC-Power, others)
OC-SDR
Category: (Hardware, Software/stack, Firmware/bootloader, Documentation)
Firmware/OCWare
Describe the issue found
There's an interesting hard fault that occurs after running UpdateEMAC(). It seems that the issue is related to the system reset that occurs after the update completes. It is also very timing sensitive - you have to perform the update at just the right time (for some reason it manifests itself more frequently in the rev-c-master branch).
Unfortunately, the CCS tools are mostly useless for pinning down this bug. It's not clear to me how UpdateEMAC() resets the system, so it's possible that it's not a complete system reset, but that would be quite strange. My guess is that some interrupt doesn't get cleared up after the reset, triggers, and then wreaks havoc on the system (seems that some critical areas get overwritten). I hope that it's simply that some peripheral isn't getting cleaned up on reset instead of our code not respecting memory boundaries.
The good news is that a simple SysCtlReset() seems to fix it all up, so it's not super severe at this moment.
Please provide all necessary steps to reproduce the issue
Build Rev_C_Changes (fa51bd4)
With board off or Tiva held in reset by debugger, start EMAC update in LM Flash Programmer
Run Tiva - update will begin shortly after initializing the external battery charge controller
Update will complete (debug logs will restart with the "OPENCELLULAR" splash)
Code should fail at some point during this execution
The text was updated successfully, but these errors were encountered: