Memory map and acces in Microblaze

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
I create with "Pheripheral wizard" (EDK) perephiral module, using
provided templates (slave OPB).
Create one register based at BASEADDR.
After using this code:
        Xuint32 pointer=USE_ADDRES;
      for(x=0;x<15;x++)
      {
        *pointer=x+1;
        printf("Addr = %X data = %X\r",pointer,*pointer);
         pointer++;
      }
Expect that every address has contain x+1.
But have:
Addr = 83000000 data = 1
Addr = 83000004 data = 0
Addr = 83000008 data = 3
Addr = 8300000C data = 0
Addr = 83000010 data = 5
Addr = 83000014 data = 0
Addr = 83000018 data = 7
Addr = 8300001C data = 0
Addr = 83000020 data = 9
Addr = 83000024 data = 0
Addr = 83000028 data = B
Addr = 8300002C data = 0
Addr = 83000030 data = D
Addr = 83000034 data = 0
Addr = 83000038 data = F

?????

PS sorry for bad english


Re: Memory map and acces in Microblaze

Quoted text here. Click to load it

With 'pointer' being an integer type rather than a pointer type, you
should not expect your program to behave the way you think it should.
Fix the declaration for 'pointer' and try again.

--
Dan Henry

Re: Memory map and acces in Microblaze
Sorry, error in listing, "pointer" declared at "Xuint32 *pointer"


Re: Memory map and acces in Microblaze

Quoted text here. Click to load it

What do you mean by "one register"?  Your program is incrementing
addresses as if multiple registers or memory exists.  If you have
created only one register location, could it be that there isn't
anything at addresses 0x83000004, 0x8300000C, 0x83000014, etc. and that
addresses 0x83000008, 0x83000010, 0x83000018, etc. are aliases for the
single register at 0x83000000?

--
Dan H.

Re: Memory map and acces in Microblaze
Write to register true at all address range  0x83000000  0x830000FF
(latch to register with write strobe, no analysis address range).
When reading, in the same way not analysing address.
Therefore, read must be equal write.
Hm-m, need check acknowledgement logic, tomorrow.


Re: Memory map and acces in Microblaze
Quoted text here. Click to load it

What are you talking about?  You need to include adequate context,
without which your article is useless.  Don't assume the reader has
access to anything that has gone before.  See my sig. if you must
use the foul google interface to usenet.

--
"If you want to post a followup via groups.google.com, don't use
 the broken "Reply" link at the bottom of the article.  Click on
We've slightly trimmed the long signature. Click to see the full one.

Site Timeline