Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++

Problem with first run

Altera_Forum
Honored Contributor II
2,449 Views

This is a newbie question. 

 

Installation and upload of the kernel and file system went smoothly on my 1s10 development board. Howerever first connection via terminal with the uClinux failed with the following message: Warning: unable to open an initial console although LED/7seg. counter did run. I will appreciate if anybody could help me. The configuration of my system and full listing of the terminal window are: 

 

- Quartus 4.1 SP2 

- Nios II 

- ByteBlaster JTAG UART 

- free RJ1 Ethernet socket 

- no CompactFlash card on the socket 

 

Listing: 

 

 

[SOPC Builder]$ nios2-terminal 

nios2-terminal: connected to hardware target using JTAG UART on cable 

nios2-terminal: "ByteBlasterII [LPT1]", device 1, instance 0 

 

nios2-terminal: Warning: The JTAG cable you are using is not supported for Nios 

nios2-terminal: II systems. You may experience intermittent JTAG communication 

nios2-terminal: failures with this cable. Please use a USB Blaster revision B 

nios2-terminal: cable or another supported cable. Please refer to the file 

nios2-terminal: errata.txt included in the Nios II development kit documents 

nios2-terminal: directory for more information. 

 

nios2-terminal: starting in terminal mode only (Control-C exits) 

 

Linux version 2.6.5-uc0 (placki@placki-mobl) (gcc version 3.3.3 (Altera Nios II 

1.0 b316))# 1 Fri Nov 26 15:39:05 CEST 2004 

 

 

uClinux/Nios II 

Altera Nios II support © 2004 Microtronix Datacom Ltd. 

On node 0 totalpages: 4096 

DMA zone: 0 pages, LIFO batch:1 

Normal zone: 4096 pages, LIFO batch:1 

HighMem zone: 0 pages, LIFO batch:1 

Built 1 zonelists 

Kernel command line: root=/dev/mtdblock0 ro 

PID hash table entries: 16 (order 4: 128 bytes) 

Memory available: 14512k/4096k RAM, 0k/0k ROM (1365k kernel code, 303k data) 

Calibrating delay loop... 37.27 BogoMIPS 

Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) 

Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) 

Mount-cache hash table entries: 512 (order: 0, 4096 bytes) 

POSIX conformance testing by UNIFIX 

NET: Registered protocol family 16 

Serial: JTAG UART driver $Revision: 1.3 $ 

ttyJ0 at MMIO 0x80920820 (irq = 1) is a jtag_uart 

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize 

smc_probe: 75000 Khz Nios 

SMSC LAN91C111 Driver (v2.1), (Linux Kernel 2.6) 

eth0: SMC91C11xFD(rev:1) at 0x80910300 IRQ:6 MEMSIZE:8192b NOWAIT:0 ADDR: 00:07: 

ed:0a:a7:fd 

smc_probe: 75000 Khz Nios 

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 

ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx 

CF: ctl=1 

hda: 3SYSTEM SSSCF016MAA, CFA DISK drive 

Using anticipatory io scheduler 

ide0 at 0x80920900-0x80920907,0x80920938 on irq 5 

hda: max request size: 128KiB 

hda: 31744 sectors (16 MB) w/2KiB Cache, CHS=248/4/32 

hda: hda1 

microtronix[mtd]: RAM probe address=0x200000 size=0x1ec000 

Creating 1 MTD partitions on "RAM": 

0x00000000-0x001ec000 : "ROMfs" 

microtronix[mtd]: set ROMfs to be root filesystem 

NET: Registered protocol family 2 

IP: routing cache hash table of 512 buckets, 4Kbytes 

TCP: Hash tables configured (established 1024 bind 2048) 

NET: Registered protocol family 1 

NET: Registered protocol family 17 

VFS: Mounted root (romfs filesystem) readonly. 

Freeing unused kernel memory: 48k freed (0x1186000 - 0x1191000) 

Warning: unable to open an initial console. 

 

Regards, 

Piotr.
0 Kudos
10 Replies
Altera_Forum
Honored Contributor II
692 Views

Sounds like its possibly a problem with the console device node. 

 

In the filesystem project that you have, can you double check that there's a file called: 

 

<project>/target/dev/@console,c,5,1 

 

If the file doesn&#39;t exist, try creating a blank file with the name I just provided. Re-build, and re-upload your filesystm project as detailed in the Getting Started Guide. 

 

I&#39;m about to leave for the weekend but I&#39;ll be back on Monday morning if my advice above didn&#39;t work.
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

Thaks for your help.  

 

This is weird but I didn&#39;t have /dev/ subdirectory under my filesystem project at all...
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

oh... hmm... if you build a new filesystem project, does it include the /dev directory? I believe you need to enable the "base" package when configuring the filesystem project through the "new project wizard".

0 Kudos
Altera_Forum
Honored Contributor II
692 Views

Yes, but the weird thing is that I did it. Second attempt to build a new filesystem from the scratch was OK. Anyway thanks for your help again. 

 

Piotr.
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

TO_BE_DONE

0 Kudos
Altera_Forum
Honored Contributor II
692 Views

Looking at the kernel commandline, I noticed that you passed: 

 

root=/dev/hda rw 

 

/dev/hda represents the entire disk/drive. What you want is to specify a partition. In your case, that would be the first partition. 

 

So your kernel command line should read: 

 

root=/dev/hda1 rw 

 

Give that a try... I think that should solve the problem.
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

 

--- Quote Start ---  

originally posted by ken@Nov 30 2004, 11:12 AM 

looking at the kernel commandline, i noticed that you passed: 

 

root=/dev/hda rw 

 

/dev/hda represents the entire disk/drive.  what you want is to specify a partition.  in your case, that would be the first partition. 

 

so your kernel command line should read: 

 

root=/dev/hda1 rw 

 

give that a try... i think that should solve the problem. 

--- Quote End ---  

 

another error: 

<div class='quotetop'>QUOTE </div> 

--- Quote Start ---  

On node 0 totalpages: 4096 

  DMA zone: 0 pages, LIFO batch:1 

  Normal zone: 4096 pages, LIFO batch:1 

  HighMem zone: 0 pages, LIFO batch:1 

Built 1 zonelists 

Kernel command line: root=/dev/hda1 rw 

PID hash table entries: 16 (order 4: 128 bytes) 

Memory available: 14480k/4096k RAM, 0k/0k ROM (1394k kernel code, 306k data) 

Calibrating delay loop... 24.78 BogoMIPS 

Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) 

Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) 

Mount-cache hash table entries: 512 (order: 0, 4096 bytes) 

POSIX conformance testing by UNIFIX 

NET: Registered protocol family 16 

Serial: JTAG UART driver $Revision: 1.3 $ 

ttyJ0 at MMIO 0x80920820 (irq = 1) is a jtag_uart 

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize 

smc_probe: 50000 Khz Nios 

SMSC LAN91C111 Driver (v2.1), (Linux Kernel 2.6) 

eth0: SMC91C11xFD(rev:1) at 0x80910300 IRQ:6 MEMSIZE:8192b NOWAIT:0 ADDR: 00:07: 

ed:00:00:00 

smc_probe: 50000 Khz Nios 

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 

ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx 

CF: ctl=1 

hda: CF 16MB, CFA DISK drive 

hdb: no response (status = 0xff), resetting drive 

hdb: no response (status = 0xff) 

Using anticipatory io scheduler 

ide0 at 0x80900800-0x80900807,0x80900838 on irq 8 

hda: max request size: 128KiB 

hda: 31232 sectors (15 MB) w/1KiB Cache, CHS=61/16/32 

hda: hda1 

microtronix[mtd]: RAM probe address=0x200000 size=0x538000 

Creating 1 MTD partitions on "RAM": 

0x00000000-0x00538000 : "ROMfs" 

microtronix[mtd]: set ROMfs to be root filesystem 

NET: Registered protocol family 2 

IP: routing cache hash table of 512 buckets, 4Kbytes 

TCP: Hash tables configured (established 1024 bind 2048) 

NET: Registered protocol family 1 

NET: Registered protocol family 17 

hda: hda1 

hda: hda1 

hda: hda1 

Kernel panic: VFS: Unable to mount root fs on hda1[/b] 

--- Quote End ---  

 

 

the cf is formatted with ext2fs.hda1 has bootable primary partition,as the quick guide suggest. 

what is the way? http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/dry.gif
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

another problem now http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/sad.gif  

 

<div class='quotetop'>QUOTE </div> 

--- Quote Start ---  

uClinux/Nios II 

Altera Nios II support © 2004 Microtronix Datacom Ltd. 

On node 0 totalpages: 4096 

  DMA zone: 0 pages, LIFO batch:1 

  Normal zone: 4096 pages, LIFO batch:1 

  HighMem zone: 0 pages, LIFO batch:1 

Built 1 zonelists 

Kernel command line: root=/dev/hda1 

PID hash table entries: 16 (order 4: 128 bytes) 

Memory available: 14788k/4096k RAM, 0k/0k ROM (1134k kernel code, 259k data) 

Calibrating delay loop... 24.72 BogoMIPS 

Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) 

Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) 

Mount-cache hash table entries: 512 (order: 0, 4096 bytes) 

POSIX conformance testing by UNIFIX 

NET: Registered protocol family 16 

Serial: JTAG UART driver $Revision: 1.3 $ 

ttyJ0 at MMIO 0x80920820 (irq = 1) is a jtag_uart 

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize 

smc_probe: 50000 Khz Nios 

SMSC LAN91C111 Driver (v2.1), (Linux Kernel 2.6) 

eth0: SMC91C11xFD(rev:1) at 0x80910300 IRQ:6 MEMSIZE:8192b NOWAIT:0 ADDR: 00:07: 

ed:ff:8c:ab 

smc_probe: 50000 Khz Nios 

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 

ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx 

CF: ctl=1 

hda: CF 16MB, CFA DISK drive 

hdb: no response (status = 0xff), resetting drive 

hdb: no response (status = 0xff) 

Using anticipatory io scheduler 

ide0 at 0x80900800-0x80900807,0x80900838 on irq 8 

microtronix[mtd]: RAM probe address=0x200000 size=0x538000 

Creating 1 MTD partitions on "RAM": 

0x00000000-0x00538000 : "ROMfs" 

microtronix[mtd]: set ROMfs to be root filesystem 

NET: Registered protocol family 2 

IP: routing cache hash table of 512 buckets, 4Kbytes 

TCP: Hash tables configured (established 1024 bind 2048) 

NET: Registered protocol family 1 

NET: Registered protocol family 17 

VFS: Cannot open root device "hda1" or unknown-block(0,0) 

Please append a correct "root=" boot option 

Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)[/b] 

--- Quote End ---  

 

 

 

 

what is that? http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/dry.gif
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

we also have tryed with the correct device minor-major number(hda is 0301,as the file on /dev indicate) 

no boot,the bios cannot found the device(unknown block(3,1) ) 

 

http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/mad.gif
0 Kudos
Altera_Forum
Honored Contributor II
692 Views

hey,nobody can help me? http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/sad.gif

0 Kudos
Reply