• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 642 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

RM44L520: Debugging and tracing recommendations

Audun Knudsrod
Intellectual 300 points
Part Number: RM44L520
Other Parts Discussed in Thread: SEGGER, HALCOGEN

Hi, I am having some problems understanding how to set up my tools for the RM44L520APGET

Background

  • This is the first time I am working with a TI controller
  • This is first time I am working with a Cortex-R
  • This is the first time I am using JTAG instead of the Cortex-M Debug interface
  • Our first prototype of a new product has been designed with a JTAG connector and the RM44
  • To do some development I also have a launchpad, the XL2-RM46.
  • The final product willl be IEC 61508 SIL 2 certified
  • I am using the J-Link Plus from Segger.
  • My company uses uVision a lot, so I am trying to do that here as well
  • I am using TI's HALCoGen to generate code for both platforms, including the FreeRTOS setup for the RM46
  • I am open to using other tools and IDEs, but I have a preference for third-party tools (like working with MCUs from two vendors but only having one IDE).

List of issues/questions

  1. Is Keil's support of this device (RM44) somewhat... lacklustre? (Lack of device support, hard to get information from the website)
  2. The FreeRTOS demo on RM46 crashes after I call vTaskStartScheduler()  (It goes to the prefetchEntry interrupt vector (sys_intvecs.asm, line 59.).).
  3. I am trying to debug the above problem in uVision but I cannot use things like the System Viewer to view system error flags etc.
    Is this just not available or have I missed out on some configuration? (I can step through the code and view the registers, but I cannot see the peripherals)
  4. Which debug connectors and tools gives me "the most" ability to debug the chip?
  5. Is this a device that requires a lot of TI tools to be debugged/analyzer properly (TI connector, TI debugger, TI IDE), or can I use standard gear and still do my stuff? (uVision/IAR, JTAG, etc).

So I think issue 2 can be solved by solving issue 3, and issue 4 and 5 are closely related.

Thank you for your attention.

  • 0
    TI__Guru 59540 points
    Hello Audun,

    In general, all of the IDEs that support the Hercules device family that I aware of are given here: www.ti.com/.../tools-software.page

    I do apologize for your experiences with the KEIL tools but, unfortunately, I am unable to confirm to what level they support the device and the convenience of their support for our devices. I have had associates use the tools without too many issues that I am aware of but that was some years back. Perhaps if they have anyone monitoring this forum, they can respond to your concerns.

    The Green Hills compiler is a complete unknown to me as I have not used it and I don't know of anyone that has used it.

    The predominate IDEs used for Hercules are the IAR IDE and the TI CCS IDE.

    If you're set on the thrid party IDE, IAR is a good choice and, I believe, offers a certified compiler as well. Most of our development tools for code generation such as Halcogen, There is a known issue with the SafeTI diagnostic libraries and IAR which should be repaired in the not too distant future, but most of our tools have been designed to work with all of our supported IDEs including IAR.

    In regard to the JTAG probe, it is dependent on the drivers included with the IDE and you would need to check with those tools to be certain the Seggar JLINK plus is upported.

    To address your KEIL issue with debug, I know that CCS requres a memory map to be setup/loaded which is done when you setup the project in CCS (its associated with the chosen target selected). Does Keil require the same?

    In FreeRTOS, I think you need to insure the permissions are configured correctly for any task that you instantiate so perhaps it is a task permissions issue that is resulting the in the exception? If you can see your CPU registers in your KEIL view, try checking the LR register to see where you were executing prior to the exception. This should give you some idea of what might be causing the issue. be sure that the tool is programming both the program flash and the ECC if ECC is enabled. An unprogrammed ECC flash would result in a multibit error and exception if the errors haven't been setup for export yet.
  • 0
    TI__Guru**** 186226 points
    Hello Audun,

    Keil uVision is not supported on this device (I could not find this device on uVision 5)..

    www.ti.com/.../tools-software.page
    This link lists the IDEs supports on this device: TI CCS, IAR Workbench, Greenhill, etc

    Regards,
    QJ