05-03-2010 08:03 AM
Greetings 2 all.
I'm planning to start new project based on LPC2368. I have couple questions regarding the LV ARM 2009 functionalities for this target. So the questions are:
1) Does LV ARM 2009 support File I/O to work with an SD card (4-bit mode on MCB2300 for LPC2368)?
2) I need two UARTs and SPI, but UART1 and SPI share pins, also I realized that only UART0 and UART1 supported- so miscellaneous changes should be done to convert UART1 code to be used as UART2?
3) External Interrupts: only EINT0-EINT3 supported, or I can set any Port0 and Port2 pins to be used as external interrupt (and they will will be combined with the EINT3 interrupt requests)?
4) Is real time clock supported?
5) What about an exisiting problems with UART, SPI etc?
Best Regards.
05-04-2010 01:46 PM
Hi Crowbar,
I'll see if I can answer some of your questions. Keep in mind that expanding the functionality of Tier 2 boards, such as the LPC2368, is something that we do not support on a board by board basis, and is generally up to the programmer. LabVIEW for ARM provides tools, such as Wizards, the ability to call C code using the in-line C node, etc. but determining the code and configurations to use and how to customize a board is up to you.
1) See this KnowledgeBase article on libraries with LabVIEW for ARM, specifically the Flash File System section. It looks like flash functionality is available with a specific library purchased from Keil.
2) These pinouts are specific to the board. LabVIEW for ARM allows interfacing with a valid UARTs as a COM port, but it is up to the programmer of the board and/or the board manufacturer to determine what pins can be used to create these UARTs.
3) I believe that EINT0-3 are the supported external interrupts, and it may be possible to extend this functionality by using other pins as interrupts, but again, this is up to the programmer to determine if this is possible and how this would need to be done.
4) What exactly do you mean by supporting a real-time clock, and what are you looking to do with this?
5) What existing problems are you referring to? I am not aware of any general problems with using UART or SPI.
Regards,
Stephen S.
05-04-2010 03:08 PM - edited 05-04-2010 03:12 PM
Hi Stephen. The MCB2300 board comes populated with LPC2368 processor. So we are talking about Tier1 device.
1) I've realized that LV ARM 2009 supports file I/O for LPC2368 cause it's Tier1 device. I was little bit confused before because I saw File I/O pallet for LM3S8962- evaluation board for this processor works with SD card in SPI mode, while LPC2368 works with SD card in MCI mode.
2) I will use UART0 and UART2 instead of UART1 (SPI will be used). UART2 is not supported by serial compatibility VIs pallet- little changes will be done.
3) Ok, EINT0-3 are suppoprted, other are available through extra-coding.
4) LPC2368 has and RTC: set of counters for time meauserement when power is on/off. Also LV ARM 2009 has functions like Get date time etc. But what about Set date time if i want correct time readings from RTC? I want my device to maintain valid time and data values when main power is turned off.
5) Ok.
One more question:
6) Peak-Poke Vis work with Flash memory or SRAM? I want to save calibration 32-bit value in order to use it during next device power ups.
Best Regards.
05-05-2010 02:46 PM
You are right about the LPC2368 being in the Tier 1 MCB2300; sorry about the mixup there, I was looking at the wrong one. However, it seems like you are doing a good job figuring out most of the issues so far. As for the issue with the clock, there is no battery on the board that would allow the clock to retain values when it is turned off, so I do not think that you could do this without implementing the functionality yourself.
As long as the flash memory or SRAM are mapped to memory, you should be able to use the Peak and Poke VIs. There is a discussion on a similar type of thing with the MCB2400 that may be helpful with this.
Regards,
Stephen S.
05-06-2010 05:13 AM