LPC176x.h

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LPC176x.h

561件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by leluno on Sat Feb 08 04:47:09 MST 2014
i'm working with lpcxpresso and i'm very satisfyed. Thank you for this fine programm.

But there seems to be a problem with the CCR-Register. Which one? there are two:

Configuration and Control Register CCR 0xE000ED14
and
Clock Control Register CCR 0x40024008

Is this ok?

In LPC176x.h
RxFliterCtrl must be named RxFilterCtrl

and
MIN for minute of rtc makes Proplems because of MIN/MAX in other functions.



ラベル(1)
0 件の賞賛
返信
2 返答(返信)

550件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by leluno on Sat Feb 08 06:23:35 MST 2014
for me its no  longer a Problem  while i have found and changed MIN to MINUTE and in

LPC_types.h

MIN in MIn

#define MAx(a, b) (((a) > (b)) ? (a) : (b))
#define MIn(a, b) (((a) < (b)) ? (a) : (b))//geändert conflict mit MINute

#endif /* LPC_TYPES_H */

The problem is, that NXP has two system-files with the same item for different meanings.


0 件の賞賛
返信

550件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MarcVonWindscooting on Sat Feb 08 05:26:38 MST 2014

Quote: leluno

MIN for minute of rtc makes Proplems because of MIN/MAX in other functions.


Yes, but the reason for this is the embedded programmers' widespread non-awareness of the consequences #define on namespaces. They were told a thousand times and still abundantly use a *text processor* in a serious programming language.
As for you, if you didn't do the same (MIN/MAX macros I guess  ;-)  ) there would be no problem! That's a good starting point to do better, isn't it?
0 件の賞賛
返信