Mac OS X development

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Mac OS X development

2,143 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by alex_grach on Wed Oct 20 23:48:48 MST 2010
Is there any apportunity to use (develop) LPCXpresso under Mac OS X (10.5 or later)?
0 Kudos
Reply
8 Replies

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Mike45 on Wed Oct 27 00:48:29 MST 2010
thank you very much for your reply.  i have a better understanding of what CMSIS is and i've got lots more to learn about everything!  i'm not sure i know what it is i'm trying to ask but this is another step towards it:

http://knowledgebase.nxp.com/showthread.php?p=4040#post4040
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Wed Oct 27 00:01:14 MST 2010
I have no idea what is provided by microbuilder.

As part of the CMSIS ARM provides the Core Peripheral Access Layer which  contains name definitions, address definitions and helper functions to  access core registers and peripherals. It also defines a device  independent interface for RTOS Kernels that includes debug channel  definitions. This layer is available for various compiler  implementations:This software layer is expanded by Silicon Partners with:

[LIST]
[*]Device Peripheral Access Layer: provides definitions for all device peripherals
[*]Access Functions for Peripherals (optional): provides additional helper functions for peripherals.
[/LIST]
Thus, for *common* (Core) Cortex-M peripherals, the API offers portability. For device-specific peripherals, the API is written by the chip vendor (NXP in this case) and is device/family specific. ADC would be device specific and thus will probably not offer portability to another vendors parts.

From my perspective, as a minimum, CMSIS provides source code written by the vendor in a common format that shows you how to control the peripheral. It also provides a common API for the Core peripherals, such as NVIC, SYSTICK etc.

See:
http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.p...
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Mike45 on Tue Oct 26 14:15:15 MST 2010
bump
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Mike45 on Thu Oct 21 15:41:18 MST 2010

Quote: CodeRedSupport
Everything is available from the command line and you can use your own editor. Add the bin and tools/bin directories to your path.

However, you will find it *much* easier to use the IDE - wizards to create projects, Makefiles automatically generated with all correct options, auto generated linker scripts for you particular mcu etc etc. You can do this yourself, but you are making your own life much harder. Try the IDE - you might even like it ;-)



wow!  that's really good news.  i know how to do these things for my avr given i've got plenty of tutorials and templates.  I will use the IDE until i understand all about the makefile and compilation.  Is this enough knowledge to do what you're saying, or more things specific to the arm?

--
(another question, if i may ask - sorry i know this should be an easy one, but i just want to clarify)
What is the difference between your libraries and the code base provided by Microbuilder.eu?

for instance, an ADC_Init routine, are there two differences?
1.  different(or the same) address operations to achieve the same thing
2.  LPC uses the CMSIS naming standard for all the registers

If #1 is true how are they able to access those registers?  what is given to the public that is common for all m3's?

thanks!
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Oct 21 14:41:59 MST 2010
Everything is available from the command line and you can use your own editor. Add the bin and tools/bin directories to your path.

However, you will find it *much* easier to use the IDE - wizards to create projects, Makefiles automatically generated with all correct options, auto generated linker scripts for you particular mcu etc etc. You can do this yourself, but you are making your own life much harder. Try the IDE - you might even like it ;-)
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Mike45 on Thu Oct 21 14:27:09 MST 2010
I got my lpcxpresso board yesterday and installed ubuntu under a VM.

It's a huge change for me as my bias is for Xcode.  is there any way i can do some basic things like code compilation somehow under xcode / terminal?

---

will there ever be a way to be able to use a different editor and compile from a commandline?
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Oct 21 10:02:30 MST 2010
...however, you can run LPCXpresso in a VM running under OSX. The Linux or Windows version will run happily under a number of VMs.
0 Kudos
Reply

2,062 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by CodeRedSupport on Thu Oct 21 02:48:22 MST 2010
There are no current plans for a Mac OS X release of LPCXpresso.

Regards,
CodeRedSupport
0 Kudos
Reply