[PATCH] ARM: OMAP: Make OMAP1 work again

[PATCH] ARM: OMAP: Make OMAP1 work again

[Dirk Behme]

[-- Attachment #1: Type: text/plain, Size: 353 bytes --]


In mach-omap1/mailbox.c the mailbox name is .name = "DSP"
while in plat-omap/dsp/dsp_core.c function  dsp_mbox_init()
asks for "dsp". This results in a strcmp() mismatch and then
OMAP1 system crashes due to NULL pointer. OMAP2 is correct,
there .name is "dsp". Correct OMAP1 name to "dsp" as well.

Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>


[-- Attachment #2: omap1_dsp_mailbox_patch.txt --]
[-- Type: text/plain, Size: 351 bytes --]

--- ./arch/arm/mach-omap1/mailbox.c_orig	2006-10-06 11:08:50.000000000 +0200
+++ ./arch/arm/mach-omap1/mailbox.c	2006-10-06 11:09:13.000000000 +0200
@@ -136,7 +136,7 @@ static struct omap_mbox1_priv omap1_mbox
 };
 
 struct omap_mbox mbox_dsp_info = {
-	.name = "DSP",
+	.name = "dsp",
 	.ops  = &omap1_mbox_ops,
 	.priv = &omap1_mbox_dsp_priv,
 };



[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Bug? - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Hello,

When trying to build the 2.6.18-omap1 kernel with the frame buffer support
option for the OSK selected, the build fails while trying to compile
".../drivers/video/omap/omapfb_main.c" with numerous errors.

I selected frame buffer support as shown at the "OSK for Dummies" web site
(albeit without the "OMAP internal LCD controller support" option checked as
it apparently no longer exists)...

http://oskfordummies.hp.infoseek.co.jp/howto/lcd.html

Has anyone successfully built the 2.6.18-omap1 kernel with frame buffer
support?  Is my problem a known bug?  Any help is appreciated.

I am going to try to revert to a 2.6.14-omap1 kernel, but there are no
guarantees that the old build will resolve my problem.

Thanks, in advance.
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu

Re: Bug? - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Dirk Behme]

Sideleau, Scott R wrote:
> When trying to build the 2.6.18-omap1 kernel with the frame buffer support
> option for the OSK selected, the build fails while trying to compile
> ".../drivers/video/omap/omapfb_main.c" with numerous errors.
> 
> I selected frame buffer support as shown at the "OSK for Dummies" web site
> (albeit without the "OMAP internal LCD controller support" option checked as
> it apparently no longer exists)...
> 
> http://oskfordummies.hp.infoseek.co.jp/howto/lcd.html
> 
> Has anyone successfully built the 2.6.18-omap1 kernel with frame buffer
> support?

With patch I sent some minutes ago most recent git works for 
me on OSK with frame buffer and Mistral LCD.

Do you use recent git? What are your errors?

I use

CONFIG_OMAP_OSK_MISTRAL=y
CONFIG_VIDEO_V4L2=y
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_OMAP=y
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2
CONFIG_FB_OMAP_DMA_TUNE=y

Cheers

Dirk

RE: Bug? - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Hello,

Thanks for the reply, Dirk.

> With patch I sent some minutes ago most recent git works for 
> me on OSK with frame buffer and Mistral LCD.
>
> Do you use recent git? What are your errors?

I was quite certain I was not using the latest Git, so I've spent most of the
day updating everything.  I grabbed the latest 2.6.18-omap1 kernel from the
repository (and put it in a completely new place) via:

git-clone git://source.mvista.com/git/linux-omap-2.6.git

I'm quite certain I have the absolute latest git right now.  I then chose the
proper frame buffer support via 'make menuconfig' that I then compared
against your list.  From your list, the following lines match in my .config
file:

CONFIG_VIDEO_V4L2=y
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_OMAP=y
CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE=2

The following lines simply do not exist in my .config file (even commented
out, as they should appear if I didn't select them):

CONFIG_OMAP_OSK_MISTRAL=y
CONFIG_FB_OMAP_DMA_TUNE=y

I just attempted another compile and it failed at the same point in
'omapfb_main.c'.  Here's an excerpt of the errors dumped to my terminal:

=====
drivers/video/omap/omapfb_main.c:1558: error: request for member
^[$(B!F^[(Bfb_info^[$(B!G^[(B in something not a structure or union
drivers/video/omap/omapfb_main.c:1558: warning: passing argument 1 of
^[$(B!F^[(Bomapfb_blank^[$(B!G^[(B makes integer from pointer without a cast
drivers/video/omap/omapfb_main.c:1558: warning: passing argument 2 of
^[$(B!F^[(Bomapfb_blank^[$(B!G^[(B makes pointer from integer without a cast
drivers/video/omap/omapfb_main.c: In function ^[$(B!F^[(Bomapfb_setup^[$(B!G^[(B:
drivers/video/omap/omapfb_main.c:1609: error: assignment of read-only
location
drivers/video/omap/omapfb_main.c: In function ^[$(B!F^[(Bomapfb_init^[$(B!G^[(B:
drivers/video/omap/omapfb_main.c:1638: warning: implicit declaration of
function ^[$(B!F^[(Bfb_get_options^[$(B!G^[(B
drivers/video/omap/omapfb_main.c: At top level:
drivers/video/omap/omapfb_main.c:1657: error: invalid operands to binary /
drivers/video/omap/omapfb_main.c:1657: error: initializer element is not
constant
drivers/video/omap/omapfb_main.c:1657: error: (near initialization for
^[$(B!F^[(B__param_arr_vram.max^[$(B!G^[(B)
drivers/video/omap/omapfb_main.c:1657: error: initializer element is not
constant
drivers/video/omap/omapfb_main.c:1657: error: (near initialization for
^[$(B!F^[(B__param_arr_vram.elem^[$(B!G^[(B)
make[3]: *** [drivers/video/omap/omapfb_main.o] Error 1
make[2]: *** [drivers/video/omap] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
=====

Any help would be appreciated.  Thanks, in advance.
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu
 

RE: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Hello,

I was finally able to get a successful compile of the 2.6.18-omap1 kernel
with the help of Dirk Behme's config file (thanks again, Dirk).  Now, though,
the OSK is unable to boot the new kernel, but instead just hangs.  From my
console (as it has been running for the last half-hour)...

=====
U-Boot 1.1.4 (Aug 29 2006 - 17:05:48)

CPU:   OMAP162123 at 96.0 MHz (DPLL1=96.0 MHz)
Board: OSK5912
DRAM:  32 MB
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 00100000 ...
   Image Name:   OE
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    1065210 Bytes =  1 MB
   Load Address: 10c08000
   Entry Point:  10c08000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...
=====

This kernel build includes the two pushes earlier today by Tony Lindgren.

Any ideas?  Any and all help/direction is appreciated.
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu
 

Re: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Dirk Behme]

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

Sideleau, Scott R wrote:
> ## Booting image at 00100000 ...
>    Image Name:   OE
>    Image Type:   ARM Linux Kernel Image (gzip compressed)
>    Data Size:    1065210 Bytes =  1 MB
>    Load Address: 10c08000
>    Entry Point:  10c08000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK

I wonder about the adresses used here. Do you followed

http://oskfordummies.hp.infoseek.co.jp/howto/flash_kernel.html

?

I would assume kernel at 0x40000 and start address/entry
point at 0x10008000. E.g.:

## Checking image at 00040000 ...
      Image Name:   Linux-2.6.11-omap1
      Image Type:   ARM Linux Kernel Image (umcompressed)
      Data Size:    1159328 Bytes = 1.1 MB
      Load Address: 10008000
      Entry Point:  10008000
      Veryfying Checksum ... OK

> Any ideas?  Any and all help/direction is appreciated.

For debugging, enable

Kernel hacking -> Kernel debugging -> Kernel low-level
debugging functions

(and temporarily apply patch in attachment, seems to be
necessary to work low level debugging properly).

Dirk



[-- Attachment #2: temp_low_level_debug_patch.txt --]
[-- Type: text/plain, Size: 872 bytes --]

--- ./arch/arm/plat-omap/clock.c_orig	2006-10-06 21:16:49.000000000 +0200
+++ ./arch/arm/plat-omap/clock.c	2006-10-06 21:17:03.000000000 +0200
@@ -135,7 +135,7 @@ void clk_disable(struct clk *clk)
 		return;
 
 	spin_lock_irqsave(&clockfw_lock, flags);
-	BUG_ON(clk->usecount == 0);
+	//BUG_ON(clk->usecount == 0);
 	if (arch_clock->clk_disable)
 		arch_clock->clk_disable(clk);
 	spin_unlock_irqrestore(&clockfw_lock, flags);
--- ./arch/arm/mach-omap1/clock.c_orig	2006-10-06 21:18:57.000000000 +0200
+++ ./arch/arm/mach-omap1/clock.c	2006-10-06 21:16:21.000000000 +0200
@@ -651,7 +651,7 @@ int __init omap1_clk_init(void)
 
 	/* USB_REQ_EN will be disabled later if necessary (usb_dc_ck) */
 	reg = omap_readw(SOFT_REQ_REG) & (1 << 4);
-	omap_writew(reg, SOFT_REQ_REG);
+	//omap_writew(reg, SOFT_REQ_REG);
 	if (!cpu_is_omap15xx())
 		omap_writew(0, SOFT_REQ_REG2);
 



[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Re: [PATCH] ARM: OMAP: Make OMAP1 work again

[Tony Lindgren]

* Dirk Behme <dirk.behme@googlemail.com> [061006 12:58]:
> 
> In mach-omap1/mailbox.c the mailbox name is .name = "DSP"
> while in plat-omap/dsp/dsp_core.c function  dsp_mbox_init()
> asks for "dsp". This results in a strcmp() mismatch and then
> OMAP1 system crashes due to NULL pointer. OMAP2 is correct,
> there .name is "dsp". Correct OMAP1 name to "dsp" as well.
> 
> Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
> 

> --- ./arch/arm/mach-omap1/mailbox.c_orig	2006-10-06 11:08:50.000000000 +0200
> +++ ./arch/arm/mach-omap1/mailbox.c	2006-10-06 11:09:13.000000000 +0200
> @@ -136,7 +136,7 @@ static struct omap_mbox1_priv omap1_mbox
>  };
>  
>  struct omap_mbox mbox_dsp_info = {
> -	.name = "DSP",
> +	.name = "dsp",
>  	.ops  = &omap1_mbox_ops,
>  	.priv = &omap1_mbox_dsp_priv,
>  };
> 
> 

Great, I pushed it.

Regards,

Tony

RE: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Hello,

Thanks again for working with me, Dirk.  :)

I wiped everything and started again, using the memory addresses from that
guide (I had been following a different one)... it still hangs.  Output is as
follows...

=====
## Booting image at 00040000 ...
   Image Name:   OE
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    1065210 Bytes =  1 MB
   Load Address: 10c08000
   Entry Point:  10c08000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...
=====

The Load Address and Entry Point have remained the same, though.  The rest of
the flash is empty as I manually erased it all.

Any ideas?
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu
 

-----Original Message-----
From: Dirk Behme [mailto:dirk.behme@googlemail.com] 
Sent: Friday, October 06, 2006 3:31 PM
To: Sideleau, Scott R
Cc: OMAP
Subject: Re: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

Sideleau, Scott R wrote:
> ## Booting image at 00100000 ...
>    Image Name:   OE
>    Image Type:   ARM Linux Kernel Image (gzip compressed)
>    Data Size:    1065210 Bytes =  1 MB
>    Load Address: 10c08000
>    Entry Point:  10c08000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK

I wonder about the adresses used here. Do you followed

http://oskfordummies.hp.infoseek.co.jp/howto/flash_kernel.html

?

I would assume kernel at 0x40000 and start address/entry
point at 0x10008000. E.g.:

## Checking image at 00040000 ...
      Image Name:   Linux-2.6.11-omap1
      Image Type:   ARM Linux Kernel Image (umcompressed)
      Data Size:    1159328 Bytes = 1.1 MB
      Load Address: 10008000
      Entry Point:  10008000
      Veryfying Checksum ... OK

> Any ideas?  Any and all help/direction is appreciated.

For debugging, enable

Kernel hacking -> Kernel debugging -> Kernel low-level
debugging functions

(and temporarily apply patch in attachment, seems to be
necessary to work low level debugging properly).

Dirk

Re: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Jonathan McDowell]

On Fri, Oct 06, 2006 at 04:38:41PM -0400, Sideleau, Scott R wrote:
> Thanks again for working with me, Dirk.  :)
> 
> I wiped everything and started again, using the memory addresses from that
> guide (I had been following a different one)... it still hangs.  Output is as
> follows...
> 
> =====
> ## Booting image at 00040000 ...
>    Image Name:   OE
>    Image Type:   ARM Linux Kernel Image (gzip compressed)
>    Data Size:    1065210 Bytes =  1 MB
>    Load Address: 10c08000
>    Entry Point:  10c08000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
> 
> Starting kernel ...
> =====
> 
> The Load Address and Entry Point have remained the same, though.  The rest of
> the flash is empty as I manually erased it all.
> 
> Any ideas?

OOI do you have CONFIG_DEBUG_MUTEXES set? I've found on the E3 having
this set means that the kernel hangs on boot with no output whereas
disabling it results in an ok boot. I've been meaning to go back and try
and work out exactly what's going wrong but haven't got round to it yet.

J.

-- 
/-\                             |    Open mouth, insert foot, echo
|@/  Debian GNU/Linux Developer |          internationally.
\-                              |

RE: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Hello,

Thanks again for any help/advice offered thus far.

Jonathan McDowell [noodles@earth.li] wrote...
> OOI do you have CONFIG_DEBUG_MUTEXES set?

I don't see that option in my .config at all, so it is not enabled.

Dirk Behme [dirk.behme@googlemail.com] wrote...
> For easier debugging, I propose to first use uncompressed 
> image (the manuals seem to use compressed one):

I re-built an uncompressed binary, at your recommendation.  After copying
this to the OSK, I was able to successfully boot to a point.  It was pointed
out to me that I would need to mount the rootfs to get it to boot any
further.

My uncompressed kernel image was 2.2-MB (2278208 bytes).  It was written to
flash at memory location 0x00040000 on the OSK.  That means the kernel ends
(after some hex arithmetic) at 0x0022c340.  It seems to make sense to me,
then, that I could drop the rootfs at 0x0022c341 since it is supposed to
start at 0x00240000 anyway.

I wrapped up a JFFS2 rootfs weighing in at 5.2-MB (5242880 bytes) and dropped
it in memory location 0x0022c341 on the OSK.  The OSK boots a little bit
further this time, but is giving some more errors I don't really understand.
Output is as follows:

=====
U-Boot 1.1.4 (Aug 29 2006 - 17:05:48)

CPU:   OMAP162123 at 96.0 MHz (DPLL1=96.0 MHz)
Board: OSK5912
DRAM:  32 MB
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 00040000 ...
   Image Name:   Linux Kernel Image
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2278144 Bytes =  2.2 MB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Linux version 2.6.18-omap1 (bigd0g@porkchop) (gcc version 4.1.1) #1 PREEMPT
Sat Oct 7 13:08:54 IST 2006
CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177
Machine: TI-OSK
Memory policy: ECC disabled, Data cache writeback
OMAP162123 revision 2 handled as 16xx id: e4059089bfcb0c11
SRAM: Mapped pa 0x20000000 to va 0xd0000000 size: 0x100000
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists.  Total pages: 8192
Kernel command line: console=ttyS0,115200 noinitrd rw ip=on rootfstype=jffs2
root=/dev/mtdblock3
Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2833 ARM_CKCTL: 0x2000
Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz
Total of 128 interrupts in 4 interrupt banks
OMAP GPIO hardware version 1.0
MUX: initialized M7_1610_GPIO62
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 30092KB available (1816K code, 394K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
MUX: initialized P20_1610_GPIO4
OMAP DMA hardware version 1
DMA capabilities: 000c0000:00000000:01ff:003f:007f
Initializing OMAP McBSP system
omap_dsp_init() done
USB: hmc 16, usb0 2 wires
i2c_omap i2c_omap.1: bus 0 rev2.2 at 100 kHz
tps65010: version 2 May 2005
No IRQF_TRIGGER set_type function for IRQ 353 (MPUIO)
tps65010: battery charging
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
Power Management for TI OMAP.
MUX: initialized T20_1610_LOW_PWR
Unbalanced enable for IRQ 10
BUG: warning at kernel/irq/manage.c:118/enable_irq()
NetWinder Floating Point Emulator V0.97 (double precision)
OMAP OCPI interconnect driver loaded
dsp dsp: OMAP DSP driver initialization
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
omapfb: configured for panel osk
omapfb: LCDC initialized
omapfb omapfb: Pixel clock divider value is obsolete.
Try to set pixel_clock to 8000 and pcd to 0 in drivers/video/omap/lcd_osk.c
and submit a patch.
MUX: initialized PWL
Console: switching to colour frame buffer device 30x40
omapfb: Framebuffer initialized. Total vram 155648 planes 1
omapfb: Pixclock 8000 kHz hfreq 20.1 kHz vfreq 63.3 Hz
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654
RAMDISK driver initialized: 1 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
i2c /dev entries driver
Clock enabled to MCBSP1 & 3
TLV320AIC23 I2C version 1.8 (10-Feb-2006)
omapflash.0: Found 1 x16 devices at 0x0 in 16-bit bank

omapflash.0: Found 1 x16 devices at 0x1000000 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Creating 4 MTD partitions on "omapflash.0":
0x00000000-0x00020000 : "bootloader"
0x00020000-0x00040000 : "params"
0x00040000-0x00240000 : "kernel"
0x00240000-0x02000000 : "filesystem"
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
IP-Config: No network devices available.
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000023c: 0x8214
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000244: 0x86ac
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000248: 0x8ad8
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000024c: 0x86c0
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000250: 0x8c84
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000254: 0x0002
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000258: 0x0400
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000025c: 0x8514
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000264: 0x8bb0
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000268: 0x8574
instead
Further such events for this erase block will not be printed
Empty flash at 0x0000059c ends at 0x000005a0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000: 0x0a73
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004: 0x5f66
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020008: 0x665f
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c: 0x540a
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020010: 0xd1e6
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014: 0xc766
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020018: 0xaa54
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002001c: 0xd666
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020020: 0x0b73
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020024: 0xad64
instead
Further such events for this erase block will not be printed
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 236, bad_blocks 0, c->nr_blocks 238
VFS: No root yet, retrying to mount root on mtdblock3 (unknown-block(31,3))
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000023c: 0x8214
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000244: 0x86ac
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000248: 0x8ad8
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000024c: 0x86c0
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000250: 0x8c84
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000254: 0x0002
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000258: 0x0400
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000025c: 0x8514
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000264: 0x8bb0
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000268: 0x8574
instead
Further such events for this erase block will not be printed
Empty flash at 0x0000059c ends at 0x000005a0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000: 0x0a73
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004: 0x5f66
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020008: 0x665f
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c: 0x540a
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020010: 0xd1e6
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014: 0xc766
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020018: 0xaa54
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002001c: 0xd666
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020020: 0x0b73
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020024: 0xad64
instead
Further such events for this erase block will not be printed
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 236, bad_blocks 0, c->nr_blocks 238
VFS: No root yet, retrying to mount root on mtdblock3 (unknown-block(31,3))
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000023c: 0x8214
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000244: 0x86ac
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000248: 0x8ad8
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000024c: 0x86c0
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000250: 0x8c84
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000254: 0x0002
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000258: 0x0400
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000025c: 0x8514
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000264: 0x8bb0
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000268: 0x8574
instead
Further such events for this erase block will not be printed
Empty flash at 0x0000059c ends at 0x000005a0
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020000: 0x0a73
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004: 0x5f66
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020008: 0x665f
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c: 0x540a
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020010: 0xd1e6
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014: 0xc766
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020018: 0xaa54
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002001c: 0xd666
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020020: 0x0b73
instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020024: 0xad64
instead
Further such events for this erase block will not be printed
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 236, bad_blocks 0, c->nr_blocks 238
VFS: No root yet, retrying to mount root on mtdblock3 (unknown-block(31,3))
=====

Any ideas?  Thanks, in advance.
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu
 

RE: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Sideleau, Scott R [srs@WPI.EDU] wrote...
> It seems to make sense to me, then, that I could drop the rootfs at
> 0x0022c341 since it is supposed to start at 0x00240000 anyway.

I'm sorry, I meant 0x0026c341.  Please note the 6.

0x0022c341 was the size of the kernel, plus 0x00040000 yields 0x0026c341 -- a
memory location already beyond 0x00240000, the listed start location for the
rootfs.
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu
 

RE: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

I re-compiled the kernel again with low-level debugging enabled and patched,
as Dirk Behme previously requested of me.

I game up trying to put the rootfs near the kernel in flash, so I moved it
back to 0x1000000, far away from everything.

The board will boot and appears to successfully mount the rootfs, but still
hangs awkwardly.  The output is quite large, so I put it in a pastebin...

http://rafb.net/paste/results/Z0L4A080.html

Any ideas?
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu
 

RE: Can't Boot - OSK Frame Buffer Support in Kernel 2.6.18-omap1

[Sideleau, Scott R]

Hello,

I noticed that after each attempt of running the kernel, the kernel would
turn up with a "Bad CRC Checksum" error.  I decided, on a whim, to try
starting over with flash protection enabled.  It appeared to get a bit
further (tried to start the Dropbear SSH server), but still fails in the end.

Output from my console is, again, quite large.  I do not know if it is of any
help in this troubleshooting, but I made it available for viewing at the
following pastebin...

http://rafb.net/paste/results/Dst2qf91.html

Any ideas?  Thanks, in advance, for any help/advice you can offer.
______________________________________________
Scott R. Sideleau
ECE '07, Worcester Polytechnic Institute
@ MQP Ireland A'06, University of Limerick
+353 61-307310 / srs@wpi.edu