Nabble - linuxppc-embedded

Query: Does Linux kernel 2.6.31 support read/write/erase on ST make M29W128GH Flash memory chip?

2009-10-22T04:18:33Z

Hi All,

I am searching for M29W128GH support in Linux kernel 2.6.31.

On internet I am seeing that there is some patch work for fixup on write buffer coomand on M29W128GH. This shows that Linux kernel 2.6.31 supports the M29W128GH.

But I am not seeing any memory mapping for M29W128GH.

Can anyone please tell me that whether Linux kernel 2.6.31 support the read/write/erase on M29W128GH? If yes how I can check that?

Which of below files I should use for communicating with ST M29W128GH flash chip?

cfi_cmdset_0001.c

cfi_cmdset_0002.c

cfi_cmdset_0020.c -- Looks like I shall use this but not confirm.

cfi_probe.c

I am novice to flash driver in kernel so might be not getting the exact details on M29W128GH.

Expecting a help from seniors in this field.

Thanks in advance.

Thanks & Regards,

Aakash

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@...
https://lists.ozlabs.org/listinfo/linuxppc-dev

Execute In Place (XIP) support for PPC440x5

2009-10-22T03:10:59Z

Hi List,

I am trying to port a board with PPC440x5 on linux-2.6.31. My board
has 64MB of flash and 256KB of RAM. Since with this much RAM it is not
possible to copy the kernel image to RAM and boot it from there. I was
trying to figure-out option in the kernel which will allow me to
execute it from flash itself.

I refered to http://www.denx.de/wiki/publish/DULG/to-delete/ConfigureLinuxForXIP.html;
but the flags mentioned here are not present for PPC architecture. I
found these flag only for ARM architecture.

So can anyone please tell me whether it is possible to have kernel
executing from flash for PPC?
If yes, then please let me know about any patch or something that will
allow me to do this?

--
Thanks and Regards,
Mohit Mewada
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@...
https://lists.ozlabs.org/listinfo/linuxppc-dev

PPC440epx boot problem

2009-10-18T11:40:20Z

Hello, all,

I have got an EP440XS board. I have port the BSP based on Sequoia board. The uImage does not boot. cuImage boots, but it is stuck in the wrapper with the message "Finalizing device tree... flat tree at 0x784300" before the kernel image starts. How do I know that the address 0x784300 is correct? I am new to LINUX, where do I start to debug this?
Thanks.

Allan

=> bootm
## Booting image at 00200000 ...
Image Name: Linux-2.6.30.4
Created: 2009-10-18 14:53:32 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1593840 Bytes = 1.5 MB
Load Address: 00400000
Entry Point: 00400460
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
CPU clock-frequency <- 0x1fca0550 (533MHz)
CPU timebase-frequency <- 0x1fca0550 (533MHz)
/plb: clock-frequency <- 7f28154 (133MHz)
/plb/opb: clock-frequency <- 3f940aa (67MHz)
/plb/opb/ebc: clock-frequency <- 3f940aa (67MHz)
/plb/opb/serial@ef600300: clock-frequency <- a8c000 (11MHz)
/plb/opb/serial@ef600400: clock-frequency <- a8c000 (11MHz)
/plb/opb/serial@ef600500: clock-frequency <- a8c000 (11MHz)
/plb/opb/serial@ef600600: clock-frequency <- a8c000 (11MHz)
Memory <- <0x0 0x0 0xffff000> (255MB)
ethernet0: local-mac-address <- 00:10:ec:01:12:83
ethernet1: local-mac-address <- 00:10:ec:81:12:83

zImage starting: loaded at 0x00400000 (sp: 0x07f2bb90)
Allocating 0x3440ec bytes for kernel ...
gunzipping (0x00000000 <- 0x0040e000:0x00777660)...done 0x32623c bytes

Linux/PowerPC load: $(bootargs) console=ttyS0,$(baudrate)
Finalizing device tree... flat tree at 0x784300

kernel oops issue in localbus driver

2009-10-15T06:36:44Z

Hi,

I have a FPGA connected to a MPC8347 through localbus.

The following kernel oops occurs sometimes:

Unable to handle kernel paging request for data at address 0x7ddfecb0
Faulting instruction address: 0xc00145f4
Oops: Kernel access of bad area, sig: 11 [#1]
PREEMPT
Modules linked in: ath_pci ath_rate_minstrel ath_hal wlan_acl
wlan_ccmp wlan_scan_ap wlan_scan_sta wlan_tkip wlan_wep wlan_xauth
wlan gpio localbus
NIP: C00145F4 LR: D1083C74 CTR: 000001C3
REGS: c700ddb0 TRAP: 0300 Tainted: P (2.6.18)
MSR: 00009032 <EE,ME,IR,DR> CR: 20024042 XER: 20000000
DAR: 7DDFECB0, DSISR: 22000000
TASK = c7786810[345] 'femain' THREAD: c700c000
GPR00: 00000000 C700DE60 C7786810 7DDFEBC8 C90620EC 00000F00 7DDFECAC
7196E7E0
GPR08: 0EECA261 D1090000 0021ED00 C00145D0 00001000 704C6206 00000000
1005924D
GPR16: C0034D7C 7DDFEBC8 C700DE9C 00000F00 00000000 C787A3C0 D1090000
00000000
GPR24: 00000000 D1090000 7DDFEBC8 D1090000 000003C0 C9062000 7DDFEBC8
D108E954
NIP [C00145F4] memcpy+0x24/0x9c
LR [D1083C74] lbp_memcpy32_fromio+0x54/0x98 [localbus]
Call Trace:
[C700DE60] [C019B780] preempt_schedule_irq+0x64/0xa4 (unreliable)
[C700DE80] [D10813C0] fpgadecenc_read+0x3ac/0x4b0 [localbus]
--- Exception: 7ddfebc8 at 0xc700df40
LR = _start+0x40000000/0xc
[C700DEF0] [C005F4DC] vfs_read+0x9c/0x140 (unreliable)
[C700DF10] [C005F840] sys_read+0x4c/0x90
[C700DF40] [C000F89C] ret_from_syscall+0x0/0x38
--- Exception: c01 at 0x300bb7dc
LR = 0x3001ed40
Instruction dump:
4e800020 7c032040 418100a0 54a7e8ff 38c3fffc 3884fffc 41820028
70c00003
7ce903a6 40820054 80e40004 85040008 <90e60004> 95060008 4200fff0 70a50007

It seems there's an issue in the localbus driver (lbp_memcpy32_fromio
is a wrapper function for the localbus memory access):

ssize_t lbp_memcpy_fromio(void *dest, void *source, __u32 count32)
{
/* attempt to acquire the semaphore */
down(&sem_lb);
/* critical region */
mb();
memcpy_fromio(dest, source, count32 * 4);
mb();
/* release the given semaphore */
up(&sem_lb);
}

Aren't we supposed to use down_interruptible() instead ?
I didn't write the driver and would like to fix it.
Any hints will be appreciated.

cheers,

Fathi
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@...
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: Inherit U-boot's pcie config

2009-10-07T14:47:10Z

I have tried pci=firmware as well, but kernel says " PCI: Unknown option `firmware' ". I have also tried setting the PPC_PCI_PROBE_ONLY flag on ppc_pci_flags with no luck.

dbrazeau wrote:

I have U-boot setting up my pcie config the way i like. I was wondering if there was some way to make linux inherit the bootloader/bios pcie config. Currently when Linux boots it wipes out all the configuration that is done in U-boot. I have tried using the kernel command pci=bios, but that doesn't seem work. Is there any other kernel command line argument or kernel configuration that I can use to do this?

Inherit U-boot's pcie config

2009-10-07T13:34:00Z

I have U-boot setting up my pcie config the way i like. I was wondering if there was some way to make linux inherit the bootloader/bios pcie config. Currently when Linux boots it wipes out all the configuration that is done in U-boot. I have tried using the kernel command pci=bios, but that doesn't seem work. Is there any other kernel command line argument or kernel configuration that I can use to do this?

Re: Problem with linux kernal Booting on ppc440x5 processor & SRAM Memory

2009-09-29T02:38:17Z

we have 16MB of SRAM from location 0x0 till 0x0FFFFFF. In this we r using the last 1 MB for the Simple bootloader to execute. We created a TLB for the entire 16Mb RAM while initializing the processor (from our simple bootloader.)i hope this is enough memory to boot linux.

We tried changing the configuration of the crosstool and found its crashing at the same level again..please find the log below. We are diggin more now on the reason for DEAR and MSR having the same value.

Bootloader : Initialized the System
Bootloader : Initialized the UART
Bootloader : Copying Linux Image to RAM
Bootloader : !!!!!!!!!!!!!!!!!!!!!!!!!!!
Bootloader : Copying Image from FLASH to 0x400000 of SRAM is Done
Bootloader : -KENTRY -

zImage starting: loaded at 0x00400000 (sp: 0x004deeb0)
Allocating 0x1dad84 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040c000:0x004dd407)...done 0x1c31cc bytes

Linux/PowerPC load: console=ttyS0 root=/dev/ram
Finalizing device tree... flat tree at 0x4eb300
inside _setup_arch-begininginside _setup_arch-1inside skybeam_register_console function
oodikkooo...inside _setup_arch-2<7>Top of RAM: 0x1a00000, Total RAM: 0x1a00000
Zone PFN ranges:
DMA 0x00000000 -> 0x00001a00
Normal 0x00001a00 -> 0x00001a00
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00001a00
MMU: Allocated 1088 bytes of context maps for 255 contexts
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 6604
Kernel command line: console=ttyS0 root=/dev/ram
Unable to handle kernel paging request for data at address 0x00021000
Faulting instruction address: 0xc010a7a4
Oops: Kernel access of bad area, sig: 11 [#1]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: c010a7a4 LR: c010dc30 CTR: 00000000
REGS: c01bfeb0 TRAP: 0300 Not tainted (2.6.30)
MSR: 00021000 <ME,CE> CR: 24000044 XER: 00000000
DEAR: 00021000, ESR: 00000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00001180 c01bff60 c01a94b8 00021000 00000025 00000008 c0104948 00000000
GPR08: 2f72616d c0110000 c0155920 c01a0000 22000024 00000000 fffff104 00000000
GPR16: 00000000 00000000 00000000 00000000 fffffff8 000008b8 c010d738 c0104948
GPR24: 00001198 00001190 c018a001 c01c5498 000008c0 00001188 00021000 c01c42f0
NIP [c010a7a4] strchr+0x0/0x3c
LR [c010dc30] match_token+0x138/0x228
Call Trace:
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Oops: Kernel access of bad area, sig: 11 [#2]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: 00000008 LR: 00000009 CTR: c010ca04
REGS: c01bfa50 TRAP: 0400 Not tainted (2.6.30)
MSR: 00021000 <ME,CE> CR: 24004042 XER: 00000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00000009 c01bfb00 c01a94b8 00000000 c01bfaf8 00000010 c01bfaf8 c01bfb7c
GPR08: ffffffff c01c628c ffffffff c01bfb00 24004048 00000000 c0152754 c0152838
GPR16: c0152604 c01528c4 c01bfc70 ffffffff c01b8628 c005bd94 00000004 c01c628c
GPR24: c01bfdb8 00000000 c016b96c c01bfb7c c01bfb10 c005be3c 00000010 c01c628c
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Recursive die() failure, output suppressed
---[ end trace 31fd0ba7d8756001 ]---
Kernel panic - not syncing: Attempted to kill the idle task!
Call Trace:
[c01bf510] [c0005d5c] show_stack+0x4c/0x16c (unreliable)
[c01bf550] [c002f15c] panic+0xa0/0x168
[c01bf5a0] [c0032e98] do_exit+0x61c/0x638
[c01bf5e0] [c000b60c] kernel_bad_stack+0x0/0x4c
[c01bf610] [c000f310] bad_page_fault+0x90/0xd8
[c01bf620] [c000e184] handle_page_fault+0x7c/0x80
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Oops: Kernel access of bad area, sig: 11 [#3]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: 00000008 LR: 00000009 CTR: c010ca04
REGS: c01bf170 TRAP: 0400 Tainted: G D (2.6.30)
MSR: 00021000 <ME,CE> CR: 24004042 XER: 20000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00000009 c01bf220 c01a94b8 00000000 c01bf218 00000010 c01bf218 c01bf29c
GPR08: ffffffff c01c628c ffffffff c01bf220 24004048 00000000 c0152754 c0152838
GPR16: c0152604 c01528c4 c01bf390 ffffffff c01b8628 c005bd94 0000007c c01c628c
GPR24: c01bf4d8 00000000 00000009 c01bf29c c01bf230 c005be3c 00000010 c01c628c
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Oops: Kernel access of bad area, sig: 11 [#4]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: 00000008 LR: 00000009 CTR: c010ca04
REGS: c01bed50 TRAP: 0400 Tainted: G D (2.6.30)
MSR: 00021000 <ME,CE> CR: 24004042 XER: 20000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00000009 c01bee00 c01a94b8 00000000 c01bedf8 00000010 c01bedf8 c01bee7c
GPR08: ffffffff c01c628c ffffffff c01bee00 24004048 00000000 c0152754 c0152838
GPR16: c0152604 c01528c4 c01bef70 ffffffff c01b8628 c005bd94 00000000 c01c628c
GPR24: c01bf0b8 00000000 00000008 c01bee7c c01bee10 c005be3c 00000010 c01c628c
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Recursive die() failure, output suppressed
---[ end trace 31fd0ba7d8756002 ]---
Kernel panic - not syncing: Attempted to kill the idle task!
Call Trace:
[c01be810] [c0005d5c] show_stack+0x4c/0x16c (unreliable)
[c01be850] [c002f15c] panic+0xa0/0x168
[c01be8a0] [c0032e98] do_exit+0x61c/0x638
[c01be8e0] [c000b60c] kernel_bad_stack+0x0/0x4c
[c01be910] [c000f310] bad_page_fault+0x90/0xd8
[c01be920] [c000e184] handle_page_fault+0x7c/0x80
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Oops: Kernel access of bad area, sig: 11 [#5]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: 00000008 LR: 00000009 CTR: c010ca04
REGS: c01be470 TRAP: 0400 Tainted: G D (2.6.30)
MSR: 00021000 <ME,CE> CR: 24004042 XER: 20000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00000009 c01be520 c01a94b8 00000000 c01be518 00000010 c01be518 c01be59c
GPR08: ffffffff c01c628c ffffffff c01be520 24004048 00000000 c0152754 c0152838
GPR16: c0152604 c01528c4 c01be690 ffffffff c01b8628 c005bd94 0000007c c01c628c
GPR24: c01be7d8 00000000 00000009 c01be59c c01be530 c005be3c 00000010 c01c628c
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Oops: Kernel access of bad area, sig: 11 [#6]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: 00000008 LR: 00000009 CTR: c010ca04
REGS: c01be050 TRAP: 0400 Tainted: G D (2.6.30)
MSR: 00021000 <ME,CE> CR: 24004042 XER: 20000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00000009 c01be100 c01a94b8 00000000 c01be0f8 00000010 c01be0f8 c01be17c
GPR08: ffffffff c01c628c ffffffff c01be100 24004048 00000000 c0152754 c0152838
GPR16: c0152604 c01528c4 c01be270 ffffffff c01b8628 c005bd94 00000000 c01c628c
GPR24: c01be3b8 00000000 00000008 c01be17c c01be110 c005be3c 00000010 c01c628c
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000008
Recursive die() failure, output suppressed
Kernel panic - not syncing: Fatal exception in interrupt
Call Trace:
Rebooting in 180 seconds..
/**************NEW LOG ****************************************/
Thanks & Regards
Vineeth V

nilwil wrote:

The crosstool config says LINUX_DIR=linux-2.6.15.4, while the kernel config says 2.6.30. Assuming you are using the right kernel image, the reason I could see is having insufficient RAM.

How much RAM do you have? A typical Linux image (uncompressed) will take at least 1-2MB space. If you can't provide enough RAM for this, you might want to configure XIP (execute in place), to run the kernel from flash. However, this might require writing a flash driver for your NAND/NOR chip.

Re: Problem with linux kernal Booting on ppc440x5 processor & SRAM Memory

2009-09-24T21:36:52Z

The crosstool config says LINUX_DIR=linux-2.6.15.4, while the kernel config says 2.6.30. Assuming you are using the right kernel image, the reason I could see is having insufficient RAM.

How much RAM do you have? A typical Linux image (uncompressed) will take at least 1-2MB space. If you can't provide enough RAM for this, you might want to configure XIP (execute in place), to run the kernel from flash. However, this might require writing a flash driver for your NAND/NOR chip.

Re: Problem with linux kernal Booting on ppc440x5 processor & SRAM Memory

2009-09-24T04:56:00Z

Hi,

Please find the crosstool.config.txt file info below. And the kernel configuration file (".config") is attached.

AR=
BINUTILS_DIR=binutils-2.16.1
BINUTILS_EXTRA_CONFIG=
BUILD=x86_64-unknown-linux-gnu
BUILD_DIR=/home/sumesh/crosstool-0.43/build/powerpc-440-linux-gnu/gcc-4.2.4-glibc-2.3.6
CC=
DEJAGNU=
EXTRA_TARGET_CFLAGS=
GCC_BUILD=
GCC_CORE_DIR=gcc-3.4.6
GCC_DIR=gcc-4.2.4
GCC_EXTRA_CONFIG=--with-cpu=440 --enable-cxx-flags=-mcpu=440
GCC_HOST=
GCC_LANGUAGES=c,c++
GDB_DIR=gdb-6.5
GLIBC_ADDON_OPTIONS==linuxthreads,
GLIBC_DIR=glibc-2.3.6
GLIBC_EXTRA_CC_ARGS=
GLIBC_EXTRA_CONFIG=--without-fp
GLIBC_EXTRA_ENV=
JUST_DOWNLOAD=
KERNELCONFIG=
LINUX_DIR=linux-2.6.15.4
LINUX_SANITIZED_HEADER_DIR=linux-libc-headers-2.6.12.0
NO_DOWNLOAD=
PREFIX=/opt/crosstool/gcc-4.2.4-glibc-2.3.6/powerpc-440-linux-gnu
PTXDIST_DIR=
SHARED_MODE=--enable-shared
SRC_DIR=/home/sumesh/crosstool-0.43/build/powerpc-440-linux-gnu/gcc-4.2.4-glibc-2.3.6
TARBALLS_DIR=/home/sky/downloads
TARGET=powerpc-440-linux-gnu
TARGET_CFLAGS=-O -mcpu=440
TOP_DIR=/home/sumesh/crosstool-0.43
USE_SYSROOT=

Please tell me if i am missing smthing in this.

Thanks,
Vineeth.config

nilwil wrote:

This could be a problem with the tool chain/kernel configuration you are using. What versions and configurations are you using for the tools and kernel?

Re: Problem with linux kernal Booting on ppc440x5 processor & SRAM Memory

2009-09-24T04:42:25Z

This could be a problem with the tool chain/kernel configuration you are using. What versions and configurations are you using for the tools and kernel?

Problem with linux kernal Booting on ppc440x5 processor & SRAM Memory

2009-09-21T03:35:49Z

Hi,

I am trying to port linux on IBM powerpc-440x5. I have this board which has this processor, a 16MB SRAM sits on location 0x0, uart and a flash.I have a simple bootloader which does the following.
1. Initialize the processor (as part of it, we Generates the tlbs for UART,16MB flash,16MB SRAM)
2. Initialize the UART
3. Copy the simple-boot linux_image (binary file) from flash to 0x400000 location of SRAM.
4. Kernel entry to 0x400000
I also have a device tree structure file (image.dts) which i am passing while generating the linux image.
It all went through and linux got extracted to the 0x0th location of SRAM. and started executing.
(plz find the log below)

it always crashed @ "Unable to handle kernel paging request for data at address 0x0xxxxxxx"
is there anything i have to change in the boot loader or kernel with respect to the MMU initialization ?

in the kernel code @ /arch/powerpc/kernel/head_44x.s; there is a comment saying "its trying to invalidate all the TLB entries except the one it currently working on". Will it make any issues as in our case we have only one TLB for the entire 16MB sram, which will be the current working one..

Can someone suggest us some clue or details on this.

Thanks & Regards,
Vineeth

LINUX BOOT LOG
----------------------------------------------------------------------------------------
Initialized the System
Initialized the UART
Copying Linux Image to RAM > !!!!!!!!!!!!!!!!!!!!!!!!!!!
Copying Image Done
-KERNEL ENTRY-
-
zImage starting: loaded at 0x00400000 (sp: 0x004deeb0)
Allocating 0x1dad84 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040c000:0x004dd3f1)...done 0x1c31cc bytes

Linux/PowerPC load: console=ttyS0 root=/dev/ram
Finalizing device tree... flat tree at 0x4eb300
id mach(): done
inside skybeam_register_console function
MMU:enterMMU:hw initMMU:mapinMMU:setioMMU:exitinside _setup_arch-begininginside _setup_arch-1inside _setup_arch-2setup_arch: bootmemarch: exit<7>Top of RAM: 0x1000000, Total RAM: 0x1000000
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
Normal 0x00001000 -> 0x00001000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00001000
MMU: Allocated 1088 bytes of context maps for 255 contexts
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 4064
Kernel command line: console=ttyS0 root=/dev/ram
Unable to handle kernel paging request for data at address 0x00021000
Faulting instruction address: 0xc010a7c4
Oops: Kernel access of bad area, sig: 11 [#1]
PREEMPT PowerPC 44x Platform
Modules linked in:
NIP: c010a7c4 LR: c010dc50 CTR: 00000000
REGS: c01bfeb0 TRAP: 0300 Not tainted (2.6.30)
MSR: 00021000 <ME,CE> CR: 24000044 XER: 00000000
DEAR: 00021000, ESR: 00000000
TASK = c01a94b8[0] 'swapper' THREAD: c01be000
GPR00: 00001180 c01bff60 c01a94b8 00021000 00000025 00000008 c0104968 00000000
GPR08: 2f72616d c0110000 c0155938 c01a0000 22000024 00000000 fffff104 00000000
GPR16: 00000000 00000000 00000000 00000000 fffffff8 000008b8 c010d758 c0104968
GPR24: 00001198 00001190 c018a001 c01c5498 000008c0 00001188 00021000 c01c42f0
NIP [c010a7c4] strchr+0x0/0x3c
LR [c010dc50] match_token+0x138/0x228
Call Trace:
[c01bff60] [c016b99c] 0xc016b99c (unreliable)
[c01bffa0] [c0104a00] sort_extable+0x28/0x38
[c01bffb0] [c01938ec] sort_main_extable+0x20/0x30
[c01bffc0] [c018c734] start_kernel+0x140/0x288
[c01bfff0] [c0000200] skpinv+0x190/0x1cc
Instruction dump:
7ca903a6 88040000 38a5ffff 38840001 2f800000 98090000 39290001 419e0010
4200ffe4 98a90000 4e800020 4e800020 <88030000> 5484063e 7f802000 4d9e0020
---[ end trace 31fd0ba7d8756001 ]---
Kernel panic - not syncing: Attempted to kill the idle task!
Call Trace:
[c01bfd90] [c0005d5c] show_stack+0x4c/0x16c (unreliable)
[c01bfdd0] [c002f17c] panic+0xa0/0x168
[c01bfe20] [c0032eb8] do_exit+0x61c/0x638
[c01bfe60] [c000b60c] kernel_bad_stack+0x0/0x4c
[c01bfe90] [c000f310] bad_page_fault+0x90/0xd8
[c01bfea0] [c000e184] handle_page_fault+0x7c/0x80
[c01bff60] [c016b99c] 0xc016b99c
[c01bffa0] [c0104a00] sort_extable+0x28/0x38
[c01bffb0] [c01938ec] sort_main_extable+0x20/0x30
[c01bffc0] [c018c734] start_kernel+0x140/0x288
[c01bfff0] [c0000200] skpinv+0x190/0x1cc
Rebooting in 180 seconds..

problem opening SPI driver on PowerPC 8313

2009-09-10T15:04:29Z

Hi,

I can't load the spi module using a 2.6.27 kernel on a PowerPc 8313.
When I try "MAKEDEV spi", a few spi devices are created but when I try to open one of them it fails. I get : "can not open device: No such device or address";

I also tried to load spi dynamically.
I did something like this:
insmod spi_mpc83xx.ko
mknod /dev/spi c 153 0
chmod 666 /dev/spi

When I tried to open the SPI dev, I got the same error "can not open device: No such device or address";

Does anyone knows how I can at least debug this ? maybe a way to obtain a little more information on the errors ? the /var/log or dmesg did not help much.

PS> We can open i2c in the same way(ioctl) with no problem.

I appreciate your assistance.

Thanks.

Yan~

ltib, upgrade package

2009-08-31T05:35:33Z

hi,
i am working on a mpc8313e. bsp of it contains some older packages. i need gstreamer good plugin 0.10.16 but bsp offers 0.10.6. search everywhere but cannot find a working solution. tried to alter the spec file but it gives the rpm bad exit error. any help?

Re: mpc8313e nand flash

2009-08-26T07:48:29Z

i know this become weird but i find the configuration file. all my questions, all my answers, sorry for inconvenience

Re: mpc8313e nand flash

2009-08-26T07:06:48Z

copying the files from nand to memory and using bootm, i solved the problem.
now third question:)
the uImage file is about 12 mb when i include the gstreamer package and its dependent ones, when trying to boot ramdisk incomplete write(-28!=32768)33554432 error occurs. i searched it and it is related to ramdisk size. how can i change the ramdisk size? or is there another better solution(with explanations please)?
by the way i am using the bsp provided by freescale to create the ltib.

today i changed bootloader to boot from nand in ltib configuration, burn the u-boot-nand.bin file to 0x0 position of nand flash, changed the switches to boot from nand and achieved to see the u-boot prompt. at the moment i need environment variables to boot to linux kernel, could anyone using this board and booting from nand paste his/her printenv output?

burkay wrote:

hi all,

i try to use mpc8313e for media streaming purposes and when included gstreamer package, the rootfs.ext2.gz.uboot image becomes about 12M which cannot fit to 8M onchip nor flash. any answer to below two questiones appreciated:

1. to which memory locations i should burn the uImage, rootfs.ext2.gz.uboot and mpc8313erdb.dtb images on the nand flash that when configured the switches to boot from nand flash, it successfully boots to linux?

2. is there a way that burning the rootfs image to nand flash, other two images to nor flash, boot from nor (switches configured to boot from nor), and succesfully reach to linux terminal?

thanks in advance..

PPC driver - generic bus width

2009-08-26T06:25:47Z

Hi all,

Im trying to develop a driver for my device, and its data bus can be 8, 16
or 32 bits. This information is passed through the device tree source.
My code is like this:

struct device_info_t {
void (*read)();
void (*write)();
};

static int __devinit device_probe()
{
prop = of_get_property(ofdev->node, "bus-width", &size);

device->bus_width = *prop;

switch (device->bus_width) {
case 8:
device->read = in_8;
device->write = out_8;
break;
case 16:
device->read = in_be16;
device->write = out_be16;
break;
case 32:
device->read = in_be32;
device->write = out_be32;
break;
default:
break;
}
}

Can someone point me some driver that is doing something similar to the
ideia shown above?

Or what Im doing wrong in my code? Cause Im getting erros (warnings) like:

cc1: warnings being treated as errors
drivers/dev_test.c:37: warning: function declaration isn't a prototype
drivers/dev_test.c:38: warning: function declaration isn't a prototype
drivers/dev_test.c: In function 'device_probe':
drivers/dev_test.c:113: warning: assignment from incompatible pointer
type

PS: Im using a MPC8349, linux kernel 2.6.26

Cheers,

--
Alemao
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@...
https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: mpc8313e nand flash

2009-08-26T02:13:02Z

today i changed bootloader to boot from nand in ltib configuration, burn the u-boot-nand.bin file to 0x0 position of nand flash, changed the switches to boot from nand and achieved to see the u-boot prompt. at the moment i need environment variables to boot to linux kernel, could anyone using this board and booting from nand paste his/her printenv output?

burkay wrote:

hi all,

i try to use mpc8313e for media streaming purposes and when included gstreamer package, the rootfs.ext2.gz.uboot image becomes about 12M which cannot fit to 8M onchip nor flash. any answer to below two questiones appreciated:

1. to which memory locations i should burn the uImage, rootfs.ext2.gz.uboot and mpc8313erdb.dtb images on the nand flash that when configured the switches to boot from nand flash, it successfully boots to linux?

2. is there a way that burning the rootfs image to nand flash, other two images to nor flash, boot from nor (switches configured to boot from nor), and succesfully reach to linux terminal?

thanks in advance..

mpc8313e nand flash

2009-08-25T04:05:51Z

hi all,

i try to use mpc8313e for media streaming purposes and when included gstreamer package, the rootfs.ext2.gz.uboot image becomes about 12M which cannot fit to 8M onchip nor flash. any answer to below two questiones appreciated:

1. to which memory locations i should burn the uImage, rootfs.ext2.gz.uboot and mpc8313erdb.dtb images on the nand flash that when configured the switches to boot from nand flash, it successfully boots to linux?

2. is there a way that burning the rootfs image to nand flash, other two images to nor flash, boot from nor (switches configured to boot from nor), and succesfully reach to linux terminal?

thanks in advance..

NETDEV WATCHDOG eth2 transmit time out frequently occure for MPC8360

2009-08-06T22:03:46Z

WE are using the MPC8360 processor, we are using the FOUR Ethernet port of MPC8360. 2 GMII Ethernet and 2 RMII Ethernet port.

RMII Ethernet port is connected MAC layer with the device. We provide the clock to both port using the External Oscillator source 50 MHz.

Problem: Some time the Ethernet port 2 is get the "NETDEV WATCHDOG eth2 transmit time out" error, once this error occur, it continually occur. As per our observation, when the we are try to transmit more packet to Ethernet port for the long duration then then this type error occur. So how we can resolve it. please provide the solution for this problem.

wait for replay

Regards,
shailesh

PPC MPC8349 : Add DMA features for DiskOnChip tffs drivers.

2009-08-06T01:06:30Z

Hi all,

I have difficulties when try to add mDOC DMA support for our architecture (PPC MPC83XX).

The file is in 2.6.27 linux kernel source /drivers/tffs/tffsarch.h and tffsarch.c

Based on the example codes (for Intel PXA27x "Mainstone" board), we need to enable call to tffs_dmasw(), which then use __dmasw_bread() and __dmasw_bwrite() routine.

After we add the necessary macros, then we insmod the modules :

$insmod tffs.ko

everything run smoothly :

.....
tffs: mDOC driver 1100.85
tffs: will not use IRQ
tffs: mDOC found
tffs: Socket 0 in addr 0xf1000000
tffs: Device 0x0: 7782400 512-byte sectors, h/w sector 512 bytes
tffs: C/H/S 916 177 48
tffs: use major device number 100
tffsa: tffsa1 tffsa2
.....

, but when we've enabled the DMA :

$ insmod tffs.ko tffs_dma_mode=3

, an error occured. Here is the dump messages from dmesg command :

.....
tffs: mDOC driver 1100.85
tffs: will not use IRQ
tffs: mDOC not found
tffs: flInit() error 60
tffs: No DiskOnChips found
.....

are we missed any other thing beside the macro definition of tffs_dmasw()? we've done nothing but simple dump messages in the __dmasw_bread() and __dmasw_bwrite() just to inform us that it does accessed when the drivers need to use DMA.

Any help will be appreciated,
Thanks

help on support Compact flash(memory mapped mode) access in linux

2009-08-05T09:13:07Z

Hi,

This is regarding Sandisk Compact flash(Memory mapped mode) driver support in linux,which has to support file system.

I am using linux version 2.6.22.

I am describing hardware configuration below:

The CF is connected directly to MPC8250 CPU (PowerQUICC II,Freescale), via (60x bus).
It is connected in Memory mapped Mode, with 16-bit data lines interface.

CF is connected directly to CPU like SDRAM on 60x bus.
The memory controller of the MPC8250 is utilized for controlling accesses to Compact Flash without the aid of a PCMCIA or ATA controller device.

The queries are :
1. What is the appropriate driver? Is there any open source driver available in Linux to make use for this mode?
2. Is there any procedure on how to integrate compact flash in Linux?
3. I have working u-boot cf driver, which has read and write sector routines which does raw read/write from CF ?

I am able to boot (u-boot) system from CF.

Also Currently U-boot supports raw read/write sectors routines. So How to port CF driver from u-boot to Linux?

Thank you very much in Advance.

Regards,
Aravind

Kernel 2.6 fail in NFS with xps_ethernetlite

2009-07-13T20:10:57Z

My system on a ML 410 board (V4FX60) is very basic: 256M ddr with MPMC, xps_ethernetlite ... build with BSB in EDK 11.1. The cable into the Marvell ethernet Phy is from a 100M switch (so xps_ethernetliet should work).

My kernel (version 2..6.29 got from git tree at http://git.xilinx.com) boot up command is: "root=/dev/nfs nfsaddrs=10.0.10.1:10.0.1.16:10.0.0.1:255.255.0.0 rw nfsroot=/exports/rootfs console=ttyS0,38400" with which I have no problem in booting up a 2.4 Kernel using NFS (with plb_ethernet though, the 2.4 kernel I get, as in the BYU project, does not support xps_ethernetlite ip).

I get the message:
xilinx_emaclite 81000000.ethernet: Device Tree Probing 'ethernet'
xilinx_emaclite 81000000.ethernet: MAC address is now 2: 0: 0: 0: 0: 0
xilinx_emaclite 81000000.ethernet: using fifo mode.
eth0 (): not using net_device_ops yet
xilinx_emaclite 81000000.ethernet: Xilinx EMACLite at 0x81000000 mapped to 0xD1020000, irq=17
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
IP-Config: Complete:
device=eth0, addr=10.0.10.1, mask=255.255.0.0, gw=10.0.0.1,
host=10.0.10.1, domain=, nis-domain=(none),
bootserver=10.0.1.16, rootserver=10.0.1.16, rootpath=

Looking up port of RPC 100003/2 on 10.0.1.16
Looking up port of RPC 100005/1 on 10.0.1.16
rpcbind: server 10.0.1.16 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default

Root-NFS: Server returned error -5 while mounting /exports/rootfs
VFS: Unable to mount root fs via NFS, trying floppy.

VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option;

(With Kernel 2.4 and PLB_Ethernet, NFS can be mounted after "looking up port")

Then I tried downloading a image file which contains a RamDisk but has the same boot command. Again, NFS fail, but the kernel boots up on the root file system provided by the RamDisk, with the message:

IP-Config: Complete:
device=eth0, addr=10.0.10.1, mask=255.255.0.0, gw=10.0.0.1,
host=10.0.10.1, domain=, nis-domain=(none),
bootserver=10.0.1.16, rootserver=10.0.1.16, rootpath=

Since the IP-Config seems to be complete, I try to "ping" the IP of the board (10.0.10.1) from another machine A (10.0.1.16) in the domain - the board can not be pinged by A with the error "Destination Host Unreachable". Then I use the board to ping another machine B (10.0.1.18) in the domian. It turned out B can be pinged by the board. After board get response from B, wiredly A is able to get response from the board suddenly.

Why initially no machine can ping the board, but after the board pings a machie, other machines can ping the board? Does the command "ping" do something like resetting Phy?

Given that "ping" has a problem, I should not be supprised that NFS fail. But how should I solve it? Am I using the wrong boot up command for NFS? Is the kernel compilation missing something? Is it a bug with regard to the 2.6 kernel drivers for xps_ethernetlite?

I can replicate the problem with a smaller board, Digilent's FX12 evaulation board.

Here is one more experiment:
1) Initially, after the board boots up, a machine A can not ping the board;
2) Rather than pinging the machine A from the board, I execute "rdate -sp 206.246.118.250" (weirdly, the system date is not updated ...). Then the machine A is able to ping the board.

I try to mount NFS after booting up with RamDisk. I can ping 10.0.1.16 but I can not mount the directory (the settings on 10.0.1.16 is good since I'm always able to boot Kernel 2.4 with NFS).
1) if I do "mount 10.0.1.16:/exports/rootfs /mnt/temp", I get error
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).

2) if I do "mount -o nolock 10.0.1.16:/exports/rootfs /mnt/temp", I get no error message,
Then I enter /mnt/temp to do a "ls", I get error: "nfs: server 10.0.1.16 not responding, still trying".

It seems that although I can ping the machine, there is still something wrong ...

Problem with JTAG - mpc8315e

2009-07-10T12:11:01Z

Hello,

I've started the bring-up process in my board. All power sources are up and the JTAG interface is OK. I'm getting the following result, the JTAG starts and tries to stop the processor, but it doesn't stop.

I put BDI2000 log below.

- CONFIG: loading configuration file passed
- CONFIG: loading register definition passed
- TARGET: processing user reset request
- BDI asserts HRESET
- Reset JTAG controller passed
- Bypass check: 0x00000001 => 0x00000001
- JTAG exists check passed
- IDCODE is 0x268B401D
- BDI removes HRESET
- PVR is 0x80850020
- SVR is 0x80B40012
- BDI sets breakpoint at 0xFFF00100
- BDI resumes program execution
- COP status is 0x01
- Waiting for target stop failed
- TARGET: Break at boot vector failed, freeze forced
- TARGET: Target PVR is 0x80850020
- TARGET: resetting target passed
- TARGET: processing target startup ....
- COP status is 0x01
*** Core is freezed, no restart possible
# PPC: timeout while waiting for freeze
*** TARGET: processing target startup failed
# PPC: timeout while waiting for freeze
- TARGET: target will be restarted in 10 sec

Thanks in advance,

I've attached the BDI2000 configuration file. mpc8315e_atmx.cfg

MPC8313ERDB board reset problem

2009-06-02T01:48:35Z

Hi im using mpc8313erdb board. and i have modified the u-boot 1.3.0 code to suit my needs. But the problem is that now as soon as power up the board, the initial msgs are dumped on the telnet...and then as soon as the prompt is displayed....it resets....and keeps on doing the same...
the thing is i dont know what change has caused this....it would be of great help if anyone can guide me identify wat component have i messed up...

thanks and regards in advance
Deepak G

initramfs without compression

2009-05-07T00:02:41Z

Dear All,

I am using linux kernel 2.6.23 on my ppc405 for around two years. Up to now I was using Linux with build (gzipped) initramfs. Such an image kernel (gzipped compressed by default) is however too big and it does not
fit to my Flash memory. I have tried to compress the entire image with lzma compression and it looks much better. I have however difficulties with the initramfs which I want to keep uncompressed during the kernel built process.

Does anybody have some experience with that i.e. how to use the uncompressed initramfs.

Thank you for any hint.

M.

irq_of_parse_and_map usage - on mpc5121

2009-03-25T14:20:43Z

Hello, I have an application where I receive a pulse routed by the CPLD to IRQ1 and I need to assign a virtual interrupt for the driver that needs it (the driver part's OK, I see the instance in /proc/interrupts).
The new interrupt entry has been created in the dts file as well but I still need to relate the actual interrupt to the virtual interrupt I call in the driver...
I see the topic has already been covered - for example:

"..........Laxmikant Rashinkar wrote:
> But with the newer linux, request_irq() works only for 17, 18 & 19. cat /proc/interrupts shows that none of the interrupts above are in use.
> Any pointers on why request_irq() is behaving thus?
Note that you need to get the raw IRQ number from the device tree now,
and map it to a virtual IRQ number using irq_of_parse_and_map.
That is the number you pass to request_irq()..............."

That's exactly my need - but I don't know how to do it. Is there sample/ tutorial code - and where to put it in the file system - be available?
Thanks in advance

Video recording application on MPC8xxx (basic architecture Q:)

2009-03-22T04:34:36Z

Hi group,

I'm looking to get some initial advice to see
if my approach for an application seems reasonable.

It is an video recording application with minimum
processing logic but high throughput.

A PowerPC 8xxx board should shuffle a video stream
to disk drives.

At the import interface the video sensor provides
data in 200 Hz * ~0,5 MB. They are available via
dual-port RAMs to the local bus of the board.
Each RAM bank is reflecting a video frame and
accessible by the 32-bit local bus.

The processor should shuffle this to the SATA II
connected drives. A continuous stream of at least
130 MB/s over 1 h needs to be written. The drives
with this raw data are frequently moved to another
machine processing the raw data offline. The board
will not do any other task.

It would be nice if it could be done with standard
tools. A single (Freescale) board, standard Linux
and at most two SATA II connectors used at the
board.

Is this a reasonable scenario and some performance
discussions available. Especially the data flow
within the PPC and capabilities of the Linux drivers.

Thanks in advance
Wolfgang R.

virtual i2c support for PCA9541 i2c demux

2009-02-04T05:55:26Z

Hi,

I'm running linux-2.6.26 on custom 460EX based board.
This platform has PCA9541 i2c demux behind the PCA9548 I2C mux on I2C bus 0.
I'm wondering how can I add the demux to the virtual i2c tree (as far as I know there is no driver for this demux)

Regards,
Vladimir

Linux 2.6-xlnx git : trouble running binaries

2009-02-04T05:32:51Z

Hello,

I'm currently running a 2.6-xlnx kernel on a PowerPC 440 board, with a ramdisk.
The system is running correctly.
I added some binaries in the ramdisk, compiled with powerpc-linux-gcc.

But I can't run them, when I try to, here's what it comes :

root:/bin> ./helloppc
./helloppc: not found

(helloppc is just a simple helloworld in C)

The file seems to be right though :

root:/bin> ls -lisa helloppc
1485 10 -rwxrwxrwx 1 root root 9230 Jan 1 00:02 helloppc

xilinx@xilinx:~/V5FX/apps/hello$ file helloppc
helloppc: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped

I don't understand what i'm doing wrong. Do I have to use busybox to add my application ? Is there a special way to install it ?

Thanks in advance for your help.

Re: FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup (100005/1)

2009-02-03T01:13:38Z

Remi Lefevre wrote:

Ok, I'm sorry, I have incorrectly set the 60x pipeline depth to 0
instead of 1 in BCR register.
It works fine now. The side effect is interesting to know...

regards,
rémi
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Hi remi,
have you solved putting the bit of the 60x pipeline depth to '0' (depth of one) or to '1' (depth of zero)??
Anyway, i've got your identical problem but i cannot solve it through your suggested modification of the pipeline depth.
Have you found anything else about this???

Re: XIlinx EMAC mainline Linux 2.6.26

2009-01-19T02:30:47Z

Hi Joachim,
Could you tell me how did you selected support for xilinx emac driver in the denx tree?
Thanks a lot

Joachim Meyer wrote:

Ok, forget it.....it worked the whole time....my fault.

Greez
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

When do i need the DMA Buffer

2009-01-11T04:00:27Z

Hi All,
i have MPC8555 processor, also i have linux-kernel 2.6.19-rc5 on my board.i want to use the DMA on my board, just a simple example is enough for me but during my reading on how to use the DMA i have some questions:
1. The DMA buffer is always needed for all kind of buses or not? (I think this is valid in the ISA bus but not in the PCI bus, plz correct me if i m wrong?)
Note that my target is to transfer data from memory location to another memory location & it will be an overhead if i copy the data from the src to the DMA buffer then from the DMA buffer to the Destination.
isn't there any other way to avoid using that DMA buffer & to copy data from src to dest directly?
i read the documentation of my board & it tells me that it contain DMA engine which "is capable of transferring blocks of data from any legal address range to any
other legal address range."

2. i have read DMA-API.txt in the linux Documentation folder but i m little confused about the APIs that exist in this file. Actually, it is stated in this file the following:
"This document describes the DMA API.This API is split into two pieces. Part I describes the API and the corresponding pci_ API".

so if the DMA controller is connected to the PCI bus, am i obligated to use the pci_API & for any other case (like ISA bus or any other bus types) shall i use this generic API?
also what r the benefits of these APIs over the normal kmalloc? specially that i have read the following section in the DMA-mapping.txt:
"If you acquired your memory via the page allocator
(i.e. __get_free_page*()) or the generic memory allocators
(i.e. kmalloc() or kmem_cache_alloc()) then you may DMA to/from
that memory using the addresses returned from those routines."

thanks in advance for ur help

Re: yaboot: text mode or graphics mode?

2008-12-30T14:45:59Z

sumedh tirodkar wrote:
> I just found out that openfirmware boots into graphics mode(non-text
> mode). Now i wish to switch back to text mode. how do i do this?

Unfortunately unless you are running some kind of yaboot-accessible or
firmware-accessible x86 BIOS emulation, this isn't possible.

--
Matt
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@...
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: virtex uImage and serial ports

2008-12-30T13:18:33Z

Gidday John,

Thanks for the clue. This works. Now to get a proper 2.6 style (with udev, sysfs and all those new fangled things) root filesystem up and running. It boots fine with my old 2.4 style buildroot/busybox filesystem.

Thanks again.

Joshua

On Tuesday, 30 December, 2008 14:23, "John Linn" <John.Linn@...> said:

> It's been a while, but here's what I remember.
>
> You have to have SERIAL_OF* turned on in the kernel configuration to get
> the code to work.
>
> Then the device tree gets parsed by of_serial.c functions for the 16550
> uart.
>
> -- John
>
>> -----Original Message-----
>> From: Joshua Lamorie [mailto:jpl@...]
>> Sent: Tuesday, December 30, 2008 12:14 PM
>> To: John Linn
>> Cc: linuxppc-embedded@...
>> Subject: RE: virtex uImage and serial ports
>>
>> Gidday John,
>>
>> Thanks for the pointer. I think I have already gone through every
> possible page on the wiki, without
>> finding my answer. There are some great pointers however, such as
>> http://xilinx.wikidot.com/debugging-kernel-boot-problems.
>>
>> As far as I can tell, if I do 'make uImage', there is no code built
> into vmlinux that will parse the
>> device tree and set up the serial ports (at least as far as I can see
> with objdump -S). When it
>> boots, there is no console output and __log_buf doesn't show any
> serial ports detected during the
>> initialization of the serial driver.
>>
>> Which leads to my question, how does the 8250 serial driver get the
> information about the attached
>> serial ports from the dtb? Which part of the code parses the dtb,
> finds the "ns16550" and
>> updates/builds the platform_device information for the 8250 serial
> port driver?
>>
>> Joshua
>>
>> On Tuesday, 30 December, 2008 13:16, "John Linn"
> <John.Linn@...> said:
>>
>> > Hi Joshua,
>> >
>> > Have you looked at our wiki site at http://xilinx.wikidot.com as we
>> > quite a bit of information there.
>> >
>> > The ML405 board is a V2Pro chip so it should be pretty close to what
> you
>> > want using the default kernel config for virtex4.
>> >
>> > I haven't tested the console at 115,200 as I use it at 9600.
> Shouldn't
>> > be a problem, but may not hurt to stay at 9600 to get it working.
>> >
>> > There are pages on the wiki about using u-boot with the kernel also
> as
>> > it sounds like that's what you're doing.
>> >
>> > Thanks,
>> > John
>> >
>> >
>> >> -----Original Message-----
>> >> From: linuxppc-embedded-bounces+john.linn=xilinx.com@...
>> > [mailto:linuxppc-embedded-
>> >> bounces+john.linn=xilinx.com@...] On Behalf Of Joshua
> Lamorie
>> >> Sent: Wednesday, December 24, 2008 3:48 PM
>> >> To: linuxppc-embedded@...
>> >> Subject: virtex uImage and serial ports
>> >>
>> >> Gidday there,
>> >>
>> >> I am trying to get 2.6.27(ish) running on my custom Virtex-II Pro
>> > platform (I call it Q5). I already
>> >> have many years of running 2.4.26 and booting from u-boot.
>> >>
>> >> The problem is getting the console running. I have a device tree
> blob
>> > built and loaded into memory,
>> >> and by peeking at __log_buf I can see that it is reading this okay
>> > (i.e. it is correctly finding my
>> >> interrupt controller). However, by the time it goes to mount the
>> > ramdisk as root, it complains that
>> >> there is no console.
>> >>
>> >> I'm fairly certain /chosen has stdout pointing to the correct UART,
>> > and the console arguments are
>> >> ttyS0,115200.
>> >>
>> >> In looking through the code however, I cannot figure out how the
>> > uImage code actually initializes the
>> >> serial-ports for the XILINX_VIRTEX_GENERIC_BOARD. As I understand
> it,
>> > the only place where
>> >> serial_console_init is called, is within platform_init, and this
> isn't
>> > called for uImage.
>> >>
>> >> So, three questions.
>> >>
>> >> 1) How is the serial driver supposed to know where the platforms
>> > serial ports are?
>> >>
>> >> 2) If I wanted to scrap u-boot and just copy kernel/ramdisk/dtb to
>> > memory, which kernel make target
>> >> should I use? dtbImage, simpleImage?
>> >>
>> >> 3) What is the best, most modern image to build that should be used
> by
>> > u-boot?
>> >>
>> >> Thanks in advance
>> >>
>> >> Joshua
>> >>
>> >> p.s. I've been trying with kernel.org mainline, xilinx git and denx
>> > ELDK xenomai (2.6.24). U-boot is
>> >> built from latest git source. DTS file built from XPS 9.1i with
>> > latest service packs, and turned
>> >> into DTB with latest dtc source from git.
>> >>
>> >>
>> >> --
>> >> Xiphos Technologies
>> >> (514) 847-9474 x227
>> >> (514) 848-9644 fax
>> >>
>> >> www.xiphos.com
>> >> _______________________________________________
>> >> The information transmitted is intended only for the
>> >> person or entity to which it is addressed and may contain
>> >> confidential and/or privileged material. If you have
>> >> received this in error, please contact the sender and delete
>> >> this communication and any copy immediately. Thank you.
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> Linuxppc-embedded mailing list
>> >> Linuxppc-embedded@...
>> >> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>> >
>> >
>> > This email and any attachments are intended for the sole use of the
> named
>> > recipient(s) and contain(s) confidential information that may be
> proprietary,
>> > privileged or copyrighted under applicable law. If you are not the
> intended
>> > recipient, do not read, copy, or forward this email message or any
> attachments.
>> > Delete this email message and any attachments immediately.
>> >
>> >
>> > _______________________________________________
>> > Linuxppc-embedded mailing list
>> > Linuxppc-embedded@...
>> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>> >
>>
>>
>> --
>> Xiphos Technologies
>> (514) 847-9474 x227
>> (514) 848-9644 fax
>>
>> www.xiphos.com
>> _______________________________________________
>> The information transmitted is intended only for the
>> person or entity to which it is addressed and may contain
>> confidential and/or privileged material. If you have
>> received this in error, please contact the sender and delete
>> this communication and any copy immediately. Thank you.
>>
>>
>>
>>
>
>
> This email and any attachments are intended for the sole use of the named
> recipient(s) and contain(s) confidential information that may be proprietary,
> privileged or copyrighted under applicable law. If you are not the intended
> recipient, do not read, copy, or forward this email message or any attachments.
> Delete this email message and any attachments immediately.
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@...
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

--
Xiphos Technologies
(514) 847-9474 x227
(514) 848-9644 fax

www.xiphos.com
_______________________________________________
The information transmitted is intended only for the
person or entity to which it is addressed and may contain
confidential and/or privileged material. If you have
received this in error, please contact the sender and delete
this communication and any copy immediately. Thank you.

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@...
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

RE: virtex uImage and serial ports

2008-12-30T11:23:07Z

It's been a while, but here's what I remember.

You have to have SERIAL_OF* turned on in the kernel configuration to get
the code to work.

Then the device tree gets parsed by of_serial.c functions for the 16550
uart.

-- John

> -----Original Message-----
> From: Joshua Lamorie [mailto:jpl@...]
> Sent: Tuesday, December 30, 2008 12:14 PM
> To: John Linn
> Cc: linuxppc-embedded@...
> Subject: RE: virtex uImage and serial ports
>
> Gidday John,
>
> Thanks for the pointer. I think I have already gone through every

possible page on the wiki, without
> finding my answer. There are some great pointers however, such as
> http://xilinx.wikidot.com/debugging-kernel-boot-problems.
>
> As far as I can tell, if I do 'make uImage', there is no code built
into vmlinux that will parse the
> device tree and set up the serial ports (at least as far as I can see
with objdump -S). When it
> boots, there is no console output and __log_buf doesn't show any
serial ports detected during the
> initialization of the serial driver.
>
> Which leads to my question, how does the 8250 serial driver get the
information about the attached
> serial ports from the dtb? Which part of the code parses the dtb,
finds the "ns16550" and
> updates/builds the platform_device information for the 8250 serial
port driver?
>
> Joshua
>
> On Tuesday, 30 December, 2008 13:16, "John Linn"
<John.Linn@...> said:
>
> > Hi Joshua,
> >
> > Have you looked at our wiki site at http://xilinx.wikidot.com as we
> > quite a bit of information there.
> >
> > The ML405 board is a V2Pro chip so it should be pretty close to what
you
> > want using the default kernel config for virtex4.
> >
> > I haven't tested the console at 115,200 as I use it at 9600.
Shouldn't
> > be a problem, but may not hurt to stay at 9600 to get it working.
> >
> > There are pages on the wiki about using u-boot with the kernel also
as

> > it sounds like that's what you're doing.
> >
> > Thanks,
> > John
> >
> >
> >> -----Original Message-----
> >> From: linuxppc-embedded-bounces+john.linn=xilinx.com@...
> > [mailto:linuxppc-embedded-
> >> bounces+john.linn=xilinx.com@...] On Behalf Of Joshua

Lamorie

> >> Sent: Wednesday, December 24, 2008 3:48 PM
> >> To: linuxppc-embedded@...
> >> Subject: virtex uImage and serial ports
> >>
> >> Gidday there,
> >>
> >> I am trying to get 2.6.27(ish) running on my custom Virtex-II Pro
> > platform (I call it Q5). I already
> >> have many years of running 2.4.26 and booting from u-boot.
> >>
> >> The problem is getting the console running. I have a device tree

blob

> > built and loaded into memory,
> >> and by peeking at __log_buf I can see that it is reading this okay
> > (i.e. it is correctly finding my
> >> interrupt controller). However, by the time it goes to mount the
> > ramdisk as root, it complains that
> >> there is no console.
> >>
> >> I'm fairly certain /chosen has stdout pointing to the correct UART,
> > and the console arguments are
> >> ttyS0,115200.
> >>
> >> In looking through the code however, I cannot figure out how the
> > uImage code actually initializes the
> >> serial-ports for the XILINX_VIRTEX_GENERIC_BOARD. As I understand

it,
> > the only place where
> >> serial_console_init is called, is within platform_init, and this
isn't

> > called for uImage.
> >>
> >> So, three questions.
> >>
> >> 1) How is the serial driver supposed to know where the platforms
> > serial ports are?
> >>
> >> 2) If I wanted to scrap u-boot and just copy kernel/ramdisk/dtb to
> > memory, which kernel make target
> >> should I use? dtbImage, simpleImage?
> >>
> >> 3) What is the best, most modern image to build that should be used

> > u-boot?
> >>
> >> Thanks in advance
> >>
> >> Joshua
> >>
> >> p.s. I've been trying with kernel.org mainline, xilinx git and denx
> > ELDK xenomai (2.6.24). U-boot is
> >> built from latest git source. DTS file built from XPS 9.1i with
> > latest service packs, and turned
> >> into DTB with latest dtc source from git.
> >>
> >>
> >> --
> >> Xiphos Technologies
> >> (514) 847-9474 x227
> >> (514) 848-9644 fax
> >>
> >> www.xiphos.com
> >> _______________________________________________
> >> The information transmitted is intended only for the
> >> person or entity to which it is addressed and may contain
> >> confidential and/or privileged material. If you have
> >> received this in error, please contact the sender and delete
> >> this communication and any copy immediately. Thank you.
> >>
> >>
> >>
> >> _______________________________________________
> >> Linuxppc-embedded mailing list
> >> Linuxppc-embedded@...
> >> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
> >
> > This email and any attachments are intended for the sole use of the

named
> > recipient(s) and contain(s) confidential information that may be
proprietary,
> > privileged or copyrighted under applicable law. If you are not the
intended
> > recipient, do not read, copy, or forward this email message or any
attachments.

> > Delete this email message and any attachments immediately.
> >
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@...
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> >
>
>
> --
> Xiphos Technologies
> (514) 847-9474 x227
> (514) 848-9644 fax
>
> www.xiphos.com
> _______________________________________________
> The information transmitted is intended only for the
> person or entity to which it is addressed and may contain
> confidential and/or privileged material. If you have
> received this in error, please contact the sender and delete
> this communication and any copy immediately. Thank you.
>
>
>
>

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@...
https://ozlabs.org/mailman/listinfo/linuxppc-embedded