Hi!
> > I'll fire up ELDK 5.4 + Pandaboard later today (which uses thumb) but I
> > think you need to bisect down to when exactly things break since my gut
> > is telling me it's not toolchain / thumb but something else that broke
> > things.
>
> Panda + ELDK 5.4, which sets CONFIG_SYS_THUMB_BUIL
On Wed, Apr 08, 2015 at 06:06:08PM +0200, Pavel Machek wrote:
> On Wed 2015-04-08 11:53:38, Tom Rini wrote:
> > On Wed, Apr 08, 2015 at 04:06:34PM +0200, Pavel Machek wrote:
> > > On Wed 2015-04-08 09:49:53, Tom Rini wrote:
> > > > On Wed, Apr 08, 2015 at 02:09:57PM +0200, Pavel Machek wrote:
> > >
On Wed, Apr 08, 2015 at 11:53:38AM -0400, Tom Rini wrote:
> On Wed, Apr 08, 2015 at 04:06:34PM +0200, Pavel Machek wrote:
> > On Wed 2015-04-08 09:49:53, Tom Rini wrote:
> > > On Wed, Apr 08, 2015 at 02:09:57PM +0200, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > >>maybe this helps? I just ste
On Wed 2015-04-08 11:53:38, Tom Rini wrote:
> On Wed, Apr 08, 2015 at 04:06:34PM +0200, Pavel Machek wrote:
> > On Wed 2015-04-08 09:49:53, Tom Rini wrote:
> > > On Wed, Apr 08, 2015 at 02:09:57PM +0200, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > > >>maybe this helps? I just stepped into same
On Wed, Apr 08, 2015 at 04:06:34PM +0200, Pavel Machek wrote:
> On Wed 2015-04-08 09:49:53, Tom Rini wrote:
> > On Wed, Apr 08, 2015 at 02:09:57PM +0200, Pavel Machek wrote:
> > > Hi!
> > >
> > > > >>maybe this helps? I just stepped into same problem on an am335x,
> > > > >>but had not yet time to
On Wed 2015-04-08 09:49:53, Tom Rini wrote:
> On Wed, Apr 08, 2015 at 02:09:57PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > >>maybe this helps? I just stepped into same problem on an am335x,
> > > >>but had not yet time to look deeper in it ...
> > > >
> > > >I did not try the cleanup_before_lin
On Wed 2015-04-08 15:13:27, Marek Vasut wrote:
> On Wednesday, April 08, 2015 at 02:09:57 PM, Pavel Machek wrote:
> > Hi!
> >
> > > >>maybe this helps? I just stepped into same problem on an am335x,
> > > >>but had not yet time to look deeper in it ...
> > > >
> > > >I did not try the cleanup_befo
On Wednesday, April 08, 2015 at 02:09:57 PM, Pavel Machek wrote:
> Hi!
>
> > >>maybe this helps? I just stepped into same problem on an am335x,
> > >>but had not yet time to look deeper in it ...
> > >
> > >I did not try the cleanup_before_linux(), but "dcache off" should have
> > >same effect, ri
On Wed, Apr 08, 2015 at 02:09:57PM +0200, Pavel Machek wrote:
> Hi!
>
> > >>maybe this helps? I just stepped into same problem on an am335x,
> > >>but had not yet time to look deeper in it ...
> > >
> > >I did not try the cleanup_before_linux(), but "dcache off" should have
> > >same effect, right
Hi!
> >>maybe this helps? I just stepped into same problem on an am335x,
> >>but had not yet time to look deeper in it ...
> >
> >I did not try the cleanup_before_linux(), but "dcache off" should have
> >same effect, right?
>
> Hmm.. not exactly... cleanup_before_linux() does also disable the mmu
Hello Pavel,
Am 07.04.2015 09:56, schrieb Pavel Machek:
Hi!
In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
hangs. (Usually, that's after "DRAM: " message).
Now, I have to admit I'm chainloading u-boot from
U-Boot 2013.01.01 (Mar 25 2015 - 15:57:21)
tftp 0x0140 .../u-bo
Hi!
> >In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
> >hangs. (Usually, that's after "DRAM: " message).
> >
> >Now, I have to admit I'm chainloading u-boot from
> >
> >U-Boot 2013.01.01 (Mar 25 2015 - 15:57:21)
> >
> >tftp 0x0140 .../u-boot.bin
> >Waiting for PHY auto negot
On Mon 2015-04-06 23:02:48, Marek Vasut wrote:
> On Monday, April 06, 2015 at 09:23:23 PM, Pavel Machek wrote:
> > On Mon 2015-04-06 20:48:45, Marek Vasut wrote:
> > > On Monday, April 06, 2015 at 08:14:44 PM, Pavel Machek wrote:
> > > > On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> > > > > On M
Hello Pavel,
Am 06.04.2015 16:40, schrieb Pavel Machek:
Hi!
In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
hangs. (Usually, that's after "DRAM: " message).
Now, I have to admit I'm chainloading u-boot from
U-Boot 2013.01.01 (Mar 25 2015 - 15:57:21)
tftp 0x0140 .../u-boo
On Monday, April 06, 2015 at 09:23:23 PM, Pavel Machek wrote:
> On Mon 2015-04-06 20:48:45, Marek Vasut wrote:
> > On Monday, April 06, 2015 at 08:14:44 PM, Pavel Machek wrote:
> > > On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> > > > On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
On Mon 2015-04-06 20:48:45, Marek Vasut wrote:
> On Monday, April 06, 2015 at 08:14:44 PM, Pavel Machek wrote:
> > On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> > > On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
> > > > Hi!
> > > >
> > > > In u-boot 2015.04-rc, as soon as executi
On Monday, April 06, 2015 at 08:14:44 PM, Pavel Machek wrote:
> On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> > On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
> > > Hi!
> > >
> > > In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
> > > hangs. (Usually, that's afte
On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
> > Hi!
> >
> > In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
> > hangs. (Usually, that's after "DRAM: " message).
>
> printf("%d") expects an argument, so could it be
On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
> Hi!
>
> In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
> hangs. (Usually, that's after "DRAM: " message).
printf("%d") expects an argument, so could it be that it touches
random piece of memory and thus hangs?
Best
Hi!
In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
hangs. (Usually, that's after "DRAM: " message).
Now, I have to admit I'm chainloading u-boot from
U-Boot 2013.01.01 (Mar 25 2015 - 15:57:21)
tftp 0x0140 .../u-boot.bin
Waiting for PHY auto negotiation to complete.. done
E
20 matches
Mail list logo
