Apr 01, 2014
11:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 01, 2014
11:49 PM
Hello there,
i am using DAP miniWiggler V3 and tested it
with the XMC4500 Relax-Kit and it is working,
but for flashing the programm and starting them
it needs about 45 seconds. If i do the same
over the onboard usb-debugger it needs about
15 seconds.
What can i do, to improve the performance of the
DAP miniWiggler?
Is there any documentation, which describes the
configuration of the miniWiggler exactly?
Best regards,
HiSH
i am using DAP miniWiggler V3 and tested it
with the XMC4500 Relax-Kit and it is working,
but for flashing the programm and starting them
it needs about 45 seconds. If i do the same
over the onboard usb-debugger it needs about
15 seconds.
What can i do, to improve the performance of the
DAP miniWiggler?
Is there any documentation, which describes the
configuration of the miniWiggler exactly?
Best regards,
HiSH
- Tags:
- IFX
7 Replies
Apr 04, 2014
04:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 04, 2014
04:45 AM
Hello Infineon Team,
could you help me with this topic?
Are there no Manuals which describes detailed
the "DAP MiniWiggler V3" and the
belonging Software?
Is there no service for selled product?
What can I do to improve the times
for flashing?
Best regards,
HiSH
could you help me with this topic?
Are there no Manuals which describes detailed
the "DAP MiniWiggler V3" and the
belonging Software?
Is there no service for selled product?
What can I do to improve the times
for flashing?
Best regards,
HiSH
Apr 04, 2014
05:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 04, 2014
05:23 AM
Hi,
I also need more infos. The infos on the infineon website are not sufficient to use miniWiggler V3 without trial and error and the whole web doesn't offer more infos. Does the miniWiggler operate with Tasking debugger and gdb? Are there differences in the download speed? Which connector has to be used to debug via swd or jtag? Are there any compatibilities to the connectors defined by ARM?
http://www2.keil.com/coresight/coresight-connectors
Your customers need a description of the complete debug chain DAVE -> miniWiggler -> XMC4500 when using Tasking Debugger or gdb. Please help.
Best Regards.
I also need more infos. The infos on the infineon website are not sufficient to use miniWiggler V3 without trial and error and the whole web doesn't offer more infos. Does the miniWiggler operate with Tasking debugger and gdb? Are there differences in the download speed? Which connector has to be used to debug via swd or jtag? Are there any compatibilities to the connectors defined by ARM?
http://www2.keil.com/coresight/coresight-connectors
Your customers need a description of the complete debug chain DAVE -> miniWiggler -> XMC4500 when using Tasking Debugger or gdb. Please help.
Best Regards.
Not applicable
Apr 07, 2014
01:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 07, 2014
01:57 AM
Hi,
Have you installed the latest DAS server? You can download it here: http://www.infineon.com/das
The miniWiggler is used together with 'UDAS' (Universal Debug Access Server) which you can find at the debug configuration for Tasking Debugger.
Have you installed the latest DAS server? You can download it here: http://www.infineon.com/das
The miniWiggler is used together with 'UDAS' (Universal Debug Access Server) which you can find at the debug configuration for Tasking Debugger.
Apr 07, 2014
03:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 07, 2014
03:37 AM
Hi,
yes it is the last version V4.4.2 and it is selected in the Tasking Debugger.
But what can i do or change to improve the perfomance?
Best Regards,
HiSH
yes it is the last version V4.4.2 and it is selected in the Tasking Debugger.
But what can i do or change to improve the perfomance?
Best Regards,
HiSH
Apr 07, 2014
08:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 07, 2014
08:54 AM
@Jackson
Many thanks for your fast response,
there are misunderstandings possible: a new user expects that a controller with jtag interface has to be connected to jtag connector of miniWiggler. But we found out the UDAS uses the DAP connector when communicating to XMC4000 family. Is this correct please? Does UDAS need any uncommon settings by the user?
Best Regards.
Many thanks for your fast response,
there are misunderstandings possible: a new user expects that a controller with jtag interface has to be connected to jtag connector of miniWiggler. But we found out the UDAS uses the DAP connector when communicating to XMC4000 family. Is this correct please? Does UDAS need any uncommon settings by the user?
Best Regards.
Apr 09, 2014
03:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 09, 2014
03:00 AM
@Jackson
i did an examination of the SWD-Signals
of the DAP-Miniwiggler V3.
You can see the Clock (TCK - blue signal) works with
403 KHz. ("Measure_TMS_TCK.jpg")
[
With the perfmeter there is a window ("DAS Access HW_0.4.JPG"),
in which i could update the clock frequenzy from
0,4 MHz for example to 10 MHz ("DAS Access HW_10.0.JPG"),
but after starting the Tasking-Debugger, the
clock frequenzy is automatically reset to 0,4 MHz
again, so i think, this is the
reason, why the the Loading
time with the DAP-MiniWiggler needs
45 sek. versus the OnBoard-Debugger
with 15 sek.
So, how could i increase the clock-frequency
of the DAP-MiniWiggler on working with the
Tasking-Debugger.
Best regards
i did an examination of the SWD-Signals
of the DAP-Miniwiggler V3.
You can see the Clock (TCK - blue signal) works with
403 KHz. ("Measure_TMS_TCK.jpg")
[
With the perfmeter there is a window ("DAS Access HW_0.4.JPG"),
in which i could update the clock frequenzy from
0,4 MHz for example to 10 MHz ("DAS Access HW_10.0.JPG"),
but after starting the Tasking-Debugger, the
clock frequenzy is automatically reset to 0,4 MHz
again, so i think, this is the
reason, why the the Loading
time with the DAP-MiniWiggler needs
45 sek. versus the OnBoard-Debugger
with 15 sek.
So, how could i increase the clock-frequency
of the DAP-MiniWiggler on working with the
Tasking-Debugger.
Best regards
Apr 23, 2014
07:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 23, 2014
07:42 AM
Hi Infineon,
I can confirm the problem, HiSH is right.
UDAS doesn't store frequency setting entered at Permeter. Setting is lost when UDAS stops after terminating tasking debugger. At next start of debugger UDAS uses only 0.4 MHz as swd clock frequency, the minimum value.
A turnaround would be:
- Start DAS Perfmeter
- At Window 'DAS Device Select' start DAS server and select family of connected target
- At window 'DAS Access H...' enter 30 as New frequency und click update, the allowed frequency value is shown, close window with Ok
- Don't close Perfmeter window, otherwise UDAS server stops when terminating debugger and swd clock frequency set is lost (debugger must be terminated before returning to Dave CE view, otherwise next download fails)
I have opened a ticket:
http://www.infineonforums.com/support/dave3/index.php?option=com_maqmahelpdesk&Itemid=0&id_workgroup...
Best Regards.
I can confirm the problem, HiSH is right.
UDAS doesn't store frequency setting entered at Permeter. Setting is lost when UDAS stops after terminating tasking debugger. At next start of debugger UDAS uses only 0.4 MHz as swd clock frequency, the minimum value.
A turnaround would be:
- Start DAS Perfmeter
- At Window 'DAS Device Select' start DAS server and select family of connected target
- At window 'DAS Access H...' enter 30 as New frequency und click update, the allowed frequency value is shown, close window with Ok
- Don't close Perfmeter window, otherwise UDAS server stops when terminating debugger and swd clock frequency set is lost (debugger must be terminated before returning to Dave CE view, otherwise next download fails)
I have opened a ticket:
http://www.infineonforums.com/support/dave3/index.php?option=com_maqmahelpdesk&Itemid=0&id_workgroup...
Best Regards.