MPC5674F Processor and 32-bit address

  • Thread starter Thread starter thiefjack
  • Start date Start date
  • Tags Tags
    Processor
AI Thread Summary
The discussion revolves around locating the 32-bit address of the Flash B Shadow Block in the MPC5674F processor's memory address space. Participants express uncertainty about how to begin solving the problem and whether Flash B's address is restricted to a specific range. The consensus is that the goal is to identify Flash B's location, but concerns are raised about the risks of probing random memory addresses, which could disrupt other devices. There is a suggestion to explore addresses that are multiples of Flash B's size, assuming a handshake sequence is in place. Overall, the conversation highlights the complexities and potential dangers of memory address probing in this context.
thiefjack
Messages
11
Reaction score
0

Homework Statement


I'm not sure where to start with the following question. Can anyone point me in the right direction? It is part of some challenging questions I was given and I'd like to try to learn how to solve them.

Assume unsigned32 X; Consider the MPC5674F processor. The 32 bit address of the Flash B Shadow Block starts at X. Use whatever resources you have to find X.

Homework Equations



None.

The Attempt at a Solution



I'm not sure even where to start! I was hoping someone could point me in the right direction towards at least starting off.
 
Physics news on Phys.org
It's not clear what the goal is here, is it to find where Flash B is located in the memory address space? Is it restricted to a range of addresses or could it be anywhere? Assuming that there's some way to write and read memory to identify the Flash B address range, it probably wouldn't be a good idea to be writing and reading random locations in the memory address space, since that it could mess up other devices that also use a part of the memory address space.
 
rcgldr said:
It's not clear what the goal is here, is it to find where Flash B is located in the memory address space? Is it restricted to a range of addresses or could it be anywhere? Assuming that there's some way to write and read memory to identify the Flash B address range, it probably wouldn't be a good idea to be writing and reading random locations in the memory address space, since that it could mess up other devices that also use a part of the memory address space.

Yes, the goal is to find where Flash B is located in the memory address space.
However, I have no idea as to where I could start looking.
 
thiefjack said:
Yes, the goal is to find where Flash B is located in the memory address space. However, I have no idea as to where I could start looking.
If there is no specified range, then you need to probe every address that is a multiple of the size of Flash B, assuming there's some handshake sequence that works with any address within range of Flash B. I don't like this idea because poking a random memory locations could mess up something else.
 
Back
Top