Page 1 of 1
Lack of forum activity
Posted: Mon Sep 12, 2005 3:31 am
by asmlang_6
Recently, I have been continuiosly checking the 6502.org Forum for new messages, but for at least a week I haven't been seeing any orange messages or cagegories. What's going on?
Posted: Mon Sep 12, 2005 4:08 am
by 8BIT
It's not uncommon for this forum to have low traffic periods. I've been on it for several years and have seen this before.
I have not been as active lately either. I am slowly working on CF storage solutions and ethernet solutions. I hope to be able to post some results in the near future.
Don't give up... things will pick up!
Daryl
Posted: Mon Sep 12, 2005 5:49 pm
by Brian_Lyons
For many of us, the weather outside is still great - sunshine & high 80s today.
Things will likely pick up in forum when vacations are over
, it gets cold out
, and there are fewer daylight hours for outside activities
.
Yesterday was the first time I burned eproms since early May.
Posted: Tue Sep 13, 2005 2:19 am
by asmlang_6
Yesterday was the first time I burned eproms since early May.
I personally prefer EEPROMs. They can easily be written in real-time (in fact, I have ideas in my head for a customizable workbench system that has a reset vector that points to $E000 that jumps to a monitor so I can easily program the ROM from the system).
Posted: Tue Sep 13, 2005 12:50 pm
by 8BIT
I personally prefer EEPROMs. They can easily be written in real-time (in fact, I have ideas in my head for a customizable workbench system that has a reset vector that points to $E000 that jumps to a monitor so I can easily program the ROM from the system).
Check out my SBC Monitor. It has exactly what you described. I use the W command to write data from RAM to EEPROM. It relocates the "write"code into RAM (inside the keyboard buffer). You have to do that as the EEPROM will not be ready for the next CPU fetch cycle and the CPU will go off into never-never land (been there, done that!).
Daryl
Posted: Tue Sep 13, 2005 4:52 pm
by wirehead
Hm.
I've been messing with the AVR instead.
Posted: Wed Sep 14, 2005 3:31 am
by asmlang_6
You have to do that as the EEPROM will not be ready for the next CPU fetch cycle and the CPU will go off into never-never land (been there, done that!).
On the 2865 (my favorite EEPROM, which I don't have!), there is a READY//BUSY line on the EEPROM. It would probably work to hook up the RDY/BSY line to the RDY line on the 6502.
Oh, and the pre-programmed program I'm thinking of is something like this:
Code: Select all
.ORG $E000
NOP
BRK #$00
NOP
RESET_VECTOR: $E000
NMI__OR_BRK_ON_THE_65C816__VECTOR: address_of_monitor