4.13 (and probably all recent) kernels refuse to boot on one Nokia N950, work or another

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

Quoted 11 lines · Pavel Machek

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

Quoted 2 lines

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

"Uart pins not muxed in NOLO" would certainly explain my problems. In 3.5.X, output works even in decompressor ("Uncompressing kernel... done, booting linux").

Quoted 9 lines

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

Quoted 2 lines

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Quoted 6 lines · Pavel Machek

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

Quoted 7 lines

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

Quoted 15 lines · Tony Lindgren

Quoted 6 lines · Pavel Machek

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

Quoted 7 lines

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

Quoted 6 lines

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

Uhuh. It looks like "P" nokia really wants initrd, otherwise it will not boot.

I got "uncompressing Linux 4.13" on serial console now, debug LEDs blinking, and if I use a flashlight, I see output on the screen, too.

(What do I need to do to get the backlight working?)

Hi,

Quoted 29 lines · Pavel Machek

Quoted 15 lines · Tony Lindgren

Quoted 6 lines · Pavel Machek

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

Quoted 7 lines

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

Quoted 6 lines

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

Uhuh. It looks like "P" nokia really wants initrd, otherwise it will not boot.

I got "uncompressing Linux 4.13" on serial console now, debug LEDs blinking, and if I use a flashlight, I see output on the screen, too.

Quoted 1 line

(What do I need to do to get the backlight working?)

Glad you got it working :) For backlight you can add this in drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c:

add the following code at the end of dsicm_probe:

-----------------------------------------------------------
mutex_unlock(&ddata->lock);
mutex_lock(&ddata->lock);
ddata->in->ops.dsi->bus_lock(ddata->in);
r = dsicm_wake_up(ddata);
if (!r)

    r = dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 100);

ddata->in->ops.dsi->bus_unlock(ddata->in);
mutex_unlock(&ddata->lock);
-----------------------------------------------------------

-- Sebastian

Quoted 34 lines · Sebastian Reichel

Hi,

Quoted 30 lines · Pavel Machek

Quoted 15 lines · Tony Lindgren

Quoted 6 lines · Pavel Machek

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

Quoted 7 lines

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

Quoted 6 lines

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

Uhuh. It looks like "P" nokia really wants initrd, otherwise it will not boot.

I got "uncompressing Linux 4.13" on serial console now, debug LEDs blinking, and if I use a flashlight, I see output on the screen, too.

(What do I need to do to get the backlight working?)

Quoted 4 lines

Glad you got it working :) For backlight you can add this in drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c:

add the following code at the end of dsicm_probe:

You did not actually include code to paste into panel-dsi-cm, can you try a again?

Quoted 11 lines

-----------------------------------------------------------
mutex_unlock(&ddata->lock);
mutex_lock(&ddata->lock);
ddata->in->ops.dsi->bus_lock(ddata->in);
r = dsicm_wake_up(ddata);
if (!r)

    r = dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 100);

ddata->in->ops.dsi->bus_unlock(ddata->in);
mutex_unlock(&ddata->lock);
-----------------------------------------------------------

Quoted 1 line

-- Sebastian

Quoted 7 lines

Quoted 4 lines

Glad you got it working :) For backlight you can add this in drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c:

add the following code at the end of dsicm_probe:

You did not actually include code to paste into panel-dsi-cm, can you try a again?

I added it directly below and you quoted it. I guess you mistook it for a signature or something :)

If someone knows how to fix the backlight, it would still be useful.

Then I was (finally!) able to run dmesg, and that tells me:

[    0.816040] mousedev: PS/2 mouse device common for all mice
[    0.817657] input: TWL4030 Keypad as
/devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl at 48:keypad/input/input0
[    0.820800] i2c /dev entries driver
[    0.830261] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout
60 sec
[    0.836212] omap_hsmmc 480b4000.mmc: RX DMA channel request failed
[    0.840026] ledtrig-cpu: registered to indicate activity on CPUs
[    0.840789] omap-aes 480c5000.aes: OMAP AES hw accel rev: 2.6
[    0.840942] omap-aes 480c5000.aes: Unable to request in DMA channel
[    0.841644] omap-aes 480c5000.aes: will run requests pump with

realtime priority

Kernel 4.13-rc2.

Quoted 4 lines

I got "uncompressing Linux 4.13" on serial console now, debug LEDs blinking, and if I use a flashlight, I see output on the screen, too.

(What do I need to do to get the backlight working?)

Glad you got it working :) For backlight you can add this in drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c:

add the following code at the end of dsicm_probe:

-----------------------------------------------------------
mutex_unlock(&ddata->lock);
mutex_lock(&ddata->lock);
ddata->in->ops.dsi->bus_lock(ddata->in);
r = dsicm_wake_up(ddata);
if (!r)

    r = dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 100);

ddata->in->ops.dsi->bus_unlock(ddata->in);
mutex_unlock(&ddata->lock);
-----------------------------------------------------------

Quoted 4 lines

I got "uncompressing Linux 4.13" on serial console now, debug LEDs blinking, and if I use a flashlight, I see output on the screen, too.

(What do I need to do to get the backlight working?)

Glad you got it working :) For backlight you can add this in drivers/gpu/drm/omapdrm/displays/panel-dsi-cm.c:

add the following code at the end of dsicm_probe:

-----------------------------------------------------------
mutex_unlock(&ddata->lock);
mutex_lock(&ddata->lock);
ddata->in->ops.dsi->bus_lock(ddata->in);
r = dsicm_wake_up(ddata);
if (!r)

    r = dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 100);

ddata->in->ops.dsi->bus_unlock(ddata->in);
mutex_unlock(&ddata->lock);
-----------------------------------------------------------

Quoted 19 lines · Tony Lindgren

Quoted 6 lines · Pavel Machek

Hi!

...hardware should be identical. 3.5.3-nemo kernel seems to work on both. 4.13-rc2 with display and clock patches boots on phone "S", but does not on phone "P"; nothing nothing is received on serial port.

Quoted 7 lines

There is some difference in the bootloaders: S's bootloader provides lots of debug info, P's is silent. R&D settings do _not_ have influence on bootloader. We know P's serial works, as 3.5.3 kernel prints "Uncompressing linux...booting" there.

I'll need to return "S" phone and serial cable tommorow. If you have any ideas, let me know.

If you get nothing out of the uart, chances are the pins are not muxed for the uart in nolo and maybe kernel dts is missing the pinctrl entries for uart?

Quoted 2 lines

Also try booting with mem=512M at 0x80000000 or 256M or 768M. Maybe the memory is different size or partially broken?

Uhuh. It looks like "P" nokia really wants initrd, otherwise it will not boot.

3.5.3-nemo kernel seems to work

If you have
any ideas, let me know.

Hi Pavel,

Quoted 1 line · Pavel Machek

3.5.3-nemo kernel seems to work

I did take a quick look at the board-rm680.c since there are some conditional statements with regards to system revision but I didn't notice anything that might prevent it from booting.

Quoted 2 lines

If you have
any ideas, let me know.

Last time I couldn't get output on serial I used CONFIG_DEBUG_LL, CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel earlyprintk kernel params to get output early enough - I guess you already tried that.

Quoted 4 lines · Filip Matijevi?

Last time I couldn't get output on serial I used CONFIG_DEBUG_LL, CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel earlyprintk kernel params to get output early enough - I guess you already tried that.

I realized I'm not getting output from the decompessor (even on "S" machine), and enabled that.

But I'm _still_ not getting any output on decompressor... early printing works ok on "S" but not on "P".

Quoted 6 lines · On Thursday 26 October 2017 09:08:15 Pavel Machek wrote:

Quoted 4 lines · Filip Matijevi?

Last time I couldn't get output on serial I used CONFIG_DEBUG_LL, CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel earlyprintk kernel params to get output early enough - I guess you already tried that.

Quoted 2 lines

I realized I'm not getting output from the decompessor (even on "S" machine), and enabled that.

That is because you have not enabled those EARLY PRINK or DEBUG LL. Similar thing is needed for N900 and IIRC in some of my linux-n900 branches I have config for it. Plus it needs patching some arch/arm source files to make it working.

Quoted 2 lines

But I'm _still_ not getting any output on decompressor... early printing works ok on "S" but not on "P".

I guess there can be either problem with memory mapping and RAM size or with OMAP HS mode?

Hi!

Quoted 10 lines · Pali Roh?r

Quoted 8 lines · On Thursday 26 October 2017 09:08:15 Pavel Machek wrote:

Quoted 4 lines · Filip Matijevi?

Last time I couldn't get output on serial I used CONFIG_DEBUG_LL, CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel earlyprintk kernel params to get output early enough - I guess you already tried that.

I realized I'm not getting output from the decompessor (even on "S" machine), and enabled that.

Quoted 4 lines

That is because you have not enabled those EARLY PRINK or DEBUG LL. Similar thing is needed for N900 and IIRC in some of my linux-n900 branches I have config for it. Plus it needs patching some arch/arm source files to make it working.

Do you have a patch? That would be very useful.

Seems like debugging in uncompressor was broken some time ago:

config DEBUG_UNCOMPRESS

        bool
		depends on ARCH_MULTIPLATFORM || PLAT_SAMSUNG ||         ARM_SINGLE_ARMV7M
	        default y if DEBUG_LL && !DEBUG_OMAP2PLUS_UART && 
		                     (!DEBUG_TEGRA_UART || !ZBOOT_ROM)
        && \!DEBUG_BRCMSTB_UART

Quoted 5 lines

Quoted 2 lines

But I'm _still_ not getting any output on decompressor... early printing works ok on "S" but not on "P".

I guess there can be either problem with memory mapping and RAM size or with OMAP HS mode?

RAM size should be ok... how do I check for OMAP HS problems?

Quoted 18 lines · On Thursday 26 October 2017 09:27:59 Pavel Machek wrote:

Hi!

Quoted 14 lines · Pali Roh?r

Quoted 8 lines · On Thursday 26 October 2017 09:08:15 Pavel Machek wrote:

Quoted 4 lines · Filip Matijevi?

Last time I couldn't get output on serial I used CONFIG_DEBUG_LL, CONFIG_DEBUG_OMAP3UART3, CONFIG_EARLY_PRINTK... and ignore_loglevel earlyprintk kernel params to get output early enough - I guess you already tried that.

I realized I'm not getting output from the decompessor (even on "S" machine), and enabled that.

That is because you have not enabled those EARLY PRINK or DEBUG LL. Similar thing is needed for N900 and IIRC in some of my linux-n900 branches I have config for it. Plus it needs patching some arch/arm source files to make it working.

Quoted 1 line

Do you have a patch? That would be very useful.

Yes, in v4.9-n900 branch, see:
https://github.com/pali/linux-n900/commit/66b22ba4132ca90f7efc3f9e8ece8d4b9adddcdc