<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>LPC 1768: ADC Trim Register Error with VTOR &amp;gt; 0</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/28401/lpc-1768-adc-trim-register-error-with-vtor-0</link><description> 
Hello, 

 
I&amp;#39;m using a NXP LPC1768 Cortex-M3 controller with KEIL MDK-ARM and
uLink2-Debugger. 

 
When I start my application from a higher address than 0 (VTOR
&amp;gt; 0) the ADC gives back strange values. This is due to the ADC
Trim register ADTRM. 

</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: LPC 1768: ADC Trim Register Error with VTOR &gt; 0</title><link>https://community.arm.com/thread/105355?ContentTypeID=1</link><pubDate>Thu, 03 Nov 2011 01:31:33 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:8a7657b5-cfcc-4fd8-ad50-bcac97721750</guid><dc:creator>Daniel Wiese</dc:creator><description>&lt;p&gt;&lt;p&gt;
Hi,&lt;/p&gt;

&lt;p&gt;
yes, the debugger should reset the controller. In the debugger
settings the address range is set to 00002000H - 0007FFFFH and I am
using an INI file:&lt;/p&gt;

&lt;p&gt;
SP=_RDWORD(0x2000); // Setup Stack Pointer&lt;br /&gt;
PC=_RDWORD(0x2004); // Setup Program Counter&lt;br /&gt;
_WDWORD(0xE000ED08, 0x2000); // Setup Vector Table Offset
Register&lt;/p&gt;

&lt;p&gt;
The bootloader is at 0x00, but it&amp;#39;s another project and I just
want to debug the real application at 0x2000 (what generally
works).&lt;/p&gt;

&lt;p&gt;
I would like to get an understanding of the things that happen at
start-up and prevent other side-effects.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LPC 1768: ADC Trim Register Error with VTOR &gt; 0</title><link>https://community.arm.com/thread/79634?ContentTypeID=1</link><pubDate>Wed, 02 Nov 2011 12:51:04 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:0d6507a0-65c9-4c72-a36f-bccf06fe0485</guid><dc:creator>@Marc Crandall</dc:creator><description>&lt;p&gt;&lt;p&gt;
Hi Daniel,&lt;/p&gt;

&lt;p&gt;
Doesn&amp;#39;t the debugger reset the micro? How are you jumping to
0x2000 when you start debugging?&lt;br /&gt;
Are you using an INI file.&lt;/p&gt;

&lt;p&gt;
What NXP responded make sense to me. Your real app will need a
bootloader at 0x0.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LPC 1768: ADC Trim Register Error with VTOR &gt; 0</title><link>https://community.arm.com/thread/59901?ContentTypeID=1</link><pubDate>Wed, 02 Nov 2011 04:59:42 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:3d672bff-f350-4096-a0b7-6b56ad267d2e</guid><dc:creator>Daniel Wiese</dc:creator><description>&lt;p&gt;&lt;p&gt;
This was the answer from NXP:&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&lt;br /&gt;
Hi,&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;It is best if the debugger can run through the boot rom after
every reset (which will complete the remapping) and then stop at main
or in the startup code as the user desires. The ROM sets up reset
values of some user registers and also sets internal registers. If
the whole boot code does not run before the user code, then the
debugging environment won&amp;rsquo;t represent the run environment as
closely as it could, for example having different Flash performance
configurations or different reset values of power management
registers, which could be misleading.&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;There is an option which can be set in the debugger (target
options &amp;gt; debug &amp;gt; settings) to stop after the
bootloader.&lt;/i&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>