Nabendu's Blog

What the damn thing happened to me I don't know,I am deliberately absent to office today for some study at home.Did some study at morning ,After feeling hungry on 2PM I bought some redimate paratha from MORE ,a coke.Returned home and cooked it.At the time of cooking I eat it. After took the coke. I felt soo sleepy May be recent psychological pressure that I am facing in career is the behind it.I decided to take break after I will do the study thing.I went to sleep around 3.30pm. I saw a damn ,unwordly and unexplainable dream.I decided to write it here.Many time I saw this kind of dream with no meaning and letter I forget them. I am in dream aged about 32 years working as engineer a very good SW firm may other some kind of company,but it it's very big.After a long days of work I am tired want to do some refreshment.So I took swimming costume pack headed toward the swimming pool.I reached the place which seemed to be swimming pool which is part port large river may be the The

I was unaware about what kind of break point should I use for debugging in different places.Which one is better?What are the advantages or disadvantages of using the? ok... Hardware breakpoints need support from hardware itself ,that is the processor itself only. Where software breakpoint needs support of processor in its instruction sets only. In software break-point the development platform inject a extra INT 3/bu which is software interrupts kind of instructions in the code itself.Whenever Instruction Pointer comes here it stops the processor here may jump to a predefined ISR location.Here the debugger development platform collect the data for debugging by programmer.We can use as many SW breakpoints as we want. On the other hand hardware break do stop the processor but in different way.Normally there are hardware registers (little known dr register in x86) to configure these kind of breakpoints.Using HW breakpoints we can use it as "memory breakpoints" or instruction brea

Computing Thoughts Port or Redesign First? by Bruce Eckel July 23, 2007 Summary I received a message asking about how to decide whether to port to a new language first, redesign first, or do both at the same time. Advertisement We have a large project that is coded in language A and has existed for many years. This project now requires a redesign and at the same time we would like to recode it in language B. From your experience, would it would better to port it from language A to B first, then work on the redesign, or code it in language B with the redesign from the beginning? The advantage with the first way is that we could possible offshore the porting, but I don't know if the complexity of redesigning after the port would offset any gains in cost that offshoring would give us. This is not a simple question because most of the answer is not about the accepted right thing to do, but more about "who are you?" The answer will be different from one team to the

Semaphores in Linux are sleeping locks. Because they cause a task to sleep on contention, instead of spin, they are used in situations where the lock-held time may be long.Conversely, since they have the overhead of putting a task to sleep and subsequently waking it up, they should not be used where the lock-held time is short. Since they sleep, however, they can be used to synchronize user contexts whereas spinlocks cannot. In other words, it is safe to block while holding a semaphore. A "mutex" (or "mutual exclusion lock") is a signal that two or more asynchronous processes can use to reserve a shared resource for exclusive use. The first process that obtains ownership of the "mutex" also obtains ownership of the shared resource. Other processes must wait for for the first process to release it's ownership of the "mutex" before they may attempt to obtain it. The most common locking primitive in the kernel is the spinlock. The spinlock

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

The difference between an RTOS and a general purpose OS is really a matter of emphasis. If you asked the designer of a general purpose OS "what is the worst case latency in your OS", they would probably answer "I don't know". It isn't something that they generally worry about unless it gets so long that someone important enough complains about it. If you ask an RTOS designer the same question, they can give you a definite answer. also if you consider the memory used... then the RTOS will consume little memory & our general purpose OSs.. you know that... as the new OS release are coming out... they are occupying more memory... yeah as you said RTOS are used in Embedded Systems... The main aim in our embedded system is that... the responce should be quick... because.. these system are used in very critical situations/applications... like in our modern cars...If these cars encounter in an accident then immidiately in a fraction the airbags will be blown...