NOR vs NAND

-
NOR-NAND comparison
PARAMETER
NOR
NAND
Capacity
16Mbits  to 1Gb (Toshiba)
512Mbits to 16Gb  (Toshiba)
XIP (execution in place /
code execution)
Yes
No
Performance Erase Write
Read
Very Slow 
Slow
Fast
Fast 
Fast
slow
Strengths
Addressable to every byte
More than 10% higher life expectancy
Erase cycle range
10,000 to 100,000
100,000 to1,000,000
Interface
SRAM-like, memory mapped
Accessed in bursts of 512 bytes; I/O mapped
Access method
Random
Sequential
Price
High
Very low
 
Pic courtesy Toshiba

Comments

Post a Comment

Popular posts from this blog

Airtel Digital tv remote factory reset and reprogram

-
Following is the way to reset Airtel Digial tv universal remote reset procedure. 1. Press red button and ok button together untill red light blinks twice. 2. Release the buttons and press 980 buttons one by one (not together)   3. Red light will blink again two times, now press ok button. Reprogramming There are 5 basic functions which your new Airtel remote needs to learn about your TV 1. TV Power code 2. TV Mute code 3. AV code 4. TV VOL + code 5. TV VOL – code Steps for Universal remote setup: Step 1:  Bring Airtel digital TV remote in learning mode. Press and hold ‘’OK + Numeric 2” key for 3 seconds. The LED blinks twice to indicate that your Airtel remote is ready to learn. Step 2 :  Hold the source remote and Airtel remote in front of each other ( 3cm-6m apart). Step 3:  Press & release the key (First on Airtel remote and then on Source remote) which needs to be programmed in Airtel remote. Example: Press and release the TV Power key on both remotes and release. The A
Read more

Tracking Linux kworker threads

-
How to find out which part of kernel/module has created this workqueue. How to track a kworker-thread named for example ''kworker/0:3 to its origin in kernel-space? I found  this thread on lkml  that answers your question a little. (It seems even Linus himself was puzzled as to how to find out the origin of those threads.) Basically, there are two ways of doing this: $ echo workqueue:workqueue_queue_work > /sys/kernel/debug/tracing/set_event $ cat /sys/kernel/debug/tracing/trace_pipe > out.txt (wait a few secs) For this you will need  ftrace  to be compiled in your kernel, and to enable it with: mount -t debugfs nodev /sys/kernel/debug More information on the function tracer facilities of Linux is available in the  ftrace.txt documentation . This will output what threads are all doing, and is useful for tracing multiple small jobs. cat /proc/THE_OFFENDING_KWORKER/stack This will output the stack of a single thread doing a lot of work. It may allow you
Read more

Asynchronus I/O (AIO) in vxworks and Linux

-
In generic Asynchronus I/O (AIO) can be designed using User lavel or in Kernel level. In user level 1) Process needs async callback/notification create another thread and process which goes to sleep on blocking calls (read/write/ioctls/select) 2) One Async master handler (process/thread) keeps track.All the process needs the service submit job to them.The master handler handles the async fd in Blocking mode and reply to requesting processes (or call the callback function) using some async notificatin like signal. In Kernel Level 1) Call some system call and submit some job to kernel workQ .After work is complete kernel notify using signal to user space.   In VxWorks :  aioPxLib provide the POSIX 1003.1b standard.Which is task implementation of aio service. functions available: 1) aio_read() - initiate an asyn. read. 2) aio_write() - initiate an syn write 3) aio_listio() - Initiate a aio list upto LIO_MAX 4) aio_error() - Get an aio error status. 5) aio_return() - Get a
Read more