Embedded driver Development for a CDRW drive-->Having problems with new CDRW drives accepting any packet commands

Article View: sci.electronics.design

Article #2737

Back to sci.electronics.design Previous Next

#2737

From: LRCR
Date: Sat, 29 Apr 2006 12:58

35 lines
3168 bytes

Many thanks for those who replied to this issue.  Unfortunately, I
already tried the suggession and I still have  problems with sending
packet command to the CDRW and getting a returned error.  If I can get
more suggession in approaching this issue, I'll he happy with any
reply regarding this issue.  Below, I am reposting my previous message
on this issue.


 I am currently developing a driver to a CDRW drive in an embedded
 system. I am currently having problems with new CDRW drives accepting
 any packet commands. (The ATA commands are handled.) The
 initialization sequence that I am using is as follows:



1) Hardware reset (Delay 10 seconds after reset is released.)

 2) Software reset - setting then clearing the SRST bit in the Device
 control register

 3) Identify Packet Device command (code A1) followed by reading the
 256 words of device information.

 (I have verified that all of the timing is correct.)

 This sequence has been successful in pre 2004 CDRW drives (TEAC
 CD-W552D, SONY CRX230AD). However, in newer CDRW drives (TEAC
 CD-W552GB, SONY CRX230AD) as soon as I set the command register for a
 PACKET COMMAND (command code A0), the check (or error) bit is set in
 the status register and the error register indicates a sense code of
 06. Is there an additional initialization step that I am missing? I
 have gone through the ATA/ATAPI 5 Spec and have not found anything
 that I am missing. 
 
 Chris

Technical Details

Message-ID: <gtn652p3aqg81tcd8p9d81ifnskcsb6hp4@4ax.com>

Path:

arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Thread: 112d1e,a56bc0373ab6a2f0,start
X-Google-Thread: fe99a,a56bc0373ab6a2f0,start
X-Google-Thread: 1118be,a56bc0373ab6a2f0,start
X-Google-Thread: f849b,a56bc0373ab6a2f0,start
X-Google-Thread: 10228c,a56bc0373ab6a2f0,start
X-Google-Thread: 10d137,a56bc0373ab6a2f0,start
X-Google-Thread: ff6c9,a56bc0373ab6a2f0,start
X-Google-Attributes: gid112d1e,gidfe99a,gid1118be,gidf849b,gid10228c,gid10d137,gidff6c9,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 29 Apr 2006 07:58:14 -0500
From: LRCR <xyz@ix.netcom.com>
Newsgroups: sci.electronics.design,sci.electronics,alt.electronics,sci.electronics.components,comp.arch.embedded,codewarrior.embedded,alt.engineering.electrical,alt.cd-rom
Subject: Embedded driver Development for a CDRW drive-->Having problems with new CDRW drives accepting any packet commands
Date: Sat, 29 Apr 2006 08:58:03 -0400
Message-ID: <gtn652p3aqg81tcd8p9d81ifnskcsb6hp4@4ax.com>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 36
X-Trace: sv3-tdHkIU0x+zoHpRmluzYllh+nV2uxTyUZrQTbvQJL62DauRj/9izSXoru/1+yukDZ/j/xYuk6X6EWhd5!IKlnvK82s0nBKuOMjw73UzjDnEKw9B62xE3hb2CmUKCaZ4PxMse0m6lEK+5Z7q+eDeGbAvsk
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.32