Project

General

Profile

MityDSP L138F : The Linux kernel panics

Added by Okan Çalış over 1 year ago

Hi, I'm trying to install the Linux kernel provided in the Critical Link MDK; however, after downloading the code to MityDsp and calling the "bootm" command in U-Boot, I get an error message stating that the kernel has panicked.
I suspect the problem might stem from my "bootargs" environment variable, which I modified multiple times before, and I don't know how to restore the original bootargs, or what it should be in order to boot Linux successfully.
Or the problem could also be due to something entirely different.
What should I do?
Thanks in advance.


Replies (7)

Additional details - Added by Okan Çalış over 1 year ago

I managed to reset the "bootargs" variable by running "flashargs". My current "bootargs" is now "mem=96M console=ttyS1,115200n8 mtdparts=nand:128M(rootfs),-(userfs) root=/dev/mtdblock0 rw,noatime rootfstype=jffs2"

The following is the error I get when I try booting the OS from 0xC0700000.

U-Boot 2009.11-00006-g66bcd23-dirty (Dec 14 2011 - 11:33:14)

I2C: ready
DRAM: 128 MB
NAND: 512 MiB
MMC: davinci: 0
In: serial
Out: serial
Err: serial
Error - Checksum on MityDSP-L138 Config Block Checksum Invalid
You must set the config to FLASH to make permanent
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
EMIFA CLock : 100000000 Hz
DSP Clock : 300000000 Hz
ASYNC3 Clock : 150000000 Hz
Enet config : 2
MMC 0 Enable : 0
Resetting ethernet phy
Net: Ethernet PHY: GENERIC @ 0x03 [0x8]

U-Boot > tftp c0700000 mityomap/uImage
Using device
TFTP from server 192.168.1.10; our IP address is 192.168.1.11
Filename 'mityomap/uImage'.
Load address: 0xc0700000
Loading: ################################################################## ################################################################# ###########################################
done
Bytes transferred = 2530232 (269bb8 hex)
U-Boot > run flashargs
U-Boot > pri bootargs
bootargs=mem=96M console=ttyS1,115200n8 mtdparts=nand:128M(rootfs),-(userfs) root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
U-Boot > bootm c0700000
  1. Booting kernel from Legacy Image at c0700000 ...
    Image Name: Linux-3.2.0
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2530168 Bytes = 2.4 MB
    Load Address: c0008000
    Entry Point: c0008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
    OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.0 (root@mitydsp) (gcc version 4.5.4 20120305 (prerelease) (GCC) ) #1 PREEMPT Mon Jan 13 11:06:16 EST 2014
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: MityDSP-L138/MityARM-1808
Ignoring unrecognised tag 0x42000101
Memory policy: ECC disabled, Data cache writethrough
DaVinci da850/omap-l138/am18x variant 0x1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 24384
Kernel command line: mem=96M console=ttyS1,115200n8 mtdparts=nand:128M(rootfs),-(userfs) root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 96MB = 96MB total
Memory: 91368k/91368k available, 6936k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xc6800000 - 0xfea00000 ( 898 MB)
lowmem : 0xc0000000 - 0xc6000000 ( 96 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc052c598 (5266 kB)
.init : 0xc052d000 - 0xc0555000 ( 160 kB)
.data : 0xc0556000 - 0xc05b5a80 ( 383 kB)
.bss : 0xc05b5aa4 - 0xc05e2490 ( 179 kB)
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 148.88 BogoMIPS (lpj=744448)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
DaVinci: 144 gpio irqs
print_constraints: dummy:
NET: Registered protocol family 16
baseboard_pre_init: Entered
mityomapl138_setup_nand: using 8 bit data
baseboard_init [IndustrialIO]...
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
print_constraints: VDCDC1: 1150 <--> 1350 mV at 1200 mV
print_constraints: VDCDC2: 1800 mV
print_constraints: VDCDC3: 1200 mV
print_constraints: LDO1: 1800 mV
print_constraints: LDO2: 2500 <--> 3300 mV at 3300 mV
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource timer0_1
musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
Waiting for USB PHY clock good...
musb-hdrc musb-hdrc: USB OTG mode controller at fee00000 using PIO, IRQ 58
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 178
io scheduler noop registered (default)
start plist test
end plist test
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a 16550A
serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a 16550A
console [ttyS1] enabled
serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a 16550A
brd: module loaded
at24 1-0050: 256 byte 24c02 EEPROM, read-only, 0 bytes/write
MityOMAPL138: Found MAC = 70:b3:d5:b5:1d:93
MityOMAPL138: Part Number = L138-FI-236-RL
ahci ahci: forcing PORTS_IMPL to 0x1
ahci ahci: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x01e18000-0x01e19fff] port 0x100 irq 67
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABADAWP)
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
Creating 2 MTD partitions on "davinci_nand.1":
0x000000000000-0x000008000000 : "rootfs"
0x000008000000-0x000020000000 : "homefs"
davinci_nand davinci_nand.1: controller rev. 2.5
spi_davinci spi_davinci.1: DMA: supported
spi_davinci spi_davinci.1: DMA: RX channel: 18, TX channel: 19, event queue: 0
m25p80 spi1.0: m25p64-nonjedec (8192 Kbytes)
Creating 8 MTD partitions on "m25p80":
0x000000000000-0x000000010000 : "ubl"
0x000000010000-0x000000090000 : "u-boot"
0x000000090000-0x0000000a0000 : "u-boot-env"
0x0000000a0000-0x0000000b0000 : "periph-config"
Using LCD panel: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
baseboard_setup_lcd: unknown LCD type : ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
MII PHY configured
0x0000000b0000-0x000000100000 : "reserved"
0x000000100000-0x000000400000 : "kernel"
0x000000400000-0x000000600000 : "fpga"
0x000000600000-0x000000800000 : "spare"
spi_davinci spi_davinci.1: Controller at 0xfef0e000
CAN device driver interface
mcp251x spi1.1: probed
davinci_mdio davinci_mdio.0: davinci mdio revision 1.5
davinci_mdio davinci_mdio.0: detected phy mask fffffff7
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy3: device 0:03, driver unknown
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 1
Waiting for USB PHY clock good...
ohci ohci.0: irq 59, io mem 0x01e25000
ata1: SATA link down (SStatus 0 SControl 300)
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: RTC power up reset detected
omap_rtc: already running
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
dsd1791 spi1.2: Failed to add route LLOUT->Line Out
asoc: dsd1791 <-> davinci-mcasp.0 mapping ok
ALSA device list:
#0: MityDSP-L138 INDIO
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
regulator_init_complete: LDO2: incomplete constraints, leaving on
regulator_init_complete: LDO1: incomplete constraints, leaving on
regulator_init_complete: VDCDC3: incomplete constraints, leaving on
regulator_init_complete: VDCDC2: incomplete constraints, leaving on
regulator_init_complete: VDCDC1: incomplete constraints, leaving on
console [netcon0] enabled
netconsole: network logging started
omap_rtc omap_rtc: setting system clock to 2000-01-01 01:30:56 UTC (946690256)
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002140c: 0xf0de instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021410: 0x46c3 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021414: 0x9ccd instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021418: 0xf2fd instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002141c: 0x4952 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021420: 0x9fcc instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021424: 0xf66c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021428: 0x4d31 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002142c: 0xa41c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00021430: 0xfb2d instead
Further such events for this erase block will not be printed
Empty flash at 0x00030ee4 ends at 0x00030ee8
Empty flash at 0x00038ad0 ends at 0x00038ad4
Empty flash at 0x0003c510 ends at 0x0003c514
Empty flash at 0x0003c520 ends at 0x0003c524
Empty flash at 0x0003c550 ends at 0x0003c554
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040000: 0x1000 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040004: 0x0120 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040008: 0x1020 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0004000c: 0x4001 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040010: 0x0010 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040014: 0x404e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040018: 0x0020 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040020: 0x2000 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00040024: 0x1000 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0004002c: 0x0014 instead
Further such events for this erase block will not be printed
Old JFFS2 bitmask found at 0x00057e30
You cannot use older JFFS2 filesystems with newer kernels
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00060000: 0x1000 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00060004: 0x0108 instead
...
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 352, bad_blocks 0, c->nr_blocks 1024
VFS: Cannot open root device "mtdblock0" or unknown-block(31,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 131072 mtdblock0 (driver?)
1f01 393216 mtdblock1 (driver?)
1f02 64 mtdblock2 (driver?)
1f03 512 mtdblock3 (driver?)
1f04 64 mtdblock4 (driver?)
1f05 64 mtdblock5 (driver?)
1f06 320 mtdblock6 (driver?)
1f07 3072 mtdblock7 (driver?)
1f08 2048 mtdblock8 (driver?)
1f09 2048 mtdblock9 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,0)
[<c000d518>] (unwind_backtrace+0x0/0xe0) from [<c0323c4c>] (panic+0x58/0x188)
[<c0323c4c>] (panic+0x58/0x188) from [<c052dbf4>] (mount_block_root+0x1bc/0x1fc)
[<c052dbf4>] (mount_block_root+0x1bc/0x1fc) from [<c052ddcc>] (mount_root+0xa0/0xc0)
[<c052ddcc>] (mount_root+0xa0/0xc0) from [<c052df48>] (prepare_namespace+0x15c/0x1bc)
[<c052df48>] (prepare_namespace+0x15c/0x1bc) from [<c052d858>] (kernel_init+0xe8/0x11c)
[<c052d858>] (kernel_init+0xe8/0x11c) from [<c0009cb8>] (kernel_thread_exit+0x0/0x8)

(The output is so long it overflows the serial terminal, hence I couldn't copy all of it.)

Here are my environment variables, in case necessary.

bootdelay=3
baudrate=115200
bootfile="uImage"
flashuboot=tftp 0xc0700000 mityomap/u-boot-ubl.bin; sf probe 0; sf erase 0x10000 0x80000; sf write 0xc0700000 0x10000 ${filesize}
flashkernel=tftp 0xc0700000 mityomap/uImage; sf probe 0; sf erase 0x100000 0x280000; sf write 0xc0700000 0x100000 ${filesize}
flashubl=tftp 0xc0700000 mityomap/UBL_SPI_MEM.ais; sf probe 0; sf erase 0 0x10000; sf write 0xc0700000 0 0x10000
flashrootfs=tftp 0xc2000000 mityomap/mityomap-base-mityomapl138.jffs2; nand erase 0 0x08000000; nand write.jffs2 0xc2000000 0 ${filesize}
autoload=no
mtdids=nand0=nand
mtdparts=mtdparts=nand:128M(rootfs),-(userfs)
bootargsbase=mem=96M console=ttyS1,115200n8
flashargs=setenv bootargs ${bootargsbase} ${mtdparts} root=/dev/mtdblock0 rw,noatime rootfstype=jffs2
progfpga=nand device nand0; nand read c4000000 00c00000 00200000; nand read c4000000 00c00000 00200000;
updatefpga=tftp c0700000 mityomap/upp.bin; nand device nand0; nand erase c00000 200000; nand erase c00000 200000; nand write c0700000 c00000 200000
updatedsp=tftp c0700000 mityomap/binary.bin; nand device nand0; nand erase 200000 a00000; nand erase 200000 a00000; nand write c0700000 200000 a00000
updatedspbootloader=tftp c0700000 mityomap/dspBoot.out; nand erase 100000 100000; nand write c0700000 100000 100000;
defaultbootcmd=sf probe 0; sf read 0xc0700000 0x100000 0x280000; bootm 0xc0700000
mirketboot=run progfpga; nand read c0700000 00100000 00100000; nand read c7000000 00200000 00800000; nand read ca000000 20000 10000; nand read c2500000 30000 10000; loadfpga c4000000 200000; bootdsp 0xc0700000;
bootargsbackup=mem=64M console=ttyS2,115200n8 ip=10.2.10.184 nfsroot=10.2.10.183: xport/rfs root=/dev/nfs rw
filesize=800000
fileaddr=C0700000
ipaddr=192.168.1.11
serverip=192.168.1.10
bootargs=mem=96M console=ttyS1,115200n8 root=/dev/mtdblock0 rw rootwait
stdin=serial
stdout=serial
stderr=serial
ethaddr=70:b3:d5:b5:1d:93
ver=U-Boot 2009.11-00006-g66bcd23-dirty (Dec 14 2011 - 11:33:14)

Environment size: 1981/65532 bytes

RE: MityDSP L138F : The Linux kernel panics - Added by Bob Duke over 1 year ago

Hi Okan,

Your bootargs tell the kernel to look at the on-board NAND flash for your filesystem. Is this your intent?

The kernel is crashing when it cannot mount the root filesystem on the NAND. Did you flash the filesystem onto the NAND using the process described in our documentation?

https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Linux_Root_File_System

RE: MityDSP L138F : The Linux kernel panics - Added by Okan Çalış over 1 year ago

Hi Bob,
Thanks for your help. I was following the instructions in https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Linux_Kernel and I thought the "Root File System" article was the next step; that's why I tried booting Linux without preparing a file system first.

I mounted the file system on the NAND flash, and I think I'm able to boot to Linux successfully this time. However, I've got a few questions:
  • The boot process hangs when I don't connect the Ethernet cable. How can I resolve this?
  • In the Linux terminal, if I type shutdown now, I get a message saying: USB 1.1 clocked from USB 2.0 PHY -- can't power it down. System halted. Is that a problem? Or does the OS halt gracefully?
  • I noticed a line that reads Failed to mount /sys/kernel/security: No such file or directory as well as other warning messages. Are those expected?

I've attached the terminal output I get, along with my current environment variables. Please take a look.
Thanks again.

Errors_out.txt View - Terminal output (17.1 KB)

RE: MityDSP L138F : The Linux kernel panics - Added by Jonathan Cormier over 1 year ago

Okan Çalış wrote:

Hi Bob,
Thanks for your help. I was following the instructions in https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Linux_Kernel and I thought the "Root File System" article was the next step; that's why I tried booting Linux without preparing a file system first.

I mounted the file system on the NAND flash, and I think I'm able to boot to Linux successfully this time. However, I've got a few questions:
  • The boot process hangs when I don't connect the Ethernet cable. How can I resolve this?

Where does it hang? You can prevent the kernel from waiting for a dhcp address by setting ip=none in the bootargs, though I noticed you set it to a static ip address this should prevent it from hanging as well. If its hanging after the filesystem takes over (see "Freeing init memory: 160K") then a log would be helpful.

  • In the Linux terminal, if I type shutdown now, I get a message saying: USB 1.1 clocked from USB 2.0 PHY -- can't power it down. System halted. Is that a problem? Or does the OS halt gracefully?

This is fine. Its likely just an extra verbose debug message. The "System halted" message is the last thing the kernel prints before it stops running.

  • I noticed a line that reads Failed to mount /sys/kernel/security: No such file or directory as well as other warning messages. Are those expected?

This is normal. Some part of systemd wants the /sys/kernel/security feature but we've never needed it so it wasn't enabled.

I've attached the terminal output I get, along with my current environment variables. Please take a look.
Thanks again.

Looks like a good boot.

RE: MityDSP L138F : The Linux kernel panics - Added by Okan Çalış over 1 year ago

Hi, Bob,

Where does it hang? You can prevent the kernel from waiting for a dhcp address by setting ip=none in the bootargs, though I noticed you set it to a static ip address this should prevent it from hanging as well. If its hanging after the filesystem takes over (see "Freeing init memory: 160K") then a log would be helpful.

I just realized that it doesn't hang but waits roughly a minute at the line net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, id=40005201)
Should I change the IP to "none"?

About the static IP, despite I set it as 192.168.1.11 at bootargs, when I type ifconfig -a in the terminal, this is what I get:

can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 70:B3:D5:B5:1D:93
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:33

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

The IP address of "local loopback" is 127.0.0.1 and "eth0" is missing an IP.
In order to download an executable to the board, I've connected the board to my host PC over Ethernet and tried pscp from my Windows command line with both 127.0.0.1 and 192.168.1.11, but neither seems to work (Fatal: Network Error: Connection Refused). What could be wrong? (I can post the SCP problem on a new thread, if needed.)

RE: MityDSP L138F : The Linux kernel panics - Added by Jonathan Cormier over 1 year ago

Okan Çalış wrote:

Hi, Bob,

Where does it hang? You can prevent the kernel from waiting for a dhcp address by setting ip=none in the bootargs, though I noticed you set it to a static ip address this should prevent it from hanging as well. If its hanging after the filesystem takes over (see "Freeing init memory: 160K") then a log would be helpful.

I just realized that it doesn't hang but waits roughly a minute at the line net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, id=40005201)
Should I change the IP to "none"?

ip=none should work. You don't have to configure the ip address at the kernel if you aren't booting from nfs. Note that i think your ip= syntax is wrong and it might be hanging while it tries to determine the missing parts. See https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Setting_a_Static_IP_Address#NFS-Mounted-File-System

Specifically the syntax: ip={ ipaddr }:{ serverip }:{ gatewayip }:{ netmask }:{ hostname }::off, where you set ipaddr, serverip, gatewayip, netmask, and hostname to desired values.

About the static IP, despite I set it as 192.168.1.11 at bootargs, when I type ifconfig -a in the terminal, this is what I get:

can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 70:B3:D5:B5:1D:93
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:33

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

The IP address of "local loopback" is 127.0.0.1 and "eth0" is missing an IP.
In order to download an executable to the board, I've connected the board to my host PC over Ethernet and tried pscp from my Windows command line with both 127.0.0.1 and 192.168.1.11, but neither seems to work (Fatal: Network Error: Connection Refused). What could be wrong? (I can post the SCP problem on a new thread, if needed.)

The local loopback is a standard network interface on any computer. It is only accessible from the machine itself and simply points back to itself. So by scp-ing to 127.0.0.1 you actually tried to connect to your own host PC.

Again see this link for how to set a static ip address inside linux. The static ip address you setup in the kernel will get overridden by the settings in linux. https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/Setting_a_Static_IP_Address

RE: MityDSP L138F : The Linux kernel panics - Added by Okan Çalış over 1 year ago

Okay, I'll look into that asap.
Thank you so much. You've been very helpful.

    (1-7/7)
    Add picture from clipboard (Maximum size: 500 MB)