Re: [Proj 4] don't seem to be accessing data with accessDRAM

[[Instr] Albert Chae]

Are you sure the address in DRAM you are trying to access is
"block-aligned"? Also, are you passing it the block_size properly?
Remember it requires a TransferUnit.

Albert

On Mon, 11 Aug 2008, Jeremy Cowles wrote:

> If you haven't already, I would step through it with gdb. Even though you are
> printing the values to screen, maybe stepping through the code line-by-line
> will make something jump out at you.
>
> Or maybe you can get Albert or a TA to look at your code...
>
>
>
> "Mark Stephen Teixeira" <mar...@imail.EECS.Berkeley.EDU> wrote in message
> news:g7qkmd$edq$1...@agate.berkeley.edu...
>> We've used printf on almost every line. We're explicitly passing the base
>> pointer to the 'data' array member of the cacheBlock struct to accessDRAM.
>> This
>> looks correct to us, but obviously isn't-- any hints?
>>
>> In article <g7qjtq$16a4$1...@geode.berkeley.edu>, "Jeremy Cowles"
>> <jeremy...@berkeley.edu> writes:
>>>
>>> Sounds like a pointer problem, like maybe you are sending the wrong
>>> pointer
>>> to accessDRAM, but then printing the correct pointer later.
>>>
>>> You might want to try logging everything at each step around accessDRAM
>>> (or
>>> use gdb) to make sure you are sending the correct pointer and address in.
>>>
>>>
>>> "Mark Stephen Teixeira" <mar...@imail.EECS.Berkeley.EDU> wrote in message
>>> news:g7qf57$cfn$1...@agate.berkeley.edu...
>>> > Unable to figure this one out right now: accessDRAM doesn't appear to >
>>> be
>>> > pulling in any data, at least none that we can detect with our printf
>>> > statements in the code. The correct data is showing up in the GUI cache
>>> > display, but in a set that we don't expect it to. Any ideas?
>>>
>
>

[Jeremy Cowles]

[Jeremy Cowles]