abios-rtool-hdl-dev Mailing List for Affordable BIOS Restoration Tool
Status: Beta
Brought to you by:
jack_gassett
Menu
▾
▴
abios-rtool-hdl-dev — List for developing the HDL.
You can subscribe to this list here.
| 2005 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Jack G. <jac...@ya...> - 2005-01-30 17:08:11
|
Ok, so based on what you are saying I thought about it some more and = came up with this: In the current VHDL it takes three 8 bit writes to set the address for = 24 bits. Most flash chips that I have dealt with so far only have 19 = address lines. So that means we have 5 bits available at the top of the address. This leaves a lot of addresses available to do what we want with.=20 So we can take the last 5 address available in a 24 bit address space = and map them to the 40 pins of the header. 2^24=3D16777216 so: - Writes to address 18777212 would set the 1st 8 pins on the 40 pin = header.=20 - Writes to address 18777213 would set the 2nd 8 pins on the 40 pin = header. - Writes to address 18777214 would set the 3rd 8 pins on the 40 pin = header. - Writes to address 18777215 would set the 4th 8 pins on the 40 pin = header. - Writes to address 18777216 would set the 5th 8 pins on the 40 pin = header. We have plenty of addresses available if we want to implement another address that just sets the control pins. But the control pins are going = to change depending on what chip we are programming... Hopefully this is clear, let me know if I need to be clearer. Jack. -----Original Message----- From: abi...@li... [mailto:abi...@li...] On Behalf Of = Mike Karr Sent: Tuesday, January 25, 2005 9:38 PM To: abi...@li... Subject: Re: [Abios-rtool-hdl-dev] Ideas on how to implement a raw mode = in the VHDL? What I was thinking would be more along the lines of having different modes accessable by writing to a set of registers in the address space. For normal mode we don't use the address space mapped directly to the device. We would write to one register to output data and another to change the address. We could make the address register increment automatically so this wouldn't effect right speeds very much at all. We would alos have another register to put the device into raw mode and anotehr few registers to control the pins. This seems like the wisest course to me. Even though we have limited room on the device I think it could be done if written properly. --- Jack Gassett <jac...@ya...> wrote: > Hello, I am sending this message to everyone that > has expressed an interest > in the Affordable BIOS Restoration Tool project on > SourceForge. I=12m also > sending this to the mailing list to archive the > thread.=20 >=20 > =20 >=20 > After talking with Mike Karr he pointed out that, it > would be beneficial to > have a raw programming mode in the VHDL so that all > pins could be controlled > from software. That way devices with different > pinouts can be handled. I was > originally thinking that a new ucf file would be > created for different > device types but I think I like Mike=12s idea better. > So I just wanted to get > everyone=12s input on the best way to implement a raw > mode. >=20 > =20 >=20 > I am thinking one way is to detect when a 10101010 > is written to the address > and then a reset is triggered, a 010101010 is then > written to the same data > port to verify raw mode. This sequence will trigger > raw mode and since there > are 40 pins on the header 5 subsequent data writes > will set those 40 pins. > Any thoughts? >=20 > =20 >=20 > Thanks, >=20 > Jack. >=20 >=20 > --=20 > Internal Virus Database is out-of-date. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.6.13 - > Release Date: 1/16/2005 > =20 >=20 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Abios-rtool-hdl-dev mailing list Abi...@li... https://lists.sourceforge.net/lists/listinfo/abios-rtool-hdl-dev --=20 Internal Virus Database is out-of-date. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 1/16/2005 =20 --=20 Internal Virus Database is out-of-date. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 1/16/2005 =20 |
|
From: Mike K. <fr...@sb...> - 2005-01-26 04:38:20
|
What I was thinking would be more along the lines of having different modes accessable by writing to a set of registers in the address space. For normal mode we don't use the address space mapped directly to the device. We would write to one register to output data and another to change the address. We could make the address register increment automatically so this wouldn't effect right speeds very much at all. We would alos have another register to put the device into raw mode and anotehr few registers to control the pins. This seems like the wisest course to me. Even though we have limited room on the device I think it could be done if written properly. --- Jack Gassett <jac...@ya...> wrote: > Hello, I am sending this message to everyone that > has expressed an interest > in the Affordable BIOS Restoration Tool project on > SourceForge. Im also > sending this to the mailing list to archive the > thread. > > > > After talking with Mike Karr he pointed out that, it > would be beneficial to > have a raw programming mode in the VHDL so that all > pins could be controlled > from software. That way devices with different > pinouts can be handled. I was > originally thinking that a new ucf file would be > created for different > device types but I think I like Mikes idea better. > So I just wanted to get > everyones input on the best way to implement a raw > mode. > > > > I am thinking one way is to detect when a 10101010 > is written to the address > and then a reset is triggered, a 010101010 is then > written to the same data > port to verify raw mode. This sequence will trigger > raw mode and since there > are 40 pins on the header 5 subsequent data writes > will set those 40 pins. > Any thoughts? > > > > Thanks, > > Jack. > > > -- > Internal Virus Database is out-of-date. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.6.13 - > Release Date: 1/16/2005 > > |
|
From: Jack G. <jac...@ya...> - 2005-01-26 01:19:13
|
Hello, I am sending this message to everyone that has expressed an =
interest
in the Affordable BIOS Restoration Tool project on SourceForge. I=92m =
also
sending this to the mailing list to archive the thread.=20
=20
After talking with Mike Karr he pointed out that, it would be beneficial =
to
have a raw programming mode in the VHDL so that all pins could be =
controlled
from software. That way devices with different pinouts can be handled. I =
was
originally thinking that a new ucf file would be created for different
device types but I think I like Mike=92s idea better. So I just wanted =
to get
everyone=92s input on the best way to implement a raw mode.
=20
I am thinking one way is to detect when a 10101010 is written to the =
address
and then a reset is triggered, a 010101010 is then written to the same =
data
port to verify raw mode. This sequence will trigger raw mode and since =
there
are 40 pins on the header 5 subsequent data writes will set those 40 =
pins.
Any thoughts?
=20
Thanks,
Jack.
--=20
Internal Virus Database is out-of-date.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 1/16/2005
=20
|
|
From: Jack G. <jac...@ya...> - 2005-01-19 03:48:23
|
Test -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 1/16/2005 |