Keil Logo Arm Logo

Porting C167 code to C164

Next Thread | Thread List | Previous Thread Start a Thread | Settings

Details Message
Read-Only
Author
David Cresswell
Posted
23-Feb-2005 12:59 GMT
Toolset
None
New! Porting C167 code to C164
How easy is it to port C167 (Kitcon) code to a C164 such as the nanoMODUL-164?

Thanks

Dave
Read-Only
Author
Wunderlich Chris
Posted
23-Feb-2005 15:02 GMT
Toolset
None
New! RE: Porting C167 code to C164
It should not be too difficult. However, you have to mindful of the different peripherals that do not exist between the devices. Code for the core is no different. This biggest issue would to change from a demux bus to a multiplexed bus.

-Chris
Read-Only
Author
David Cresswell
Posted
23-Feb-2005 19:14 GMT
Toolset
None
New! RE: Porting C167 code to C164
How conceivable is it to do this without a C164 evaluation/development board? I've got plenty of C167 development boards available but the C164 will allow me smaller packaging. Not to mention the fact the C167 is overpowered for the task.

Dave
Read-Only
Author
Wunderlich Chris
Posted
23-Feb-2005 20:31 GMT
Toolset
None
New! RE: Porting C167 code to C164
In my opinion it is very doable. If you only use peripherals that are on both and adjust for the performance hit of going to a multiplexed bus then it should be very close. (There is an OTP version of the C164 available to run in single chip mode). You also need to be aware that the C164 does not have port6 so the chip selects and segmentation address lines are both on port4. For peripherals that you want to use that are not on the C167 you can use dscope which is very representative of the actual hardware interaction. Although it is not cycle accurate it does a very nice job.

-Chris

Next Thread | Thread List | Previous Thread Start a Thread | Settings

Keil logo

Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings