Unfortunately my code will eventually use RAM (EEPROM actually), I simply don't see a way around it if you want to write to an IDE hard drive. Since when you write you have to write a whole sector you have to HAVE the whole sector ready to write (512 bytes). If you are just using the disk raw then I guess you could generate your sector on the fly, but if you are modifying a sector (like what I will be doing) you need to store it locally, and a 16 series PIC just doesn't have enough general purpose ram to do that. For various reasons I don't want to release my code, at least for the moment (wouldn't be of much use anyways since I tend to comment AFTER the project is done! :( TTYL > -----Original Message----- > From: pic microcontroller discussion list > [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of M. Adam Davis > Sent: Monday, March 18, 2002 07:58 > To: PICLIST@MITVMA.MIT.EDU > Subject: Re: [PIC]: IDE interfacing > > > I've been hoping someone would release IDE code that doesn't use RAM - > is this something you can give out? I'd like a copy of whatever you > currently have... > > -Adam > > Herbert Graf wrote: > > >Actually I was just looking at your site and you seem to be doing almost > >exactly what I'm doing with regards to accessing the IDE device > (except that > >I don't have any ram, I just output whatever the drive sends to me to the > >serial port, will be adding some RAM later). It's weird, I must > be missing > >something pretty basic. I guess I'll just have to keep on experimenting. > >Thanks, TTYL > > > >>-----Original Message----- > >>From: pic microcontroller discussion list > >>[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Barry Michels > >>Sent: Sunday, March 17, 2002 16:47 > >>To: PICLIST@MITVMA.MIT.EDU > >>Subject: Re: [PIC]: IDE interfacing > >> > >> > >>When I was testing my design, I hand clocked sectors out on the > >>breadboard, > >>so I imagine 9600 should be fast enough. :) Once your > >>registers are setup > >>properly, just clock out the data without changing CS or > anything else. I > >>don't think it would hurt anything to deselect the drive, but I > >>didn't have > >>to in my design. > >> > >>The EC command is just like any other sector access command. > >>Just setup the > >>registers and clock out the data as fast or slow as you want. > >> > >>Barry > >>http://www.barrymichels.com/ide > >> > >>My friends think I'm weird for finding it fun to sit inside, > >>hunched over an > >>electronics table when there's plenty of stuff to do outside. :) > >> > >>----- Original Message ----- > >>From: "Herbert Graf" > >>To: > >>Sent: Sunday, March 17, 2002 4:40 PM > >>Subject: [PIC]: IDE interfacing > >> > >> > >>>Just for fun (fun? it's weird what I find fun...) I'm trying to > >>> > >>interface > >>a > >> > >>>16F877 to a laptop harddrive (possible for massive datalogging in the > >>>future, haven't decided yet). I know some others here have > gotten things > >>>working and I've been reading alot of the hits google gives me the the > >>> > >>most > >> > >>>simple of things I haven't been able to find. I'm driving to > >>> > >>implement the > >> > >>>EC command (drive identify) and it's kind of working (I do get > >>> > >>some of the > >> > >>>stuff back correctly) but I'm also seeing prior register > >>> > >>accesses showing > >>up > >> > >>>and things like that. Is there anything special about reading the 256 > >>> > >>words > >> > >>>from the drive? Does it have to be done within a maximum > amount of time? > >>>(right now I'm pumping every word down a 9600bps serial line > >>> > >>one by one). > >> > >>>Can I simply leave the CS and AD lines and strobe the RDb line for each > >>>word? Do I have to poll the status register between every read > >>> > >>of the data > >> > >>>register? Is there something fundemental I'm missing here? > >>> > >>>I have started wading through the 475 pages of the ATA6 spec trying to > >>> > >>find > >> > >>>my answers but I'm hoping the list will be faster. What I > really want is > >>> > >>the > >> > >>>waveforms of a sector read. Thanks for any info. TTYL > >>> > >>>-- > >>>http://www.piclist.com hint: To leave the PICList > >>>mailto:piclist-unsubscribe-request@mitvma.mit.edu > >>> > >>> > >>-- > >>http://www.piclist.com hint: To leave the PICList > >>mailto:piclist-unsubscribe-request@mitvma.mit.edu > >> > >> > >> > > > >-- > >http://www.piclist.com hint: To leave the PICList > >mailto:piclist-unsubscribe-request@mitvma.mit.edu > > > > > > > > > > > > -- > http://www.piclist.com hint: PICList Posts must start with ONE topic: > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads > > > -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads