Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Data2MEM Error - 33 : Matching ADDRESS_SPACE not found

13 views
Skip to first unread message

gentel

unread,
Nov 4, 2009, 6:42:30 AM11/4/09
to
hi,all

I am trying to target the XUP by Digilent with my big application. My
settings are almost there, but for some reason I get the following output:

..

Address Map for Processor microblaze
(0x0000000-0x5fffffff) DDR_256MB_64Mx64_rank2_row13_col10_cl2_5 sopb

(0x0000000-0x000ffff) dlmb_cntrl slmb
(0x0000000-0x000ffff) ilmb_cntrl slmb
(0x40600000-0x4060ffff) RS232_Uart_1 sopb
(0x41400000-0x4140ffff) debug module sopb

ERROR:Data2MEM:33 - Matching ADDRESS_SPACE for code segment #4 not found
in 'sys
tem_stub_bd.bmm'.
Code segment #4 occupies [0x50000000:0x5002B357]
thanks for your help..

---------------------------------------
This message was sent using the comp.arch.fpga web interface on
http://www.FPGARelated.com

Brian Drummond

unread,
Nov 4, 2009, 6:53:54 PM11/4/09
to
On Wed, 04 Nov 2009 05:42:30 -0600, "gentel" <gent...@163.com> wrote:

>hi,all
>
>I am trying to target the XUP by Digilent with my big application. My
>settings are almost there, but for some reason I get the following output:
>
>..
>
>Address Map for Processor microblaze
> (0x0000000-0x5fffffff) DDR_256MB_64Mx64_rank2_row13_col10_cl2_5 sopb
>
> (0x0000000-0x000ffff) dlmb_cntrl slmb
> (0x0000000-0x000ffff) ilmb_cntrl slmb
> (0x40600000-0x4060ffff) RS232_Uart_1 sopb
> (0x41400000-0x4140ffff) debug module sopb
>
> ERROR:Data2MEM:33 - Matching ADDRESS_SPACE for code segment #4 not found
>in 'sys
>tem_stub_bd.bmm'.
> Code segment #4 occupies [0x50000000:0x5002B357]
>thanks for your help..
>

At least three problems here:
(1) you have mapped 1.5GB of address space onto 256MB of DDR memory. That'll
work but may not do what you want.

(2) Some of that space is also mapped onto peripherals. Reading from those
regions will definitely not work.

(3) DATA2MEM inserts data into the bitfile used to configure the FPGA. It
follows that the memory being configured must be internal to the FPGA. Yet
according to the address map it is mapped into the DDR module..

- Brian

gentel

unread,
Nov 4, 2009, 8:14:12 PM11/4/09
to
>On Wed, 04 Nov 2009 05:42:30 -0600, "gentel" <gent...@163.com> wrote:
>thanks for your reply,i got something wrong. the DDR memmory is
(0x50000000-0x5fffffff).but,what should i do if i put the software and
hardware bits into the board????

Brian Drummond

unread,
Nov 5, 2009, 6:41:08 AM11/5/09
to
On Wed, 04 Nov 2009 19:14:12 -0600, "gentel" <gent...@163.com> wrote:

>>On Wed, 04 Nov 2009 05:42:30 -0600, "gentel" <gent...@163.com> wrote:
>>thanks for your reply,i got something wrong. the DDR memmory is
>(0x50000000-0x5fffffff).but,what should i do if i put the software and
>hardware bits into the board????

what do you mean by putting bits into the board?

If you mean loading the DDR memory with this code segment after power-up, the
usual approach is to write a bootstrap loader - which has to be mapped into
internal memory - which loads this segment from non-volatile storage (e.g. flash
memory, or possibly Ethernet or even the UART.

Alternatively, map this entire segment into internal memory, if there is enough
memory. Or re-write it to use less space.

- Brian

0 new messages