<?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>Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/15030/possible-bug-in-uvision-2-31-c51-7-01</link><description> Hi all, 
Could someone please check the following behaviour of uVision 2.31 (C51 7.01)? 
 
If in the Options for Target... dialog you switch from the &amp;quot;Target&amp;quot; tab to the &amp;quot;Device&amp;quot; tab and then back to the &amp;quot;Target&amp;quot; tab, some of the options are lost. 
</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/141184?ContentTypeID=1</link><pubDate>Mon, 16 Sep 2002 01:07:00 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:c67488fe-23b2-4309-82f6-da6a73550612</guid><dc:creator>Vaclav Korecek</dc:creator><description>&lt;p&gt;&lt;i&gt;&amp;quot;The ESC key does not perform the &amp;#39;Cancel&amp;#39; function; it is simply ignored :-(&amp;quot;&lt;/i&gt;&lt;br /&gt;
True. I want to described that behaviour of Cancel button is same as ESC in another similar dialogues under Win32 because I have another W98SE language mutation than English and I hadn&amp;#39;t been sure with English Win version (My &amp;quot;Cancel&amp;quot; is named &amp;quot;Storno&amp;quot;). Certainly, if ESC will perform the Cancel function it would be fine.&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;&amp;quot;I tried it with the Triscend devices, and I had no problem so long as I didn&amp;#39;t actually change the device&amp;quot;&lt;/i&gt;&lt;br /&gt;
&lt;b&gt;Triscend&lt;/b&gt; on my PC : &lt;br /&gt;
if I apply my procedure above, it &lt;b&gt;&lt;i&gt;change&lt;/i&gt;&lt;/b&gt; Xtal to 40MHz and do unchecking of &lt;b&gt;&amp;quot;Use multiple DPTR reg.&amp;quot;&lt;/b&gt; and &lt;b&gt;&amp;quot;Use On/chip XRAM&amp;quot;&lt;/b&gt; while &lt;b&gt;&amp;quot;Memory model&amp;quot;, &amp;quot;Code Rom Size&amp;quot;&lt;/b&gt; and &lt;b&gt;&amp;quot;OS&amp;quot;&lt;/b&gt; give back previous settings what is same as for my Dallas,... .&lt;br /&gt;
My conclusion is: Keil uV2 2.31 (W98SE) installation (on my PC !!!) &lt;b&gt;change&lt;/b&gt; Xtal to max. and &lt;b&gt;uncheck&lt;/b&gt; all device depended &lt;b&gt;Check boxes&lt;/b&gt;. It all hold for first click to &amp;quot;Device Tab&amp;quot; and immediate click back to &amp;quot;Target Tab&amp;quot; &lt;b&gt;only&lt;/b&gt;.&lt;br /&gt;
&lt;br /&gt;
Vaclav&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/137611?ContentTypeID=1</link><pubDate>Sun, 15 Sep 2002 17:23:21 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:871c563b-e204-4690-ac56-95d5af94e522</guid><dc:creator>Andrew Neil</dc:creator><description>&lt;p&gt;&lt;i&gt;&amp;quot;You can use ESC (or &amp;quot;Cancel&amp;quot; button) to conserve your original Target Tab settings.&amp;quot;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
The &lt;b&gt;ESC&lt;/b&gt; key does not perform the &amp;#39;Cancel&amp;#39; function; it is simply ignored :-(&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;&amp;quot;I don&amp;#39;t think that it is problem &amp;#39;only certain devices...&amp;#39;&amp;quot;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
I tried it with the Triscend devices, and I had no problem so long as I didn&amp;#39;t actually &lt;i&gt;&lt;b&gt;change&lt;/b&gt;&lt;/i&gt; the device&lt;br /&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/134112?ContentTypeID=1</link><pubDate>Sun, 15 Sep 2002 11:25:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:fa7643f8-f069-48bb-9119-5ee9fac05820</guid><dc:creator>Vaclav Korecek</dc:creator><description>&lt;p&gt;Andrew,&lt;br /&gt;
the problem is (step-by-step).&lt;br /&gt;
&lt;br /&gt;
1. Open &amp;quot;Option for Targets &amp;#39;xxx&amp;#39; &amp;quot;&lt;br /&gt;
2. In openned window is activated Target Tab as first.&lt;br /&gt;
3. Set different properties than is default settings in &amp;quot;Device database&amp;quot; for your Device type if you haven&amp;#39;t set it at the moment.&lt;br /&gt;
(Different Xtal frequency as Jose mentioned,...) &lt;br /&gt;
4. Click on Device Tab and immediately click back on Target Tab. &lt;br /&gt;
5. If you&amp;#39;ll find some changes against the prevoius settings in Target Tab than you have same behaviour as Jose and me.&lt;br /&gt;
(In my case, it set default &amp;quot;Database&amp;quot; settings for my device type)&lt;br /&gt;
&lt;br /&gt;
You can use ESC (or &lt;b&gt;&amp;quot;Cancel&amp;quot;&lt;/b&gt; button) to conserve your original Target Tab settings.&lt;br /&gt;
&lt;br /&gt;
I don&amp;#39;t think that it is problem &lt;i&gt;&amp;quot;only certain devices...&amp;quot;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
Jon,&lt;br /&gt;
thank you for the good message. &lt;br /&gt;
&lt;br /&gt;
Vaclav&lt;br /&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/121799?ContentTypeID=1</link><pubDate>Sat, 14 Sep 2002 13:57:05 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:26198757-ab51-4464-aa2d-404a043337e4</guid><dc:creator>Andrew Neil</dc:creator><description>&lt;p&gt;&lt;i&gt;&amp;quot;This problem will be corrected in the next (7.02) release.&amp;quot;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
Jose surmised that this may apply to only certain devices; this seems likel, as he can reproduce the problem, but I didn&amp;#39;t see it.&lt;br /&gt;
&lt;br /&gt;
Would you care to elucidate on this?&lt;br /&gt;
&lt;br /&gt;
And while you&amp;#39;re there, &lt;b&gt;&lt;i&gt;please&lt;/i&gt;&lt;/b&gt; could you make the &lt;b&gt;ESC&lt;/b&gt; key work in this dialogue?!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/110092?ContentTypeID=1</link><pubDate>Sat, 14 Sep 2002 12:29:48 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:05d4d146-a4c4-47c9-a1b0-676a8c1d253a</guid><dc:creator>Jon Ward</dc:creator><description>&lt;p&gt;This problem will be corrected in the next (7.02) release.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Jon&lt;/b&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/95166?ContentTypeID=1</link><pubDate>Sat, 14 Sep 2002 11:41:44 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:1d31269b-2b53-4cdb-b2b8-a396ff78d8bd</guid><dc:creator>Andrew Neil</dc:creator><description>&lt;p&gt;As I said, I don&amp;#39;t see this behaviour if I just &lt;b&gt;view&lt;/b&gt; the &amp;#39;Device&amp;#39; tab - only if I actually &lt;b&gt;change&lt;/b&gt; the device&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/95172?ContentTypeID=1</link><pubDate>Sat, 14 Sep 2002 10:40:39 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:c1f5d134-7760-4cf4-bd32-4dc7d8d5a346</guid><dc:creator>Jose  Sanchez del Pozo</dc:creator><description>&lt;p&gt;Andrew, Vaclav,&lt;br /&gt;
I&amp;#39;ve double checked and I can confirm that the settings are resetted by just clicking the &lt;i&gt;Device&lt;/i&gt; tab. It happens in two different installations of the C51 package.&lt;br /&gt;
&lt;br /&gt;
In my case, even the Xtal setting is changed to 18.0 from the 16.0 which I use in my project. The off-chip code and xdata memory settings are not changed, by the way.&lt;br /&gt;
&lt;br /&gt;
It may happen only with certain Devices, I&amp;#39;ll investigate further.&lt;br /&gt;
&lt;br /&gt;
Jose&lt;br /&gt;
&lt;br /&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/54652?ContentTypeID=1</link><pubDate>Sat, 14 Sep 2002 00:26:15 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:e9b71fee-dcdb-4181-bf8b-a0f24657b457</guid><dc:creator>Vaclav Korecek</dc:creator><description>&lt;p&gt;&lt;i&gt;&amp;quot;changing the device is a pretty fundamental change, and could well invalidate some of the Target settings anyway!&amp;quot;&lt;/i&gt;&lt;br /&gt;
&lt;br /&gt;
Yes, it can be fundamental change but if I don&amp;#39;t change device anyway why is changed Target option same way as the &lt;b&gt;Default&lt;/b&gt; button?&lt;br /&gt;
&lt;br /&gt;
If I forget this behaviour and click by mistake on the Device Tab than I quickly use &lt;b&gt;&amp;quot;Cancel&amp;quot;&lt;/b&gt; button.&lt;br /&gt;
&lt;br /&gt;
It&amp;#39;s not critical but it is a bug I mean.&lt;br /&gt;
&lt;br /&gt;
Vaclav&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible bug in uVision 2.31 (C51 7.01)</title><link>https://community.arm.com/thread/39140?ContentTypeID=1</link><pubDate>Fri, 13 Sep 2002 08:50:54 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:eb20d53e-2114-42ba-b2e0-d9f9749f7542</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;Just switching between the tabs doesn&amp;#39;t seem to do it.&lt;br /&gt;
&lt;br /&gt;
However, if I &lt;i&gt;change&lt;/i&gt; the device - &lt;i&gt;eg&lt;/i&gt; from Triscend TE502 to TE505 - that &lt;i&gt;does&lt;/i&gt; cause the &amp;#39;Use multiple DPTRs&amp;#39; and &amp;#39;Use On-chip XRAM&amp;#39; options to be cleared (and maybe others - I didn&amp;#39;t check).&lt;br /&gt;
&lt;br /&gt;
This is not a new behaviour: in previous versions, the Device &amp;amp; Target options were separate dialogues, but changing the Device had the same effect.&lt;br /&gt;
I&amp;#39;m not sure that the behaviour is entirely unreasonable: changing the device is a pretty fundamental change, and could well invalidate some of the Target settings anyway! (&lt;i&gt;eg,&lt;/i&gt; whether or not multiple DPTRs are available to be enabled!)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>