SAM Dallas module

2006-12-04 Thread Chris Pile
Hi Folks,

I tried emailing Edwin about this, but all email addresses I found for him 
simply bounced.  So I'm posting
here instead...

Does anyone have programming information for Edwin's SAM Dallas clock module?  
Particularly the port
addresses and how to read/write to the Dallas 114-bytes of scratch-ram?  Also, 
does Simcoupé save the
Dallas module's RAM contents on exit - thus emulating the persistent qualities 
of the Dallas scratch-ram?

Cheers,
Chris.




RE: SAM Dallas module

2006-12-04 Thread Simon Owen
Chris Pile wrote:
 I tried emailing Edwin about this, but all email addresses I 
 found for him simply bounced.  So I'm posting here instead...

The last one he used on the list is edwin.blinkathome.nl - if he doesn't
spot this I'll check when he's next on MSN.


 Does anyone have programming information for Edwin's SAM 
 Dallas clock module? Particularly the port addresses and how 
 to read/write to the Dallas 114-bytes of scratch-ram?

Try this for the data sheet:
http://www.embeddedarm.com/downloads/Components/12887.pdf
Clock.cpp in the SimCoupe source might also help: http://tinyurl.com/y8b53s

The original DALLAS has 128 bytes of nvram, with the bottom 14 used for
clock values.  Reading and writing the full 128 range is done in the same
way, with the RTC updating the lower ones automatically.

Bit 8 of the port address is 0 for register select and 1 for data.  So
writing 123 to port 00EF would select location 123 in RAM, then writing a
byte to port 01EF would write it to that location in nvram.  For the
current (original) chip only the bottom 7 bits of the location are used, but
the new chip support I'll add will use all 8 bits.


 Also, does Simcoupé save the Dallas module's RAM contents on exit - 
 thus emulating the persistent qualities of the Dallas scratch-ram?

Not currently, as I didn't realise that worked with the original device.  I
can implement that tonight if you want something to play with.  :-)

Si



Re: SAM Dallas module

2006-12-04 Thread Wayne Weedon

Chris Pile wrote:

Hi Folks,

I tried emailing Edwin about this, but all email addresses I found for him 
simply bounced.  So I'm posting
here instead...

Does anyone have programming information for Edwin's SAM Dallas clock module?  
Particularly the port
addresses and how to read/write to the Dallas 114-bytes of scratch-ram?  Also, 
does Simcoupé save the
Dallas module's RAM contents on exit - thus emulating the persistent qualities 
of the Dallas scratch-ram?

  


Chris..  Hope you are all well.   Steve Parry-Thomas is more likely than 
most to know  how to contact Edwin.


Regards
 Wayne...


--
---
Wayne M Weedon  Email: [EMAIL PROTECTED]
Fdos Design Poole UK  
Tel +44-1202-677025Fax +44-1202-770515  Mobile: 07774 439915


Specialists in small batch  Production Mechanical/Electrical Engineering
---



Re: SAM Dallas module

2006-12-04 Thread Chris Pile
Hi Si,

 Chris Pile wrote:
 I tried emailing Edwin about this, but all email addresses I
 found for him simply bounced.  So I'm posting here instead...

 The last one he used on the list is edwin.blink at home dot nl - if
 he doesn't spot this I'll check when he's next on MSN.


No problem.  I won't need to bother Edwin now, as all I wanted was the port 
address
for the Dallas chip.  You kindly supplied that in your reply!  I had 
recollectrions of the
address / data accessing of the chip from way back - when I played around with 
PC
CMOS stuff.  Ports 112 (address) and 113 (data) sprang to mind!  Strange the 
silly
things people tend to remember!  :-)


 Chris Pile wrote:
 Also, does Simcoupé save the Dallas module's RAM contents on exit -
 thus emulating the persistent qualities of the Dallas scratch-ram?

 Not currently, as I didn't realise that worked with the original device.  I
 can implement that tonight if you want something to play with.  :-)


:-)  That would be great.  No rush though, as I can't really start playing 
until the weekend.

Cheers,
Chris.




Re: SAM Dallas module

2006-12-04 Thread Chris Pile
Hi Wayne,

 Chris..  Hope you are all well.   Steve Parry-Thomas is more likely than 
 most to know  how to contact Edwin.

You were quite right!  Steve emailed me Edwin's address.  However, I won't need 
to
bother him now, as all I wanted was the chip's port address.  Which I now have! 
 :-)

Cheers,
Chris.

P.S.  I'll email you properly soon...  Or should that be soon-ISH.  You know 
what I'm
like for that...  ;-)