The memory map is about to change in order to make non-cacheable transfers 
easier. This breaks software binary compatibility and you'll need to recompile 
all applications using the hardware directly according to the new headers 
(software/include/hw/...).

The patch is merged, but not tested yet.

Sébastien


----------  Forwarded Message  ----------

Subject: FYI: Flash
Date: Wednesday 07 July 2010, 00:46:32
From: Michael Walle <[email protected]>
To: Sébastien Bourdeauducq <[email protected]>


Hi Sebastien,

NOR flash write support is working:
 - added support for writing (only halfword write access supported)
 - added support for byte/halfword read access
 - swapped byte order (we have to use the -Byte_swap filter in srec_cat)

Modified conbus:
 - ignores MSB, which creates a shadow memory area of 0000_0000-3fff_ffff at 
8000_0000-ffff_ffff
 - use only 2 bits for slave selection, which gives us 4 256MB segements

New memory map:
 - NOR         0x00000000 (shadow @0x80000000)
 - USB          0x20000000 (shadow @0xa0000000)
 - FML bridge     0x40000000 (shadow @0xc0000000)
 - CSR bridge     0x60000000 (shadow @0xe0000000)

So we have to replace every 0x8000XXXX with 0xe000XXXX within the milkymist 
headers.

I'll checkin the changes and put my milkymist repo on serverraum tomorrow. 
I'll send a mail to the ML, too.

btw. you can create a (X)SVF with BPI programming. So we could distribute this 
file for initial programming/loading of a programming 'bridge'. My bus pirate 
arrived today. If i find time, i'll check if it openocd can replay this (x)svf 
file.

gn8 michael.

-----------------------------------------
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkym...@freenode
Webchat: www.milkymist.org/irc.html
Wiki: www.milkymist.org/wiki

Reply via email to