Altera_Forum
Honored Contributor
Honored Contributorhow to use CF card in uclinux?
I use cyclone board and the system detected CF card, but have error.
so I can't format CF card use command: fdisk /dev/hda help me! thanks a lot.Forum Discussion
16 Replies
Altera_Forumwhat error message are you receiving?
- Altera_Forum
<div class='quotetop'>QUOTE </div>
--- Quote Start --- what error message are you receiving?[/b] --- Quote End --- CF: ctl=1 hda: é‘é‰é?霽??????????????? ATA DISK drive Using anticipatory io scheduler ide0 at 0x80900800-0x80900807,0x80900838 on irq 8 hda: max request size: 1024KiB hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda: 3959483392 sectors (2027255 MB) w/30209KiB Cache, CHS=65535/255/63 hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda:hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } end_request: I/O error, dev hda, sector 0 Buffer I/O error on device hda, logical block 0 hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } end_request: I/O error, dev hda, sector 0 Buffer I/O error on device hda, logical block 0 unable to read partition table - Altera_Forum--- Quote Start --- originally posted by ken@Dec 16 2004, 03:36 PM what error message are you receiving? --- Quote End --- CF: ctl=1 hda: é‘é‰é?霽??????????????? ATA DISK drive Using anticipatory io scheduler ide0 at 0x80900800-0x80900807,0x80900838 on irq 8 hda: max request size: 1024KiB hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda: 3959483392 sectors (2027255 MB) w/30209KiB Cache, CHS=65535/255/63 hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda:hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } end_request: I/O error, dev hda, sector 0 Buffer I/O error on device hda, logical block 0 hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } ide0: reset: success hda: read_intr: status=0x51 { DriveReady SeekComplete Error } hda: read_intr: error=0x04 { DriveStatusError } end_request: I/O error, dev hda, sector 0 Buffer I/O error on device hda, logical block 0 unable to read partition table
- Altera_Forum
why does no one answer this question?
http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/mad.gif come on, experts, help us~ http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/sad.gif - Altera_Forum
I'm sorry, but your post came in at 9pm on a Friday night here (which incidently is well after our business hours). I'll pass it forward to one of my co-workers who knows more about this than I do.
- Altera_Forum
Hi Xlking,
Are you using the Linux core Microtronix provides, or your own customized core? It looks like the driver could not get correct data from the CF card. If you are using a Cyclone board from Altera, the booting message "CF: ctl=1" means the CF controller is not powered, thus won't work correctly. You need a message like "CF: ctl=3" in order to make the Linux driver work. I am inclined to think it is a hardware issue. Regards, wentao - Altera_Forum
I use Microtronix linux core and CF_Component and CF_qp which was downloaded from this forum, I think it maybe the problem of hardware, I use altera cyclone board;
<div class='quotetop'>QUOTE </div> --- Quote Start --- If you are using a Cyclone board from Altera, the booting message "CF: ctl=1" means the CF controller is not powered, thus won't work correctly. You need a message like "CF: ctl=3" in order to make the Linux driver work.[/b] --- Quote End --- but how to power the CF controller? is there anything need to be notice such as pin assignment when use CF card of altera's cyclone board? thank you. - Altera_Forum
You are using the pre-built linux.sof core that is included with the Nios II Linux distribution? It has all the pins appropriately assigned already. If you are using your own custom core, I can post the pin connections and pin assignments that are needed.
Dennis Scott Microtronix Datacom Ltd. - Altera_Forum
<div class='quotetop'>QUOTE </div>
--- Quote Start --- If you are using your own custom core, I can post the pin connections and pin assignments that are needed.[/b] --- Quote End --- thank you, please email pin assignments to me.let me try it again.hope it can work. my email: xlking@ujs.edu.cn - Altera_Forum
First, you must name the compact flash component "cf" in SOPC builder so that the kernel build will find it.
Once you have the component built into your SOPC block you need to attach and assign pins. Inputs: detect_to_the_cf -- B13 intrq_to_the_cf -- G17 iordy_to_the_cf -- G14 Outputs: addr_from_the_cf[0] -- H17 addr_from_the_cf[1] -- H18 addr_from_the_cf[2] -- H19 addr_from_the_cf[3] -- W18 addr_from_the_cf[4] -- K15 addr_from_the_cf[5] -- J18 addr_from_the_cf[6] -- J17 addr_from_the_cf[7] -- J14 addr_from_the_cf[8] -- H14 addr_from_the_cf[9] -- J20 addr_from_the_cf[10] -- J15 atasel_n_from_the_cf -- D13 cs_n_from_the_cf[0] -- H20 cs_n_from_the_cf[1] -- U19 iord_n_from_the_cf -- G19 iowr_n_from_the_cf -- G20 power_from_the_cf -- M13 reset_n_from_the_cf -- unconnected (the board does not give direct access to the reset line) rfu_from_the_cf -- U20 we_n_from_the_cf -- V18 Bidirectional: data_to_and_from_the_cf[0] -- F20 data_to_and_from_the_cf[1] -- F15 data_to_and_from_the_cf[2] -- E19 data_to_and_from_the_cf[3] -- F18 data_to_and_from_the_cf[4] -- E17 data_to_and_from_the_cf[5] -- D17 data_to_and_from_the_cf[6] -- D18 data_to_and_from_the_cf[7] -- C18 data_to_and_from_the_cf[8] -- C19 data_to_and_from_the_cf[9] -- D19 data_to_and_from_the_cf[10] -- D20 data_to_and_from_the_cf[11] -- F17 data_to_and_from_the_cf[12] -- E18 data_to_and_from_the_cf[13] -- F16 data_to_and_from_the_cf[14] -- F19 data_to_and_from_the_cf[15] -- G16 Dennis Scott Microtronix Datacom Ltd.
