Content originally posted in LPCWare by thinkchip on Wed Dec 29 23:12:56 MST 2010 Hi, I want to know if NXP have some plan to expand the devices for cortex M0, like 3 uarts, usb, rtc,more pins, etc, thanks
Content originally posted in LPCWare by larryvc on Sat Mar 05 11:36:30 MST 2011 I like the Fujitsu part for its very low active and standby current. I didn't find stock for this either. I have been looking at the Ramtron FM24W256. It seems to fit my requirements also is 256 Kb. http://www.ramtron.com/files/datasheets/FM24W256_ds.pdf
Content originally posted in LPCWare by Ex-Zero on Sat Mar 05 02:11:01 MST 2011 Quote: larryvc Zero what is the part number of the FRAM Santa brought you? It's a Fujitsu MB85RC128 (MB85RC128PNF-G-JNE1). Unfortunately Santa bought the whole stock :mad: [INDENT]Farnell Order Code: 1831995 [/INDENT][INDENT]Availability: Awaiting Delivery Datasheet: http://www.semiconductorstore.com/pdf/newsite/Fujitsu/e513110.pdf [/INDENT]Description: [INDENT]FRAM: 128Kbit Voltage Range: 2.7V to 3.6V Case Style: SOP8 Interface: I2C Memory Configuration: 16K x 8bit Operating Temperature Range: -40°C to +85°C [/INDENT]
Content originally posted in LPCWare by larryvc on Fri Mar 04 22:12:01 MST 2011 Quote: Zero BTW EEPROM: Last Christmas (= last week) Santa brought me a FRAM (128K) Zero what is the part number of the FRAM Santa brought you?
Content originally posted in LPCWare by Ex-Zero on Wed Jan 12 15:56:18 MST 2011 Quote: NXP_USA ...should be available... Found a 'Development' product status on NXP website. :( Is there a roadmap for 'Production' ? (Just to know if I have to add it to Christmas list 2011 or later...)
Content originally posted in LPCWare by NXP_USA on Wed Jan 12 10:34:49 MST 2011 The parts should be available through all of our distributors. There are no plans to limit the sale just to automotive companies.
Content originally posted in LPCWare by Ex-Zero on Wed Jan 12 07:28:20 MST 2011 Yes, it does. Always thought it's not very clever to integrate transceivers, but the more interesting question for me is: will these wonderful things be available (in small quantities :)) for me through my german distributors or is this stuff just sold to automotive companies :mad:
You might also want to check that when building a Debug build of your project has the linker option "[FONT=Courier New][SIZE=1]--gc-sections[/SIZE][/FONT]" specified - which will cause unused functions to be eliminated from your final image, and can dramatically reduce overall code size. Some earlier versions of LPCXPresso IDE had this option removed (as did some versions of the example projects).
Anyway, can I suggest that if you want to discuss application size further, then you create a new forum thread - as code size is not really related to the main subject of this thread.
Content originally posted in LPCWare by Senso on Mon Jan 03 19:13:35 MST 2011 So, where can I get the newLib and where to put it so the CodeRed IDE can use it?
Content originally posted in LPCWare by cyberstudio on Mon Jan 03 14:41:03 MST 2011 Adding to the list of wants, I want smaller than LQFP64. ST is able to jam 64 pins into a 5mm x 5mm BGA and NXP could easily do the same, after all they are the one coming up with the 2mm x 2mm LPC1102.
Content originally posted in LPCWare by Ex-Zero on Mon Jan 03 09:38:48 MST 2011 Quote: KTownsend You wanted RTC ... they gave it to you. You should have told Santa that you ALSO wanted CAN. :p Now you'll have to wait until next Christmas for better presents. Come on, don't blame Santa :) He knows for sure that we always want more and more features and not less. Unfortunately someone else :confused: must have forgotten to invite him to this roadmap meetings.
Content originally posted in LPCWare by ktownsend on Mon Jan 03 08:20:21 MST 2011 Quote: Zero Q1, that's now :) Is there a roadmap for releasing an UM? NXP Search doesn't show results. Found a preliminary at http://www.zlgmcu.com/NXP/LPC1000/LPC1200/LPC122x_UM_EN.pdf LQFP64 and no CAN :confused: You wanted RTC ... they gave it to you. You should have told Santa that you ALSO wanted CAN. :p Now you'll have to wait until next Christmas for better presents. I've actually been looking at the 122x and it's kind of a tradeoff for me. The speed is fine (though a bit limited with the internal crystal), and I really need the extra flash space and the RTC (at last!) ... but with more pins than the 1114 only one SSP block kind of stinks. I often need two since I like to have a dedicated SPI block for the radio transceiver and a second one for an SD card or an external 16-bit ADC or high-traffic sensor, etc. I'm going to use it for a wireless protocol analyser (for debugging 802.15.4 traffic), but it's not really an upgrade to the 1114/1343 per se. It has some things I miss in the 1100/1300 family (more flash + RTC), but you lose a few things I would have found useful (two SSPs and maybe CAN). There are some pretty cool new peripheral blocks though that look really interesting and useful ... but I don't really want to list a lot of details until a UM is published somewhere officially. It looks like an interesting chip and I'm looking forward to trying it, I just wouldn't really consider it an upgrade to the 1114 ... it's kind of a different mix of features. Hope the price is as competitive at the 1100s though.
Content originally posted in LPCWare by Ex-Zero on Mon Jan 03 05:38:49 MST 2011 Q1, that's now :) Is there a roadmap for releasing an UM? NXP Search doesn't show results. Found a preliminary at http://www.zlgmcu.com/NXP/LPC1000/LPC1200/LPC122x_UM_EN.pdf LQFP64 and no CAN :confused:
Content originally posted in LPCWare by NXP_Europe on Mon Jan 03 03:12:27 MST 2011 [COLOR=black][FONT=Arial][/FONT][/COLOR] [COLOR=black][FONT=Arial]The roadmap has the LPC122x on it, which has a RTC and 128KB of Flash.[/FONT][/COLOR] [COLOR=black][FONT=Arial]This part will be released in Q1 2011.[/FONT][/COLOR]
Content originally posted in LPCWare by TheFallGuy on Sun Jan 02 09:36:29 MST 2011 You might find optimizing for space improves your code size still further. The normal optimization levels (O1, O2, O3) are for performance optimizations, which can *increase* code size (especially between O2 and O3 because the compiler will do things like loop unrolling etc).
In Code Red, you will need to add -Os in the "Other optimisations" box.
Content originally posted in LPCWare by Wenzu on Sat Jan 01 19:53:49 MST 2011 Quote: A simple 4 interrupt capture is swallowing 20K of code !!! :confused:My mistake. I had UART + I2C enabled.
So.. took advice given earlier..and re-compiled to see differences.
a simple 4 input capture using 2x 32-Bit timers and 2x 16-Bit Timers just capturing only... no other stuff, no printf etc... 8388 ( text )
If I optimize at level 03, it goes down to 6996 ( text )
( text ) I am assuming is the code size after a compile.....
OK.. I am now reading AN10963.pdf to better understand what needs to be done.
Content originally posted in LPCWare by Ex-Zero on Sat Jan 01 18:23:08 MST 2011 Quote: I'm not sure what you're doing to get 20KB code for something seemingly simple? I had FAT32/SDHC + a 240x320 TFT LCD + USBCDC + a command-line interface and ~20 commands and drivers for things like EEPROM, etc., plus a decent graphics library with embedded fonts compiling in around 28KB flash. 32KB is tight, but you can still do a lot with it with careful programming. BTW EEPROM: Last Christmas (= last week) Santa brought me a FRAM (128K) :). So I threw good old 512K EEPROM away and made a few tests: >12 times faster and working with standard I2C driver without problems. :D
Content originally posted in LPCWare by ktownsend on Sat Jan 01 17:19:27 MST 2011 Quote: Wenzu Ditto for me....
I am disappointed today, because ( as a 1343/ARM noob ) I have discovered that 32k is being filled up with only barebones code.... A simple 4 interrupt capture is swallowing 20K of code !!! :confused: Main code is already 20K alone.... I'm not sure what you're doing to get 20KB code for something seemingly simple? I had FAT32/SDHC + a 240x320 TFT LCD + USBCDC + a command-line interface and ~20 commands and drivers for things like EEPROM, etc., plus a decent graphics library with embedded fonts compiling in around 28KB flash. 32KB is tight, but you can still do a lot with it with careful programming. Try compiling with -0s and in release mode, for example?
