<?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>Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/27730/porting-mcb2300-examples-to-mcb1700</link><description> 
Dear all, 

 
I am using Keil MDK 4.12, and MCB1700 board. 

 
I managed to port simple program examples from MCB2300 to MCB1700,
but when I try to port more complex program (RL-TCPNet) I found
problems with compiling. 

 
Kindly help me to point me</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/126400?ContentTypeID=1</link><pubDate>Tue, 14 Sep 2010 09:30:28 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a2101ece-6c65-47e3-8974-208b03500d07</guid><dc:creator>Ojahan Hutajulu</dc:creator><description>&lt;p&gt;&lt;p&gt;
Mark thank you for the information, the problem is solved
now,thanks to your direction and also other friends info.&lt;/p&gt;

&lt;p&gt;
Again thank you for everyones help&lt;br /&gt;
Hopefully I can also help anytime soon&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/116008?ContentTypeID=1</link><pubDate>Tue, 14 Sep 2010 07:52:21 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:25b26a9f-ffb5-4752-a1cf-ea7ef630a836</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
You have incorrect usage.&lt;/p&gt;

&lt;p&gt;
You use FIODIR2 - probably assuming it controls the direction for
port 2.&lt;/p&gt;

&lt;p&gt;
But note in the header file. FIODIR2 is a field in a union, inside
a structure named LPC_GPIO_TypeDef.&lt;/p&gt;

&lt;p&gt;
You need to look up the variable of type LPC_GPIO_TypeDef that
relates to the port you want to control. Then you need to access the
relevant fields for that variable.&lt;/p&gt;

&lt;p&gt;
And FIODIR0, FIODIR1, FIODIR2, FIODIR3 are there if you want to
just perform an 8-bit operation to update the port direction for a
group of 8 I/O pins of a port.&lt;/p&gt;

&lt;p&gt;
You seem to want to perform an assign of a 32-bit value - this
would correspond with the union field
&amp;lt;port-variable_name&amp;gt;.FIODIR. Or you only want to change the low
byte, in which case you should use
&amp;lt;port-variable_name&amp;gt;.FIODIR0.&lt;/p&gt;

&lt;p&gt;
If the variable is instead a pointer, you have to use
&amp;lt;port-variable_name&amp;gt;-&amp;gt;FIODIR.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/102284?ContentTypeID=1</link><pubDate>Tue, 14 Sep 2010 07:32:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:814be91f-96c1-40c7-9359-cdb06ace45e4</guid><dc:creator>Ojahan Hutajulu</dc:creator><description>&lt;p&gt;&lt;p&gt;
I check in lpc17xx.h, it does contain the undefined
parameters.&lt;/p&gt;

&lt;p&gt;
Sample of lpc17xx.h is below&lt;/p&gt;

&lt;pre&gt;
/**************************************************************************//**
 * @file     LPC17xx.h
 * @brief    CMSIS Cortex-M3 Core Peripheral Access Layer Header File for
 *           NXP LPC17xx Device Series
 * @version: V1.08
 * @date:    21. December 2009
 *
 * @note
 * Copyright (C) 2009 ARM Limited. All rights reserved.
 *
 * @par
 * ARM Limited (ARM) is supplying this software for use with Cortex-M
 * processor based microcontrollers.  This file can be freely distributed
 * within development tools that are supporting such ARM based processors.
 *
 * @par
 * THIS SOFTWARE IS PROVIDED &amp;quot;AS IS&amp;quot;.  NO WARRANTIES, WHETHER EXPRESS, IMPLIED
 * OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE APPLY TO THIS SOFTWARE.
 * ARM SHALL NOT, IN ANY CIRCUMSTANCES, BE LIABLE FOR SPECIAL, INCIDENTAL, OR
 * CONSEQUENTIAL DAMAGES, FOR ANY REASON WHATSOEVER.
 *
 ******************************************************************************/
.
.
.
#include &amp;quot;core_cm3.h&amp;quot;                       /* Cortex-M3 processor and core peripherals           */
#include &amp;quot;system_LPC17xx.h&amp;quot;                 /* System Header                                      */
.
.
.
/*------------- General Purpose Input/Output (GPIO) --------------------------*/
/** @brief General Purpose Input/Output (GPIO) register structure definition */
typedef struct
{
  union {
    __IO uint32_t FIODIR;
    struct {
      __IO uint16_t FIODIRL;
      __IO uint16_t FIODIRH;
    };
    struct {
      __IO uint8_t  FIODIR0;
      __IO uint8_t  FIODIR1;
      __IO uint8_t  FIODIR2;
      __IO uint8_t  FIODIR3;
    };
  };
  uint32_t RESERVED0[3];
  union {
    __IO uint32_t FIOMASK;
    struct {
      __IO uint16_t FIOMASKL;
      __IO uint16_t FIOMASKH;
    };
    struct {
      __IO uint8_t  FIOMASK0;
      __IO uint8_t  FIOMASK1;
      __IO uint8_t  FIOMASK2;
      __IO uint8_t  FIOMASK3;
    };
  };
  union {
    __IO uint32_t FIOPIN;
    struct {
      __IO uint16_t FIOPINL;
      __IO uint16_t FIOPINH;
    };
    struct {
      __IO uint8_t  FIOPIN0;
      __IO uint8_t  FIOPIN1;
      __IO uint8_t  FIOPIN2;
      __IO uint8_t  FIOPIN3;
    };
  };
  union {
    __IO uint32_t FIOSET;
    struct {
      __IO uint16_t FIOSETL;
      __IO uint16_t FIOSETH;
    };
    struct {
      __IO uint8_t  FIOSET0;
      __IO uint8_t  FIOSET1;
      __IO uint8_t  FIOSET2;
      __IO uint8_t  FIOSET3;
    };
  };
  union {
    __O  uint32_t FIOCLR;
    struct {
      __O  uint16_t FIOCLRL;
      __O  uint16_t FIOCLRH;
    };
    struct {
      __O  uint8_t  FIOCLR0;
      __O  uint8_t  FIOCLR1;
      __O  uint8_t  FIOCLR2;
      __O  uint8_t  FIOCLR3;
    };
  };
} LPC_GPIO_TypeDef;

&lt;/pre&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/78636?ContentTypeID=1</link><pubDate>Tue, 14 Sep 2010 07:26:19 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:30801556-8f22-4ae7-adb5-eeb347468677</guid><dc:creator>Ojahan Hutajulu</dc:creator><description>&lt;p&gt;&lt;p&gt;
Project: adc.uvproj (from sample code)&lt;br /&gt;
Tools: Keil 4&lt;br /&gt;
Previously it compile without error, test it on MCB1700 and works
fine.&lt;/p&gt;

&lt;p&gt;
Later I add simple instruction:&lt;/p&gt;

&lt;pre&gt;
  FIODIR2  = 0x000000FF;
  FIOMASK2 = 0x00000000;
  FIO2PIN  = 0x00000000;
  PINSEL10 = 0;
&lt;/pre&gt;

&lt;p&gt;
The compiling msgs are below:&lt;br /&gt;
I try to update the lpc17xx.h file as suggested by John L, but still
the problem exists.&lt;br /&gt;
I also try to define path in each file option and directory option to
point to where the dependencies located.&lt;/p&gt;

&lt;p&gt;
Please help...&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&lt;br /&gt;
------------------------------------------------------&lt;br /&gt;
compiling system_LPC17xx.c...&lt;br /&gt;
compiling adc.c...&lt;br /&gt;
adc.c(32): error: #20: identifier &amp;quot;ADC&amp;quot; is undefined&lt;br /&gt;
adc.c(121): error: #20: identifier &amp;quot;SC&amp;quot; is undefined&lt;br /&gt;
adc.c(124): error: #20: identifier &amp;quot;PINCON&amp;quot; is undefined&lt;br /&gt;
adc.c(129): error: #20: identifier &amp;quot;ADC&amp;quot; is undefined&lt;br /&gt;
adc.c(167): error: #20: identifier &amp;quot;ADC&amp;quot; is undefined&lt;br /&gt;
compiling adctest.c...&lt;br /&gt;
adctest.c(27): error: #20: identifier &amp;quot;FIODIR2&amp;quot; is undefined&lt;br /&gt;
adctest.c(28): error: #20: identifier &amp;quot;FIOMASK2&amp;quot; is undefined&lt;br /&gt;
adctest.c(29): error: #20: identifier &amp;quot;FIO2PIN&amp;quot; is undefined&lt;br /&gt;
adctest.c(30): error: #20: identifier &amp;quot;PINSEL10&amp;quot; is undefined&lt;br /&gt;
Target not created&lt;br /&gt;
------------------------------------------------------&lt;br /&gt;&lt;/i&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/65874?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2010 23:23:43 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:383d98d3-67ff-4eee-8c18-af25685927e3</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
Problems with &lt;i&gt;compiling&lt;/i&gt; are to do with your &amp;#39;C&amp;#39; language
syntax &amp;amp; usage - not to do with the differences between MCB2300
&amp;amp; MCB1700.&lt;/p&gt;

&lt;p&gt;
Dealing with compiler errors is a standard part of the programming
process in any language on any platform - nothing specifically to do
with embedded, Keil, NXP, etc...&lt;/p&gt;

&lt;p&gt;
What errors, exactly, are you getting?&lt;/p&gt;

&lt;p&gt;
Usually, compiler errors tell you exactly what is wrong - and,
from that, it should be easy to fix the problem!&lt;/p&gt;

&lt;p&gt;
The key is to read the messages literally; eg, if the message
tells you that something is &lt;i&gt;&lt;b&gt;un&lt;/b&gt;&lt;/i&gt;defined - then the
solution is to &lt;b&gt;define&lt;/b&gt; it!&lt;/p&gt;

&lt;p&gt;
Note that one error often leads to a load of consequent errors -
so fix the first error first!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/90628?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2010 18:50:44 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:2e26e71e-a1e7-4070-ae13-e279ce68790e</guid><dc:creator>John Linq</dc:creator><description>&lt;p&gt;&lt;p&gt;
Hi all,&lt;/p&gt;

&lt;p&gt;
Not sure if I should create a new thread to raise my question.
Sorry for any inconvenience caused.&lt;/p&gt;

&lt;p&gt;
Do you use the new NXP Cortex-M3 programming model? I mean the
Software Driver Model.&lt;/p&gt;

&lt;p&gt;
LPC17xx CMSIS-Compliant &lt;b&gt;Standard Peripheral Firmware Driver
Library&lt;/b&gt; (GNU, Keil, IAR) (Jul 26, 2010)&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;In the below URL,&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&lt;a target="_blank" href="http://ics.nxp.com/support/documents/microcontrollers/?scope=LPC1768"&gt;ics.nxp.com/.../&lt;/a&gt;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;there are several software packages. They are:&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;Sample Code Bundle for LPC17xx Peripherals using Keil&amp;#39;s MDK-ARM
V1.02 (Jan 7, 2010)&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;LPC17xx CMSIS-Compliant Standard Peripheral Firmware Driver
Library (GNU, Keil, IAR) (Jul 26, 2010)&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;LPC13xx and LPC17xx IEC60335 Class B Certified Library (Feb 11,
2010)&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
======================================================&lt;/p&gt;

&lt;p&gt;
For [Sample Code Bundle for LPC17xx Peripherals using Keil's
MDK-ARM], I think it is equivalent to [Sample Code Bundle for
LPC23xx/LPC24xx Peripherals using Keil's &amp;micro;Vision]&lt;/p&gt;

&lt;p&gt;
For [LPC17xx CMSIS-Compliant Standard Peripheral Firmware Driver
Library], I think it is equivalent to the Luminary&amp;#39;s or ST&amp;#39;s
Cortex-M3 Peripheral Driver Library. What I am curious is, does
anyone use this NXP Cortex-M3 Peripheral Driver Library for
production?&lt;/p&gt;

&lt;p&gt;
For [LPC13xx and LPC17xx IEC60335 Class B Certified Library], I
think it is actually a tool to help users to pass the IEC60335 Class
B Certification. Am I right?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Porting MCB2300 examples to MCB1700</title><link>https://community.arm.com/thread/58648?ContentTypeID=1</link><pubDate>Mon, 13 Sep 2010 13:44:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:105a7f7b-c00e-4dfe-8402-c8cafeea8eda</guid><dc:creator>Remi Ricard</dc:creator><description>&lt;p&gt;&lt;p&gt;
Hello Ojahan,&lt;/p&gt;

&lt;p&gt;
One thing that may help you is the document from Keil: &lt;a href="http://www.nxp.com/documents/application_note/AN10878.pdf"&gt;www.nxp.com/.../AN10878.pdf&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;
I&amp;#39;m currently working on the transition of my code from a LPC2368
to a LPC1768. I had a few issues with RL, but by comparing the
examples RL-CAN and RL-Blinky of the two families, I was able to see
a couple of differences in the configuration wizards...&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>