Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

data bus width difference between processor and memory

fragnen

Full Member level 4
Full Member level 4
Joined
Apr 3, 2019
Messages
211
Helped
0
Reputation
0
Reaction score
1
Trophy points
18
Activity points
1,490
A processor has a 64 bit data bus and with this 64 bit data bus the processor want to write into a memory whose data bus width is 16. What can be done with the processor to write into this memory which has data bus width of 16 so thar there is no data loss of the data that is coming out of the 64 bit width data bus of processor?
 
Problems are everywhere for a person who does not know how to or perhaps does not want to use a search engine to find out answers for questions.
 
You can declare a 64 but register to temporarily store the processor data. Use a finite state machine with at least an 'enable' signal and a 'done' signal to store consecutive 16 bits into consecutive memory location with four write cycles.
 
Whose choice was it to use "a" memory of stupid-short width, and with lagging-tech 16b memory being surplus dirt why cannot you just buy 3 more?

There's material cost and then there's sitting around engineering cost. Get it done
 
Presume it's just an exercise problem. Unfortunately important information is missing, e.g. async or sync bus interface, does it expose a wait request input?
 
Presume it's just an exercise problem. Unfortunately important information is missing, e.g. async or sync bus interface, does it expose a wait request input?
It is sync bus. Is there a way to do something with the processor as it was heard it can be done with some features of processor and this way is simpler than the proposed method by Akanimo.

What do you mean by "does it expose a wait request input"?
 
Is there a way to do something with the processor as it was heard it can be done with some features of processor
Possibly, depends on which features the processor has. One possible feature would be the ability to pause a read or write cycle when receiving a wait request.
 
Presume it's just an exercise problem. Unfortunately important information is missing, e.g. async or sync bus interface, does it expose a wait request input?
It is sync bus. Is there a way to do something with the processor as it was heard it can be done with some features of processor and this way is simpler than the proposed method by
--- Updated ---

Presume it's just an exercise problem. Unfortunately important information is missing, e.g. async or sync bus interface, does it expose a wait request input?
It is sync bus. Is there a way to do something with the processor as it was heard it can be done with some features of processor and this way is simpler than the proposed method by
--- Updated ---

Is there any more solution someone can provide in terms of something available with the processor and that provides a simple solution?
 
I think, the problem is that the question isn't completely specified. I already guessed it's an exercise with half of the description missing.

We don't know which features the processor has, can it e.g. configure a 16 bit wide memory bank? If not, is it acceptable that the 16 bit memory isn't mapped continuously but accessed by 16 bit wide transfers. Means the memory can't read and written transparently as if it was 64 bit wide but must be handled specifically in software.

Barry addressed an important point. Is the question really about ASIC design?
 
I think, the problem is that the question isn't completely specified. I already guessed it's an exercise with half of the description missing.

We don't know which features the processor has, can it e.g. configure a 16 bit wide memory bank? If not, is it acceptable that the 16 bit memory isn't mapped continuously but accessed by 16 bit wide transfers. Means the memory can't read and written transparently as if it was 64 bit wide but must be handled specifically in software.

Barry addressed an important point. Is the question really about ASIC design?
FvM, this was a question from "fragnen"! From the OPs previous posts over the years, memebers who are regular here know the type of questions and coumter-responses this user is capable of.
I think posts #1 and #4 answers the OPs question. If anything else is needed the OP must ELABORATE.
 

LaTeX Commands Quick-Menu:

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top