imx28evk based board moving from fido to jethro stopped to fully boot

imx28evk based board moving from fido to jethro stopped to fully boot

[Ivan Sergio Borgonovo]

I've a board that just need a couple of patches to device tree compared 
to the imx28evk board:
- configuration of serial ports
- display timing

It was fully booting with fido (linux-fsl) and I was able to see the 
login prompt on the screen.

Now I see the penguin logo and no more login prompt.

While I wait to have a cable to connect a serial console this is the 
only information I can provide.

I was reading
http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.0-release

http://freescale.github.io/doc/release-notes/2.0/#known-issues

but nothing seems relevant unless the gcc problem is relevant for the 
current status of linux-fsl kernel (4.1).

Since my only changes to the imx28evk are related to dt and the screen 
does seem to work I'd be tempted to say the problem is elsewhere.
I had to adjust local.conf just to cope with a couple of changes in qt5 
and gstreamer, but software that shouldn't have any impact on boot.

Any clue that may help me to fix this while I wait for cable?
Has anyone tested imx28evk with jethro?


thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it

Re: imx28evk based board moving from fido to jethro stopped to fully boot

[justin chaise]

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

Hi, I am working with a board that is almost the same as the imx23evk, the
imx28evk sibling.
It seems that not all of our, MXS family, drivers were ported to the newer
kernels.
If fido booted and you saw a login on the lcd you may be in good shape.

When you see the penguin logo that is the bootloader, u-boot, initializing
the hardware.
If the screen goes away after that; linux is not using or initializing the
lcd. It may be using the serial port.
First I would check the linux kernel command line switches in your device
tree under chosen --> bootargs.
Compare that to the settings you used with fido (linux-fslc 3.18?)
Second check the boot arguments in u-boot. These settings will overwrite
the command line switches from your device tree.
I you can not type at the command line in u-boot, you can change the boot
arguments in the code then recompile u-boot
see (include/configs/mx28evk.h)
I hope this starts you in the right direction.

On Mon, Dec 14, 2015 at 3:34 AM, Ivan Sergio Borgonovo <mail@webthatworks.it
> wrote:

> I've a board that just need a couple of patches to device tree compared to
> the imx28evk board:
> - configuration of serial ports
> - display timing
>
> It was fully booting with fido (linux-fsl) and I was able to see the login
> prompt on the screen.
>
> Now I see the penguin logo and no more login prompt.
>
> While I wait to have a cable to connect a serial console this is the only
> information I can provide.
>
> I was reading
>
> http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.0-release
>
> http://freescale.github.io/doc/release-notes/2.0/#known-issues
>
> but nothing seems relevant unless the gcc problem is relevant for the
> current status of linux-fsl kernel (4.1).
>
> Since my only changes to the imx28evk are related to dt and the screen
> does seem to work I'd be tempted to say the problem is elsewhere.
> I had to adjust local.conf just to cope with a couple of changes in qt5
> and gstreamer, but software that shouldn't have any impact on boot.
>
> Any clue that may help me to fix this while I wait for cable?
> Has anyone tested imx28evk with jethro?
>
>
> thanks
>
> --
> Ivan Sergio Borgonovo
> http://www.webthatworks.it
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

[-- Attachment #2: Type: text/html, Size: 3426 bytes --]

Re: imx28evk based board moving from fido to jethro stopped to fully boot

[Ivan Sergio Borgonovo]

On 12/14/2015 03:08 PM, justin chaise wrote:
> Hi, I am working with a board that is almost the same as the imx23evk,
> the imx28evk sibling.
> It seems that not all of our, MXS family, drivers were ported to the
> newer kernels.
> If fido booted and you saw a login on the lcd you may be in good shape.
>
> When you see the penguin logo that is the bootloader, u-boot,
> initializing the hardware.
> If the screen goes away after that; linux is not using or initializing
> the lcd. It may be using the serial port.
> First I would check the linux kernel command line switches in your
> device tree under chosen --> bootargs.
> Compare that to the settings you used with fido (linux-fslc 3.18?)
> Second check the boot arguments in u-boot. These settings will overwrite
> the command line switches from your device tree.
> I you can not type at the command line in u-boot, you can change the
> boot arguments in the code then recompile u-boot
> see (include/configs/mx28evk.h)
> I hope this starts you in the right direction.

It is definitively a good starting but it is even more puzzling:
- if uboot version changed from fido to jethro... it seems it is still 
working since I can see the penguin logo
- the kernel didn't change. I'm using 4.1 in fido and jethro.

Anyway... I'll check in the direction you pointed.

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it

Re: imx28evk based board moving from fido to jethro stopped to fully boot

[justin chaise]

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

Before I assumed..
I should have asked what was the last thing you saw on your screen before
it went blank?

On Mon, Dec 14, 2015 at 8:08 AM, justin chaise <justinchaisejmc1@gmail.com>
wrote:

> Hi, I am working with a board that is almost the same as the imx23evk, the
> imx28evk sibling.
> It seems that not all of our, MXS family, drivers were ported to the newer
> kernels.
> If fido booted and you saw a login on the lcd you may be in good shape.
>
> When you see the penguin logo that is the bootloader, u-boot, initializing
> the hardware.
> If the screen goes away after that; linux is not using or initializing the
> lcd. It may be using the serial port.
> First I would check the linux kernel command line switches in your device
> tree under chosen --> bootargs.
> Compare that to the settings you used with fido (linux-fslc 3.18?)
> Second check the boot arguments in u-boot. These settings will overwrite
> the command line switches from your device tree.
> I you can not type at the command line in u-boot, you can change the boot
> arguments in the code then recompile u-boot
> see (include/configs/mx28evk.h)
> I hope this starts you in the right direction.
>
> On Mon, Dec 14, 2015 at 3:34 AM, Ivan Sergio Borgonovo <
> mail@webthatworks.it> wrote:
>
>> I've a board that just need a couple of patches to device tree compared
>> to the imx28evk board:
>> - configuration of serial ports
>> - display timing
>>
>> It was fully booting with fido (linux-fsl) and I was able to see the
>> login prompt on the screen.
>>
>> Now I see the penguin logo and no more login prompt.
>>
>> While I wait to have a cable to connect a serial console this is the only
>> information I can provide.
>>
>> I was reading
>>
>> http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.0-release
>>
>> http://freescale.github.io/doc/release-notes/2.0/#known-issues
>>
>> but nothing seems relevant unless the gcc problem is relevant for the
>> current status of linux-fsl kernel (4.1).
>>
>> Since my only changes to the imx28evk are related to dt and the screen
>> does seem to work I'd be tempted to say the problem is elsewhere.
>> I had to adjust local.conf just to cope with a couple of changes in qt5
>> and gstreamer, but software that shouldn't have any impact on boot.
>>
>> Any clue that may help me to fix this while I wait for cable?
>> Has anyone tested imx28evk with jethro?
>>
>>
>> thanks
>>
>> --
>> Ivan Sergio Borgonovo
>> http://www.webthatworks.it
>>
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>
>
>

[-- Attachment #2: Type: text/html, Size: 3960 bytes --]

Re: imx28evk based board moving from fido to jethro stopped to fully boot

[Ivan Sergio Borgonovo]

On 12/14/2015 03:14 PM, justin chaise wrote:
> Before I assumed..
> I should have asked what was the last thing you saw on your screen
> before it went blank?

It doesn't turn blank. I keep on seeing the penguin, but no login prompt.

Fido and jethro seems to use slightly different u-boot versions.
Recipes just seem to point to different versions, there are some patches 
but they are for different CPU.
A bit better for the kernel, same version but different git revision.

It will take me some time to get an idea how the recipes work and what 
are the differences between versions.

I'll have to check in the tmp/work dir.

Tomorrow there is a chance I'll get my serial cable and things may get 
easier.

Again has anyone succeed to boot an imx28evk based board?

thanks


> On Mon, Dec 14, 2015 at 8:08 AM, justin chaise
> <justinchaisejmc1@gmail.com <mailto:justinchaisejmc1@gmail.com>> wrote:
>
>     Hi, I am working with a board that is almost the same as the
>     imx23evk, the imx28evk sibling.
>     It seems that not all of our, MXS family, drivers were ported to the
>     newer kernels.
>     If fido booted and you saw a login on the lcd you may be in good shape.
>
>     When you see the penguin logo that is the bootloader, u-boot,
>     initializing the hardware.
>     If the screen goes away after that; linux is not using or
>     initializing the lcd. It may be using the serial port.
>     First I would check the linux kernel command line switches in your
>     device tree under chosen --> bootargs.
>     Compare that to the settings you used with fido (linux-fslc 3.18?)
>     Second check the boot arguments in u-boot. These settings will
>     overwrite the command line switches from your device tree.
>     I you can not type at the command line in u-boot, you can change the
>     boot arguments in the code then recompile u-boot
>     see (include/configs/mx28evk.h)
>     I hope this starts you in the right direction.
>
>     On Mon, Dec 14, 2015 at 3:34 AM, Ivan Sergio Borgonovo
>     <mail@webthatworks.it <mailto:mail@webthatworks.it>> wrote:
>
>         I've a board that just need a couple of patches to device tree
>         compared to the imx28evk board:
>         - configuration of serial ports
>         - display timing
>
>         It was fully booting with fido (linux-fsl) and I was able to see
>         the login prompt on the screen.
>
>         Now I see the penguin logo and no more login prompt.
>
>         While I wait to have a cable to connect a serial console this is
>         the only information I can provide.
>
>         I was reading
>         http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.0-release
>
>         http://freescale.github.io/doc/release-notes/2.0/#known-issues
>
>         but nothing seems relevant unless the gcc problem is relevant
>         for the current status of linux-fsl kernel (4.1).
>
>         Since my only changes to the imx28evk are related to dt and the
>         screen does seem to work I'd be tempted to say the problem is
>         elsewhere.
>         I had to adjust local.conf just to cope with a couple of changes
>         in qt5 and gstreamer, but software that shouldn't have any
>         impact on boot.
>
>         Any clue that may help me to fix this while I wait for cable?
>         Has anyone tested imx28evk with jethro?
>
>
>         thanks
>
>         --
>         Ivan Sergio Borgonovo
>         http://www.webthatworks.it
>
>         --
>         _______________________________________________
>         meta-freescale mailing list
>         meta-freescale@yoctoproject.org
>         <mailto:meta-freescale@yoctoproject.org>
>         https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
>

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it

Re: imx28evk based board moving from fido to jethro stopped to fully boot

[Fabio Estevam]

Hi Ivan,

On Mon, Dec 14, 2015 at 7:34 AM, Ivan Sergio Borgonovo
<mail@webthatworks.it> wrote:

> Any clue that may help me to fix this while I wait for cable?

Yes, you can direct the console output to the display and see where it
gets stuck.

In order to do so you can pass:

'console=tty0 console=ttyAMA0,115200' into your kernel command line.