RM46L852: Learning the Board

Bavi U M

Prodigy 30 points

Part Number: RM46L852
Other Parts Discussed in Thread: HALCOGEN,

Hello Team,

I am new to TI. i just started learning HERCULES MCU's because i need this for my Project.

i bought the LaunchPad Board RM46L852.and started learning by using CCS and HALCOGEN.

i did small program (below)

int main(void)

{

int counter = 0;

++counter;

return 0;

}

check this e2e forum for the error i am also haviing the same problem

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1234918/rm48l540-debugger-consistently-crashes-at-0x00000004-right-after-start/4676608?tisearch=e2e-sitesearch&keymatch=rm48l540#4676608

as per this i have to generate the halcogen code and then debug

i have generated the code and then i am getting the following error after flashing

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0 due to System Reset
CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0 due to System Reset
CortexR4: Error: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.11.0.00128)
CortexR4: Unable to determine target status after 20 attempts
CortexR4: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

and i gone through with this website also https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

and changed the jtag clock speed but no luck.

i got stucked here kindly help

Thanks and Regards

Bavi U M

over 2 years ago

0 jagadish gundavarapu over 2 years ago

TI__Guru 73236 points

Hi Bavi U M,

Here is the basic LED tutorial example:

Hercules Tutorial: Turning on the LEDs - YouTube

Please refer the above video, generate the code from HALCoGen and do the necessary settings in CCS by following above video.

Thanks & regards,
Jagadish.

0 Bavi U M over 2 years ago in reply to jagadish gundavarapu

Prodigy 30 points

Hai jagadish,

Thanks for the Replay.

as i mentioned i already generated the Code and try to debug. for the generated code only i am getting this error for your reference i had attached the code and Error screenshot kindly check.

i am hoping for the solution

and this is my main.c

/* USER CODE BEGIN (0) */
#include "het.h"
/* USER CODE END */

/* Include Files */

#include "sys_common.h"

/* USER CODE BEGIN (1) */
/* USER CODE END */

/** @fn void main(void)
*   @brief Application main function
*   @note This function is empty by default.
*
*   This function is called after startup.
*   The user can use this function to implement the application.
*/

/* USER CODE BEGIN (2) */
/* USER CODE END */

void main(void)
{
/* USER CODE BEGIN (3) */

    gioSetDirection(hetPORT1, 0xFFFFFFFF);

    gioSetBit(hetPORT1, 0,1);
    gioSetBit(hetPORT1, 17,1);
/* USER CODE END */

}

/* USER CODE BEGIN (4) */

void gioNotification(int bit)
{
    return;
}

void esmGroup1Notification(int bit)
{
    return;
}
void esmGroup2Notification(int bit)
{
    return;
}

/* USER CODE END */

kindly check i hope for the solution

Thnaks

Bavi U M

0 jagadish gundavarapu over 2 years ago in reply to Bavi U M

TI__Guru 73236 points

Hi Bavi,

Can you please zip the complete project and attach it?

If you don't know how to attach complete project, please refer below thread:

(+) TMS570LC4357: TMS570LC43X - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

Thanks & regards,
Jagadish.

0 Bavi U M over 2 years ago in reply to jagadish gundavarapu

Prodigy 30 points

7115.test1.zip

Hai Jagadish,

pls find the Zip file in the attachment

Thanks

Bavi U M

0 jagadish gundavarapu over 2 years ago in reply to Bavi U M

TI__Guru 73236 points

Hi Bavi,

I went through your code, and it looks fine. I understood it is not a software bug and it looks like hardware error.

Can you please try the steps in the below thread:

(+) Error connecting to the target - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

If you were unable to perform the steps mentioned in above thread, then we can setup a call and do the live debugging.

Thanks & regards,
Jagadish.

0 Bavi U M over 2 years ago in reply to jagadish gundavarapu

Prodigy 30 points

hai Jagadish,

Thanks for the detailed Response Page.

I have gone through the Steps i am able connect icepick and DAP.but still the error persist

please check the attached Screenshot.and kindly let me know where am i wrong

Thanks

Bavi U M

0 Bavi U M over 2 years ago in reply to Bavi U M

Prodigy 30 points

Hai,

i forget to attach one more screenshot.

des: when i press the green button in the above screenshot the following error is coming (in the attachment below)

kindly help

Thanks

Bavi U M

0 jagadish gundavarapu over 2 years ago in reply to Bavi U M

TI__Guru 73236 points

Hi Bavi,

Apologies for the delay!

Did you try several retries as given in the above thread?

And also could you please check where exactly the code hanging after connecting to the Icepick.

For example:

In above example you can see the code always branching to the address 0x00006de4 in disassembly code.

Now open the map file, which is present in the debug folder of the project and there you can search this address like as below

Now you could see the function where the execution was stuck.

Thanks & regards,
Jagadish.

0 Bavi U M over 2 years ago in reply to jagadish gundavarapu

Prodigy 30 points

Hai Jagadish,

as mentioned i tried for around 50 Times. please check the below Screenshot for the error and where it is halting

i did stepinto and came to know that when the cursor comes here (blue line in the screenshot) the error is coming please let me know further

Thanks and Regards

Bavi

0 jagadish gundavarapu over 2 years ago in reply to Bavi U M

TI__Guru 73236 points

Hi Bavi,

Can you please test with below attached code and let me know the result:

LED_Blinky_Example_RM46_Launchpad.zip

After testing with above code please let me know whether the controller still producing error at "CLKTEST" instruction or not?

Thanks & regards,
Jagadish.

0 Bavi U M over 2 years ago in reply to jagadish gundavarapu

Prodigy 30 points

Hai Jagadish,

i Tested the above Code. This is also problem with Clock

void trimLPO(void)
{
uint32 u32clocktestConfig;
/* Save user clocktest register configuration */
u32clocktestConfig = systemREG1->CLKTEST;
/* USER CODE BEGIN (4) */
/* USER CODE END */
/*The TRM states OTP TRIM value should be stepped to avoid large changes in the HF LPO clock that would result in a LPOCLKMON fault. At issue is the TRM does not specify what the maximum step is so there is no metric to use for the SW implementation - the routine can temporarily disable the LPOCLKMON range check so the sudden change will not cause a fault.*/
/* Disable clock range detection*/
systemREG1->CLKTEST = (systemREG1->CLKTEST
| (uint32)((uint32)0x1U << 24U))
& (uint32)(~((uint32)0x1U << 25U));

This function in system.c

the same error i am getting when i stepinto systemREG1->CLKTEST = (systemREG1->CLKTEST

Thanks

Bavi U M

0 QJ Wang over 2 years ago in reply to Bavi U M

TI__Guru**** 198766 points

Hi Bavi,

The CLKTEST register should to written un privileged mode. If you are using the HALCoGen generated initialization code, it should be fine to program this register since the device is in system mode.

Please double check the part number of Hercules MCU on the launchpad. I'd like to make sure it is RM46L852 device.

0 QJ Wang over 2 years ago in reply to QJ Wang

TI__Guru**** 198766 points

I am sorry for the typos in my lresponse.

The CLKTEST register should be written in privileged mode.