Not applicable
Jun 18, 2013
05:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 18, 2013
05:45 AM
Hi All,
Quite often when I click the 'Resume' (Play) button in the TASKING Debug environment in DAVE I get the following error...
No source available for "0x0() "
Sometimes if I exit and re-enter the TASKING Debug environment it is OK.
Any help would be much appreciated.
Aaron
Quite often when I click the 'Resume' (Play) button in the TASKING Debug environment in DAVE I get the following error...
No source available for "0x0() "
Sometimes if I exit and re-enter the TASKING Debug environment it is OK.
Any help would be much appreciated.
Aaron
- Tags:
- IFX
14 Replies
Not applicable
Jun 20, 2013
02:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 20, 2013
02:38 AM
Hi Aaron,
I had experienced this before. Usually i will try to stop the debugger and restart again. You may need to restart several times...
Best regards,
Zain
I had experienced this before. Usually i will try to stop the debugger and restart again. You may need to restart several times...
Best regards,
Zain
Not applicable
Jun 20, 2013
03:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 20, 2013
03:27 AM
Thanks Zain, I am indeed stopping and restarting the debugger. Hopfully I'll find a pattern or more clues to help find the root cause soon.
Best regards
Aaron
Best regards
Aaron
Not applicable
Jun 21, 2013
03:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 21, 2013
03:08 AM
Just a small update to this problem. I can recover by following the sequence below...
1) No source available for "0x0() " is displayed
2) Click on 'Debug' button again. Code is downloaded to target device again
3) Click on 'Resume (play) button.
4) If error message re-appears, repeat steps 2 and 3. Normally it takes 2 or 3 tries to recover.
1) No source available for "0x0() " is displayed
2) Click on 'Debug' button again. Code is downloaded to target device again
3) Click on 'Resume (play) button.
4) If error message re-appears, repeat steps 2 and 3. Normally it takes 2 or 3 tries to recover.
Not applicable
Jun 28, 2013
03:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 28, 2013
03:16 AM
Would someone from Infineon please help with this problem. I am wasting 50% of my available time trying to run in debug mode and our business cannot afford the delay to a critical project.
Thank you
Aaron
Thank you
Aaron
Jun 28, 2013
08:38 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 28, 2013
08:38 AM
I discussed this topic with Altium, today. There is no know issue that the source code is not shown. If the source code is not shown then most like the MCU was executing form a pre compiled library where source code is not available. However in this case the disassembly window should be shown correctly.
When exactly does the “No source available” message appear? Right after download before you have pressed the resume button the first time? Is your debug configuration deviating from the default settings, if yes which one did you change?
According to your description the problem happens quite frequently, is it possible that you provide us the project for analysis of the problem?
When exactly does the “No source available” message appear? Right after download before you have pressed the resume button the first time? Is your debug configuration deviating from the default settings, if yes which one did you change?
According to your description the problem happens quite frequently, is it possible that you provide us the project for analysis of the problem?
Not applicable
Jul 01, 2013
09:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 01, 2013
09:44 AM
Hi Georg,
Thank you for your reply.
The “No source available” message appears after download when I press the 'Resume' button. If I repeat the process of pressing the 'Debug' button then the 'Resume' button, after a number of attempts the “No source available” message does not appear and I can run the code.
I have checked the debug configuration and it looks OK, I haven't intentionally changed anything from the default settings.
I have a feeling the problem may be related to USB connections / App and a 'race condition' in DAVE. I also see the “No source available” message appear momentarily on projects that run OK.
The project code is confidential so I will send you a link via email to download it. Please try and run the debugger many times as it may work initially.
Thanks again
Best regards
Aaron
Thank you for your reply.
The “No source available” message appears after download when I press the 'Resume' button. If I repeat the process of pressing the 'Debug' button then the 'Resume' button, after a number of attempts the “No source available” message does not appear and I can run the code.
I have checked the debug configuration and it looks OK, I haven't intentionally changed anything from the default settings.
I have a feeling the problem may be related to USB connections / App and a 'race condition' in DAVE. I also see the “No source available” message appear momentarily on projects that run OK.
The project code is confidential so I will send you a link via email to download it. Please try and run the debugger many times as it may work initially.
Thanks again
Best regards
Aaron
Not applicable
Jul 25, 2013
01:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 25, 2013
01:00 AM
Some good news I hope.
Today I removed a delay between the DAVE_Init() and USBVC001_Init() functions and I have not seen the "no source error" since. The original code copied from the USBVC001_VCOMSerial_Example1 was...
I have changed this to...
Now the debugger always works. I can pause, reset, resume, anything I like and I don't see the error.
Thank you.
Best regards
Aaron
Today I removed a delay between the DAVE_Init() and USBVC001_Init() functions and I have not seen the "no source error" since. The original code copied from the USBVC001_VCOMSerial_Example1 was...
DAVE_Init(); // Initialization of DAVE Apps
delay(12000000); // time between DAVE_Init() and USBVC001_Init to to allow a save enumeration process
/* Initialization of the USBVC001 App */
USBVC001_Init();
I have changed this to...
DAVE_Init(); // Initialization of DAVE Apps
/* Initialization of the USBVC001 App */
USBVC001_Init();
Now the debugger always works. I can pause, reset, resume, anything I like and I don't see the error.
Thank you.
Best regards
Aaron
Not applicable
Oct 26, 2013
07:53 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 26, 2013
07:53 AM
Hi All,
I am facing one challenge in DAVE3 tool while programming the xmc4500 controller.
When clicking on Debug button
1. Erase program
2. Download program
3. Verify program
Above three tasks are done properly but after that message displayed as "No source available for "" ".
Means instruction pointer is not at the first instruction of main and resume button is already disabled.
Please help me. I am attaching the snapshot after clicking on debug btn.
I am facing one challenge in DAVE3 tool while programming the xmc4500 controller.
When clicking on Debug button
1. Erase program
2. Download program
3. Verify program
Above three tasks are done properly but after that message displayed as "No source available for "" ".
Means instruction pointer is not at the first instruction of main and resume button is already disabled.
Please help me. I am attaching the snapshot after clicking on debug btn.
Not applicable
Oct 27, 2013
02:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 27, 2013
02:08 PM
This is likely caused when the application jumps or returns to address 0x0. It could be a NULL pointer in the wrong place, smashed stack, uninitialized function pointer, over-written structure, take your pick. The projects don't get loaded at 0x00000000, so there is no source code there to view.
You posted another thread about not getting a warning if a user-defined ISR wasn't found. It could be that something isn't being initialized in time given the delay you have. If you must have the delay, try a smaller value.
You posted another thread about not getting a warning if a user-defined ISR wasn't found. It could be that something isn't being initialized in time given the delay you have. If you must have the delay, try a smaller value.
Not applicable
Oct 28, 2013
01:39 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oct 28, 2013
01:39 AM
Hi jfhaugh,
Thank you for your post.
Just to let you know the original post was caused by problems within the USBVC001 app and the fix was to remove a delay given in the USBVC001 example.
My other post regarding not getting a warning if a user defined ISR does not exist is not related to this post at all.
The "No source available at 0x0()" experienced by mohan.patil has the same symptoms but not the same route cause, though as you say it is likely to be an incorrect initialization or pointer error. The Tasking debugger is pretty un-helpful in diagnosing the problem. I have also seen this error randomly when stopping the debugger on perfectly functioning code so I think there is an underlying bug in the debugger too.
Best regards
Aaron
Thank you for your post.
Just to let you know the original post was caused by problems within the USBVC001 app and the fix was to remove a delay given in the USBVC001 example.
My other post regarding not getting a warning if a user defined ISR does not exist is not related to this post at all.
The "No source available at 0x0()" experienced by mohan.patil has the same symptoms but not the same route cause, though as you say it is likely to be an incorrect initialization or pointer error. The Tasking debugger is pretty un-helpful in diagnosing the problem. I have also seen this error randomly when stopping the debugger on perfectly functioning code so I think there is an underlying bug in the debugger too.
Best regards
Aaron
Attachments are accessible only for community members.
Not applicable
Mar 03, 2017
05:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 03, 2017
05:43 AM
I have got same problem for week, before worked correctly, and currently after click debug :
No source available for "(gdb[4].proc[42000].threadGroup[i1],gdb[4].proc[42000].OSthread[1]).thread[1].frame[0]"
and bottom i placed debug log
No source available for "(gdb[4].proc[42000].threadGroup[i1],gdb[4].proc[42000].OSthread[1]).thread[1].frame[0]"
and bottom i placed debug log
02-00000000-00-00001079-003F: T0FC8 001:079 JLINK_Halt() returns 0x00 (0000ms, 0497ms total)
02-00000000-00-00001079-0043: T0FC8 001:079 JLINK_IsHalted() returns TRUE (0000ms, 0497ms total)
02-00000000-00-00001079-0050: T0FC8 001:079 JLINK_ReadReg(R15 (PC)) returns 0x10001018 (0000ms, 0497ms total)
03-00000000-00-00001079-0022: ...Target halted (PC = 0x10001018)
01-00000290-00-00001079-0006: $OK#9a
00-00000290-00-00001080-000E: $qRcmd,676f#2c
03-00000000-00-00001080-0016: Starting target CPU...
02-00000000-00-00001080-0043: T0FC8 001:080 JLINK_IsHalted() returns TRUE (0000ms, 0497ms total)
02-00000000-00-00001084-00C1: T0FC8 001:080 JLINK_GoEx(MaxEmulInsts = -1, Flags = 0x00) -- CPU_ReadMem(4 bytes @ 0xE0001000) -- CPU_WriteMem(4 bytes @ 0xE0001000) -- CPU_WriteMem(4 bytes @ 0xE0001004) (0004ms, 0501ms total)
01-00000290-00-00001084-0006: $OK#9a
03-00000000-00-00001086-001C: GDB closed TCP/IP connection
Not applicable
Mar 27, 2017
03:56 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mar 27, 2017
03:56 AM
i too facing the same problem my code is simple as here
i can not enter into debugging at all.
debugging terminated..on execution.
and all debugging options are inactive "step in","step-out","resume" and all
please help me to debug
i can not enter into debugging at all.
debugging terminated..on execution.
and all debugging options are inactive "step in","step-out","resume" and all
please help me to debug
#include
int main(void)
{
DAVE_STATUS_t status;
int delay_count =0;
status = DAVE_Init(); /* Initialization of DAVE APPs */
if(status != DAVE_STATUS_SUCCESS)
{
/* Placeholder for error handler code. The while loop below can be replaced with an user error handler. */
XMC_DEBUG("DAVE APPs initialization failed\n");
while(1U)
{
}
}
CAN_NODE_MO_Transmit(&CAN_NODE_0_LMO_01_Config);
//CAN_NODE_MO_Receive(&CAN_NODE_0_LMO_01_Config);
/* Placeholder for user application code. The while loop below can be replaced with user application code. */
while(1U)
{
DIGITAL_IO_ToggleOutput(&LED1); //toggles : 1 -> 0 (if initial output level is logic 1)
//Add application code here
for(delay_count = 0;delay_count<0xfff;delay_count++);
DIGITAL_IO_ToggleOutput(&LED1); //toggles : 0 -> 1
//Add application code here
for(delay_count = 0;delay_count<0xfff;delay_count++);
}
}
Feb 26, 2019
09:59 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 26, 2019
09:59 PM
When debug is pressed, No source available for "0x0 appears.why? Thank you.
Feb 26, 2022
11:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 26, 2022
11:06 PM
to my experience, is definitly due the hardware issue, connection problem