I have a memory DIP (one of the HM62256B series chips) and the datasheet says that the memory is organized in a 32-kword x 8 bit grid but the chip only has 15 address inputs. How can the datasheet claim that the chip is organized in words when the packet only has 15-bits of address access?

A "word" is arbitrary; on an 8-bit processor, it could be 8 bits (synonymous with byte), and on a 16-bit processor, it could be 16 bits. In this case, your memory has an 8 bit word. It only has 32,768 locations, which requires exactly 15 address lines.

I believe that the confusion I am having arose from the ambiguity of whether a kilobit is equal to 1,000 bits or 1,024 bits. I have seen both definitions.

Click to expand...

It's frustating and confusing. This practice carries over to hard drive and other storage devices as well. Sometimes kilo/mega/etc is a 1024 based number, sometimes kilo/mega/gig/etc is a 1000 based number, and most annoying of all is when they mix the two, such as 1 million bytes. First is the 1000 system, second is the 1024 system. Until you work with it, you can't exactly figure out the number of usable bits, especially with hidden bad sectors, etc.

It's frustating and confusing. This practice carries over to hard drive and other storage devices as well. Sometimes kilo/mega/etc is a 1024 based number, sometimes kilo/mega/gig/etc is a 1000 based number, and most annoying of all is when they mix the two, such as 1 million bytes. First is the 1000 system, second is the 1024 system. Until you work with it, you can't exactly figure out the number of usable bits, especially with hidden bad sectors, etc.

Click to expand...

As an experienced person in electronics, would you conclude that the potential loss of 24 bits would affect larger-scaled systems badly? Can they be safely ignored?

As an experienced person in electronics, would you conclude that the potential loss of 24 bits would affect larger-scaled systems badly? Can they be safely ignored?

Click to expand...

One potential problem: An operating system computes drive space in megabytes by using integer division. It divides say 1,000,000,000 bytes by 1024 to get the number of kilobytes = 976562 KB. In this case, it rounds down - but then another operating system decides to round up to 976563 KB. This creates a size incompatibility - for example, duplicating a backup. Now if the sizes were multiples of 1024, there'd be no problem.

It's not the loss of just 24 bits, either. On a large scale, a 1 GB drive is 1,000,000,000 bytes instead of 1,073,741,824 bytes - a whole 7.3%. A terabyte drive is usually only 931 GB. As you can see, a considerable amount of space is not actually there.