Broadcom_BCM53014.JLinkScript 2.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647
  1. /*********************************************************************
  2. * SEGGER Microcontroller GmbH *
  3. * Solutions for real time microcontroller applications *
  4. **********************************************************************
  5. * *
  6. * (c) 1995 - 2018 SEGGER Microcontroller GmbH *
  7. * *
  8. * www.segger.com Support: support@segger.com *
  9. * *
  10. **********************************************************************
  11. ----------------------------------------------------------------------
  12. Purpose : J-Link script file for Broadcom BCM53014 device.
  13. - Handles connect pre-configuration
  14. ---------------------------END-OF-HEADER------------------------------
  15. */
  16. /*********************************************************************
  17. *
  18. * Public code, functions which are called by the DLL
  19. *
  20. **********************************************************************
  21. */
  22. /*********************************************************************
  23. *
  24. * InitTarget
  25. */
  26. void InitTarget(void) {
  27. int v;
  28. //
  29. // The broadcom BCM53014 has an incorrect CoreSight ROMTable in it,
  30. // so auto-detection of CoreSight components (inclusive base address of core debug registers) is not possible
  31. // and needs to be pre-configured via a J-Link script
  32. // More info about how to specify J-Link script files for execution in various IDEs etc., please refer to UM08001, section "Executing J-Link script files"
  33. //
  34. // The rest of the J-Link generic auto-detection can be performed (determining JTAG devices etc.). Therefore, we only need to pre-configure the CPU + base address of the debug registers
  35. //
  36. Report("J-Link script: Broadcom BCM53014 J-Link script");
  37. CPU=CORTEX_A9;
  38. CORESIGHT_CoreBaseAddr = 0x19010000;
  39. //
  40. // Manually configure which APs are present on the CoreSight device
  41. //
  42. CORESIGHT_AddAP(0, CORESIGHT_CUSTOM_AP);
  43. CORESIGHT_AddAP(1, CORESIGHT_APB_AP);
  44. CORESIGHT_IndexAPBAPToUse = 1; // For Cortex-A/R devices, always an APB-AP needs to be present since this is the interface for accessing the debug registers. Pre-select the APB-AP for this device
  45. }