AURIX™ Forum Discussions

Hi I'm using infineon tc375 chip on my board.

My board has no problem debugging my board with ads v1.9.4 but I had updated to  v1.9.16  today morning and I have debugging start problem.  

But I got below error when start debugging with internal ADS's debugger(titled with TASKING C/C++ Debugger). 

"Loading Failed: Without direct access, flashing is not possible if the target is running."

When I start debugging with WINIDEA, below error is popped up and Cannot go next step after Emulation start step.

"An internal error occurred during: "Launching Control_board_final_code_for_PFC_working (1)".
ICONNECT_E_ERROR: Error occurred while performing the requested operation. / Emulation start failed: Error : Unable to connect to the debug module. / isys::CSessionCtrl::begin_program() failed! winIDEA error: [WrapperBase.cpp, 84]"

Can anybody give me some solution about this? 

+)

When I start WINIDEA and in progress section, I got below messages

"Running Emulation Initialization
Support for Infineon miniWiggler is provided for evaluation and non-commercial use.
LOADING C:\Users\HALAB_G\AURIX-v1.9.16-workspace\workspace_LSI\Control_board-PFC_LSI_working\Control_board_final_code_for_PFC_working\Debug\Control_board_final_code_for_PFC_working.elf
EMULATION Initial debug frequency set
EMULATION Asserting reset
EMULATION Couldn't connect to SoC
EMULATION Reset is INACTIVE
EMULATION Connected to SoC/core(s)
EMULATION Finished connecting to SoC
EMULATION Releasing reset
EMULATION Reset is INACTIVE
EMULATION Initialization script (if any) done
EMULATION Final debug frequency set
EMULATION SoC ID match OK
SoC Detected device: TC370 series, rev. AA
EMULATION STARTED
Running Loading C:\Users\HALAB_G\AURIX-v1.9.16-workspace\workspace_LSI\Control_board-PFC_LSI_working\Control_board_final_code_for_PFC_working\Debug\Control_board_final_code_for_PFC_working.elf
Emulation start failed: Error : Unable to connect to the debug module."

Hi,

    My math model had many global variables in dsam, and ADS will auto extend and put these variables to psram, but these variables of psram always abnormal, for example as below code section, in this model I must get "1", but I always get "0", when I debugging this scetion, I found Test_Memory become 1 to 0, it's incorrect.

But when I move this variable from psram to other dsram, I will get correct result of "1", have any advices?

Thanks

uint8 Test_Memory=1;  //Psram

if(Test_Memory)
    return 1;
else
    return 0;  // Always return 0, incorrect and Test_Memory abnormal
///////////////////////////////////////
uint8 Test_Memory=1;  //Move to Dsram

if(Test_Memory)
    return 1;  // return correct value
else
    return 0;