new2coding: It took Micron 10 years to admit that PCM does not scale, after having signed an exclusive, royalty-bearing license for the PCM patents in 1994. Intel started their PCM technoPonzi in 2000, and even demoed the abomination they called the "world's first cell phone with PCM" in 2008, culminating with this year's complete failure (Numonyx failed to deliver a 1Gbit 45nm chip, and has gained absolutely no traction with its 90nm 128Mbit chip). Samsung started in 2003. So you should expect all kinds of funny things from them until they admit by 2013, at the latest, that PCM will never be commercialized in volume, because it does not scale, is too slow and power-consuming in write, and too costly to make. Are things clearer now?
Well, I am now a proud owner of a brand-new, commercial Samsung E2550 bought in Singapore. It contains NOR Flash, of course, and no absolutely no PRAM MCP. For those on the hunt for the non-commercial Samsung e2550 handsets that allegedly contain the PRAM MCP, here is a method to quickly identify an "interesting phone" - open the battery compartment, remove the battery, and look above the SIM card placeholder - if the solder bridge is next to the E2550 mark, then this is the regular commercial Samsung phone with NOR Flash in it, if it is next to the E2550L mark, then you MAY have a handset with PRAM MCP. Good hunting! Although, I am now convinced that Samsung simply planted only a handful non-commercial units for a marketing stunt.
The comments on this column have made for about the most entertaining technology read I can remember. Great job bringing these out Peter.
I don't think there is much more to add to the comments especially when people like RG Neale have posted here (not to mention his comprehensive series of articles on PCM scaling). But I did add my own two cents in my last column:
If you want to help me with entertainment value, please spread some of your love over there.
Somobody just brought to my attention an interesting document prepared by Samsung on October 4th, 2010:
Page 3 states: "Samsung’s 512Gb PRAM is combined with Mobile DRAM to deliver performance three times faster than NOR-based MCPs, making it ideal to quickly process large-size multimedia
The "three times faster" is obviously a lie, but hard to prove given that the only PRAM chip in a cell phone has been destroyed.
However, it is obvious that Samsung lied about PRAM being 512Gb. It is just 512Mb. Samsung exaggerated by a factor of 1024x.
And, apparently, nobody has noticed so far. People must be busy installing those chips into fake phones instead of reading marketing materials.
Great job, Samsung!
I agree, the memory market is huge and there is a lot at stake. It's not always about technical merit as we know ;-)
@Volatile Memory, keep your posts coming, I find them informative and entertaining :-)
When a Huge hedgefund And competing companies have have tons of money to loose if PCM suceeds of course you will see all of these"Experts" come out to beat it up and spread the lies ..
good luck ecd.fan keep it up .ooops i mean "virtual memory "
the truth shall set you free
Peter--this article was picked up by the Wall Street Journal's "Best of the Web Today" column, but alas, not for its content, but for the word-play of the headline. See:
Go about 3/4 down,under the heading:
"It's Always in the Last Place You Look"
I wonder who sent it in to them--has to besomeone who both reads EET AND sends things to this popular daily column.--Bill S
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.