• State
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 40 views
  • Users 0 members are here
Support feedback
Options
Options
Related

J784S4XEVM: Open Firewall 2465

Mathuran Kandeepan
Prodigy 60 points

Part Number: J784S4XEVM

Hello,

I am working on the J784S4XEVM board and currently focusing on the Firewalls.

I would like to know if it is possible to open Firewall 2465 (for DEBUGSS_WRAP0) owned by TIFS?
If so, which SCI message open it?

You can find more information here:
https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j784s4/firewalls.html

Thanks, 

  • 0
    TI__Guru 62263 points

    Hi Mathuran,

    Firewall expert is currently out, and will be back tomorrow. Please expect response back tomorrow.

    Regards,

    Takuma

  • 0
    TI__Guru 71015 points

    Hi Mathuran,

    Mathuran Kandeepan said:
    I would like to know if it is possible to open Firewall 2465 (for DEBUGSS_WRAP0) owned by TIFS?
    If so, which SCI message open it?

    If the firewall id region is owned by TIFS it cannot be configured, since the debug subsystem is owned by TIFS so does the firewall configuration is done.

    May i know the reason for reconfiguring this?

    Regards
    Diwakar

  • 0 in reply to Diwakar Dhyani
    Prodigy 60 points

    Thank you for your response.

    To clarify our requirement, we need to configure the CoreSight component via software using the mcu1_0 directly, rather than relying on external JTAG access.
    We previously implemented this successfully on GP devices by taking control of the first M4F core and manually disabling the firewall. However, we have encountered limitations when attempting the same process on HS devices.

    For development and validation purposes, it is critical for us to trace code execution via CoreSight and the TI TBR.
    The current restrictions imposed by the TIFS are hindering our testing phase. Is there a documented procedure or a workaround to bypass these security limitations for development/test builds?