Hi, Mr Jaya, Apologize for my poor english, such that you completely missed my points. Let me re-phrase it to simple questions: I want to switch away from LPC2103 and LPC2132/6. Could you the expert (who disqualify/condemn the Philips parts) help to find some replacement chips for me?? Only simple chip features needed!! - Reliable Code Read Protection. - Around 48 I/O on the LQFP64 package. and 32 I/O on LQFP48 - Good to have 1x Clock execution cycle at 60MHz but can go without it - Flash size 32K to 256KB, SRAM 8KB to 32KB - Competitive pricing. Available from Digikey a plus. - (All USB, UART, SPI, I2C, PWM, Timers, watchdog are standard features on all vendors' chips. All vendor's parts have buggy peripherals but all can be fixed by software. So what's the big problem/fuss??) Name me another vendor's ARM7 chip first. Before you try to confuse me more with those "cost of moving" and etc... or Student's lab-kit?? Which are supposed to be on 8-bit?? I'm not interested in debating on chip's features. Just name me a good ARM7 alternative replacement for LPC2103, LPC2134/36 and you get rid of one of your opponents immediately (I will switch to "that" new chip's discussion group).... :) Regards --- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@...> wrote: > > --- In lpc2000@yahoogroups.com, "unity0724" <unity0724@> wrote: > > > > I've seen a lot of "move to another processor" here. > > I did not realise I said this so many times in one post! Must be I > was trying to tell the poster something ... :) > > > I'm trying hard to do that but could not. > > Having already made the selection, you have to weigh costs of moving > against maintaining status quo. > > I have see two cases where having made the selection, they had to move: > > 1/ Student Lab Kit: LPC does not allow flash to be locked down. > Students could (deliberately) destroy the hardware by corrupting boot > sector. They switched to OKI. > > 2/ Flash Data Storage: LPC does not allow flash to be written at > units of byte or words. The 16-bit write requirement, ad hoc block > sizes for 256K parts coupled with its life cycle made it unsuitable > for data storage. I am not sure if they switched to OKI or SAM. > > In both cases, it did not look like the switch was more expensive. > > A third case is pending on what Robert and Tom have to say about UART > issues in LPC family. > > [Note that Philips has not indicated the UART bugs can be fixed, or > that it will be fixed, unlike power on reset bug.] > > A fourth case is pending on what happens in July in relation depletion > of LPC stocks in the field. > > > Since you are the > > expert, could you find me an alternate ARM7 good enough?? I only > > need simple features: > > - Reliable Code Read Protection. > > - Around 48 I/O on a LQFP64 package. The other chips are having > > <50% of pins as I/O > > - Good to have 1x Clock execution cycle at 60MHz but can go > > without it > > - Flash size 32K to 256KB, SRAM 8KB to 32KB > > - Competitive pricing. > > - (All USB, UART, SPI, I2C, PWM, Timers, watchdog are standard on > > all chips. All parts have buggy peripherals but all can be > > fixed. What the big problem/fuss??) > > Flattery will not get me doing the selection chart for you :) > > The designs I have seen where client does not want the product cloned > by copying hardware and the software, especially when software is the > value item, do not use LPCs. AVRs seem to be the popular choice. > > As for flash speed, I understand LPC is not as fast as SAM and maybe > even OKI. Have a look at guaranteed speeds and write/erase times. I > dont know why you consider LPC flash as fastest. > > The other reason to stay away from LPC flash is that it is in its > infant stage -- there are a number of implementation bugs to be ironed > out before it becomes as usable like other flash architectures. At > the moment it is good for OTP needs but with the advantage that field > upgrades are possible. > > Hope this helps. > > Jaya >
Message
Re: LPC hardware+software problems
2006-04-30 by unity0724
Attachments
- No local attachments were found for this message.