debugging on board

debugging on board

[Gabriel Tisan]

Hi !

What should I do to be able to see any debug messages ? On the serial console I
could see the Barebox version but after that nothing. I suppose that
is something
regarding nand.

If I have no JTAG debugger what should I do to be able to debug ? For
other board I
could not see any messages on console.

Regards,
Gabriel

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Sascha Hauer]

Hi Gabriel,

On Thu, Apr 05, 2012 at 08:11:47AM +0200, Gabriel Tisan wrote:
> Hi !
> 
> What should I do to be able to see any debug messages ? On the serial console I
> could see the Barebox version but after that nothing. I suppose that
> is something
> regarding nand.

This means that your console is already running, a first step can then
be to put a '#define DEBUG' above the includes in common/startup.c. This
will cause the initcalls to be printed which will give you a first clue
where execution stops.

Also you should have the following options enabled:

CONFIG_MMU
ARM_EXCEPTIONS
CONFIG_ARM_UNWIND
CONFIG_KALLSYMS

This gives you a stack dump when something bad happens.

> 
> If I have no JTAG debugger what should I do to be able to debug ? For
> other board I
> could not see any messages on console.

That's more difficult. If you have for example a U-Boot as first stage
loader then you can add some register writes to the UART send register
in the early startup code. Otherwise you are stuck with LED debugging
(Just configure a gpio connected to a LED and see where you can still
turn it on)

What machine are you working on?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Gabriel Tisan]

Thanks !

I have an ARM from Freescale, i.MX35.

Regards,
Gabriel


On Thu, Apr 5, 2012 at 8:33 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Gabriel,
>
> On Thu, Apr 05, 2012 at 08:11:47AM +0200, Gabriel Tisan wrote:
>> Hi !
>>
>> What should I do to be able to see any debug messages ? On the serial console I
>> could see the Barebox version but after that nothing. I suppose that
>> is something
>> regarding nand.
>
> This means that your console is already running, a first step can then
> be to put a '#define DEBUG' above the includes in common/startup.c. This
> will cause the initcalls to be printed which will give you a first clue
> where execution stops.
>
> Also you should have the following options enabled:
>
> CONFIG_MMU
> ARM_EXCEPTIONS
> CONFIG_ARM_UNWIND
> CONFIG_KALLSYMS
>
> This gives you a stack dump when something bad happens.
>
>>
>> If I have no JTAG debugger what should I do to be able to debug ? For
>> other board I
>> could not see any messages on console.
>
> That's more difficult. If you have for example a U-Boot as first stage
> loader then you can add some register writes to the UART send register
> in the early startup code. Otherwise you are stuck with LED debugging
> (Just configure a gpio connected to a LED and see where you can still
> turn it on)
>
> What machine are you working on?
>
> Sascha
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Sascha Hauer]

On Thu, Apr 05, 2012 at 08:43:12AM +0200, Gabriel Tisan wrote:
> Thanks !
> 
> I have an ARM from Freescale, i.MX35.

Booting from SD card? Internal or external boot mode?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Gabriel Tisan]

I use external boot mode from NAND. I choosed
CONFIG_NAND_IMX_BOOT_512_2K although I have a flash with 2k page size.

On Thu, Apr 5, 2012 at 8:54 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Thu, Apr 05, 2012 at 08:43:12AM +0200, Gabriel Tisan wrote:
>> Thanks !
>>
>> I have an ARM from Freescale, i.MX35.
>
> Booting from SD card? Internal or external boot mode?
>
> Sascha
>
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Sascha Hauer]

On Thu, Apr 05, 2012 at 09:06:30AM +0200, Gabriel Tisan wrote:
> I use external boot mode from NAND. I choosed
> CONFIG_NAND_IMX_BOOT_512_2K although I have a flash with 2k page size.

Try 'make barebox.S' and have a look at the resulting barebox.S file.
Everything including

reset
__mmu_cache_flush
imx_nand_load_image

must fit into the first 2k of memory. We currently do not catch this
(though we could using a seperate linker section for this). If your
lowlevel init code is too big then you can easily exceed this
limitation.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Gabriel Tisan]

So, the opcodes from the start of the file barebox.S until
__mmu_cache_flush(inclusive) including
reset & imx_nand_load_image make 1372 bytes, lower than 2K.

Regards,
Gabriel

On Thu, Apr 5, 2012 at 11:27 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Thu, Apr 05, 2012 at 09:06:30AM +0200, Gabriel Tisan wrote:
>> I use external boot mode from NAND. I choosed
>> CONFIG_NAND_IMX_BOOT_512_2K although I have a flash with 2k page size.
>
> Try 'make barebox.S' and have a look at the resulting barebox.S file.
> Everything including
>
> reset
> __mmu_cache_flush
> imx_nand_load_image
>
> must fit into the first 2k of memory. We currently do not catch this
> (though we could using a seperate linker section for this). If your
> lowlevel init code is too big then you can easily exceed this
> limitation.
>
> Sascha
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Sascha Hauer]

On Thu, Apr 05, 2012 at 02:28:58PM +0200, Gabriel Tisan wrote:
> So, the opcodes from the start of the file barebox.S until
> __mmu_cache_flush(inclusive) including
> reset & imx_nand_load_image make 1372 bytes, lower than 2K.

So far for the obvious possibilities. Sorry, I can't give you any
further general advices, except the one I already have given: Look for a
gpio and try to set it from different locations and see if you get there
or not.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Jean-Christophe PLAGNIOL-VILLARD]

On 11:27 Thu 05 Apr     , Sascha Hauer wrote:
> On Thu, Apr 05, 2012 at 09:06:30AM +0200, Gabriel Tisan wrote:
> > I use external boot mode from NAND. I choosed
> > CONFIG_NAND_IMX_BOOT_512_2K although I have a flash with 2k page size.
> 
> Try 'make barebox.S' and have a look at the resulting barebox.S file.
> Everything including
> 
> reset
> __mmu_cache_flush
> imx_nand_load_image
> 
> must fit into the first 2k of memory. We currently do not catch this
> (though we could using a seperate linker section for this). If your
> lowlevel init code is too big then you can easily exceed this
> limitation.
we can now I add an option for this

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Gabriel Tisan]

On Fri, Apr 6, 2012 at 4:59 AM, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@jcrosoft.com> wrote:
> On 11:27 Thu 05 Apr     , Sascha Hauer wrote:
>> On Thu, Apr 05, 2012 at 09:06:30AM +0200, Gabriel Tisan wrote:
>> > I use external boot mode from NAND. I choosed
>> > CONFIG_NAND_IMX_BOOT_512_2K although I have a flash with 2k page size.
>>
>> Try 'make barebox.S' and have a look at the resulting barebox.S file.
>> Everything including
>>
>> reset
>> __mmu_cache_flush
>> imx_nand_load_image
>>
>> must fit into the first 2k of memory. We currently do not catch this
>> (though we could using a seperate linker section for this). If your
>> lowlevel init code is too big then you can easily exceed this
>> limitation.
> we can now I add an option for this
>
Which commit include this option ?

Actually which is the last stable barebox ? I've got the version from
master with last commit 96a43ca "pxa27x_udc: Fix compilation warning"
from 23 Mar 2012.

Regards,
Gabriel

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: debugging on board

[Jean-Christophe PLAGNIOL-VILLARD]

On 17:08 Wed 25 Apr     , Gabriel Tisan wrote:
> On Fri, Apr 6, 2012 at 4:59 AM, Jean-Christophe PLAGNIOL-VILLARD
> <plagnioj@jcrosoft.com> wrote:
> > On 11:27 Thu 05 Apr     , Sascha Hauer wrote:
> >> On Thu, Apr 05, 2012 at 09:06:30AM +0200, Gabriel Tisan wrote:
> >> > I use external boot mode from NAND. I choosed
> >> > CONFIG_NAND_IMX_BOOT_512_2K although I have a flash with 2k page size.
> >>
> >> Try 'make barebox.S' and have a look at the resulting barebox.S file.
> >> Everything including
> >>
> >> reset
> >> __mmu_cache_flush
> >> imx_nand_load_image
> >>
> >> must fit into the first 2k of memory. We currently do not catch this
> >> (though we could using a seperate linker section for this). If your
> >> lowlevel init code is too big then you can easily exceed this
> >> limitation.
> > we can now I add an option for this
> >
> Which commit include this option ?
> 
> Actually which is the last stable barebox ? I've got the version from
> master with last commit 96a43ca "pxa27x_udc: Fix compilation warning"
> from 23 Mar 2012.
you need to check the commits that put the bare_init size and if you can not
use it do simthing similar for the pre_image

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox