[En-Nut-Discussion] Major memory mapping changes?

Radek Podgorny radek at podgorny.cz
Tue Oct 19 13:06:22 CEST 2004


Hi,

I've been using Ethernut 1.3 so far without any serious problems. I use it to 
control some IO boards which are connected directly to the address and data 
bus. It works in a simple way where I write to *(xdata unsigned char *)
(0xe000) and the board just knows I want to talk to it and takes the data. 
Reading works the same. Unfortunately, with Ethernut 2.1, this got broken. 
The writing is still functional but when I try to read from this memory area 
(which should be AFAIK not occupied by any device) I just get all 
0xff. :-( Don't you know what could be wrong? Of course I can change the 
address of the boards to something else but I don't have time to try all 
possible combinations so I would need a hint... :-(

Thanks...
Radek Podgorny

-- 
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x98E56D84
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.egnite.de/pipermail/en-nut-discussion/attachments/20041019/a9086322/attachment-0001.pgp>


More information about the En-Nut-Discussion mailing list