Jocke,
>> ok - works for me, i.e. no quad-nop needed anymore.
>>
> Does both your boards work now?
>
MPC8343 @ 400MHz never had any issues - it's still working with your
patch applied.
MPC8377 works fine up to 533MHz ... 600MHz+ still hangs.
Looks like there are more sync missing.
>>
Andre Schwarz wrote on 2010/11/04 15:49:06:
>
> Jocke,
>
> >> CPU: e300c4, MPC8379, Rev: 2.1 at 600 MHz, CSB: 400 MHz
> >>
> >> - Boot from NOR Flash
> >> - HRCW from I2C EEPROM
> >> - Reset Vector 0x100, i.e. low boot.
> >>
> > OK, almost the same as me, but I got a:
> > CPU: e300c2, MPC8321,
Jocke,
>> CPU: e300c4, MPC8379, Rev: 2.1 at 600 MHz, CSB: 400 MHz
>>
>> - Boot from NOR Flash
>> - HRCW from I2C EEPROM
>> - Reset Vector 0x100, i.e. low boot.
>>
> OK, almost the same as me, but I got a:
> CPU: e300c2, MPC8321, Rev: 1.1 at 266.664 MHz, CSB: 133.332 MHz
>
> However, I th
Andre Schwarz wrote on 2010/11/04 14:32:15:
>
> Jocke,
>
> [snip]
>
> > still -E_TOO_LITTLE_INFO:
> >
>
> sorry - thought it was clear already.
>
> > "include weather booted from NAND or NOR, CPU type(e300cX) and
> > what reset vector is used."
> >
> CPU: e300c4, MPC8379, Rev: 2.1 at 600 MHz,
Jocke,
[snip]
> still -E_TOO_LITTLE_INFO:
>
sorry - thought it was clear already.
> "include weather booted from NAND or NOR, CPU type(e300cX) and
> what reset vector is used."
>
CPU: e300c4, MPC8379, Rev: 2.1 at 600 MHz, CSB: 400 MHz
- Boot from NOR Flash
- HRCW from I2C EEPROM
-
Wolfgang Denk wrote on 2010/11/04 14:07:50:
>
> Dear Joakim Tjernlund,
>
> In message
> you
> wrote:
> >
> > > Could do what? Modify the memory map such that the Flash is mapped
> >
> > Issue an soft reset somehow. Don't know how but I guessing it is possible?
> > If so the CPU would use reset
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > Could do what? Modify the memory map such that the Flash is mapped
>
> Issue an soft reset somehow. Don't know how but I guessing it is possible?
> If so the CPU would use reset vector 0x110 instead of 0x100(still guessing
> here)
I wonder
Andre Schwarz wrote on 2010/11/04 13:28:27:
>
>
> >> Andy,
> >>
> Sure, but until freescale or someone else with eq. and motivation
> researches it, we are stuck. I am not sure anyone else has tried
> 83xx based boards yet. If someone has please report. Also
> include weather b
Wolfgang Denk wrote on 2010/11/04 13:46:17:
>
> Dear Joakim Tjernlund,
>
> In message
> you
> wrote:
> >
> > > What exactly is a "soft reset" in U-Boot? And how would you perform
> > > one?
> >
> > Not in u-boot, but Linux or a privileged linux app. could.
>
> Could do what? Modify the memory
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > What exactly is a "soft reset" in U-Boot? And how would you perform
> > one?
>
> Not in u-boot, but Linux or a privileged linux app. could.
Could do what? Modify the memory map such that the Flash is mapped
as it was (eventually) when U-Boo
>> Andy,
>>
Sure, but until freescale or someone else with eq. and motivation
researches it, we are stuck. I am not sure anyone else has tried
83xx based boards yet. If someone has please report. Also
include weather booted from NAND or NOR, CPU type(e300cX) and
what
Wolfgang Denk wrote on 2010/11/04 12:16:31:
>
> Dear Joakim Tjernlund,
>
> In message
> you
> wrote:
> >
> > hmm, what if a board decides to do a soft reset anyway, perhaps by mistake.
> > Would it not be a good thing if u-boot could handle that too?
>
> What exactly is a "soft reset" in U-Boot
Andre Schwarz wrote on 2010/11/04 13:14:37:
>
> Andy,
> >> Sure, but until freescale or someone else with eq. and motivation
> >> researches it, we are stuck. I am not sure anyone else has tried
> >> 83xx based boards yet. If someone has please report. Also
> >> include weather booted from NAND or
Andy,
>> Sure, but until freescale or someone else with eq. and motivation
>> researches it, we are stuck. I am not sure anyone else has tried
>> 83xx based boards yet. If someone has please report. Also
>> include weather booted from NAND or NOR, CPU type(e300cX) and
>> what reset vector is used.
Dear Joakim Tjernlund,
In message
you
wrote:
>
> hmm, what if a board decides to do a soft reset anyway, perhaps by mistake.
> Would it not be a good thing if u-boot could handle that too?
What exactly is a "soft reset" in U-Boot? And how would you perform
one?
Best regards,
Wolfgang Denk
Joakim wrote...
> Sure, but until freescale or someone else with eq. and motivation
> researches it, we are stuck. I am not sure anyone else has tried
> 83xx based boards yet. If someone has please report. Also
> include weather booted from NAND or NOR, CPU type(e300cX) and
> what reset vector is
"Andy Pont" wrote on 2010/11/04 11:58:19:
>
> Joakim wrote...
>
> > Sure, but until freescale or someone else with eq. and motivation
> > researches it, we are stuck. I am not sure anyone else has tried
> > 83xx based boards yet. If someone has please report. Also
> > include weather booted from N
Dear Joakim Tjernlund schrieb:
> no, the nops has to be directly after _start:
> . = EXC_OFF_SYS_RESET
>
> .globl _start
> _start: /* time t 0 */
> nop
> nop
> nop
> nop
>
> My theory is that e300c2(no FPU) CPUs configured for low
> boot vector, 0x100, really
>
> Wolfgang Denk wrote on 2010/11/04 10:57:42:
> >
> > Dear Joakim Tjernlund,
> >
> > In message
> >
> > you wrote:
> > >
> > > > 4 nops after _start does the trick, i.e. the board is up and running
> > > > fine.
> > ...
> > > How is this going? If nothing else I think you should send
> > > a
Wolfgang Denk wrote on 2010/11/04 10:57:42:
>
> Dear Joakim Tjernlund,
>
> In message
> you
> wrote:
> >
> > > 4 nops after _start does the trick, i.e. the board is up and running fine.
> ...
> > How is this going? If nothing else I think you should send
> > a patch for 83xx, adding the 4 nop's
Wolfgang Denk wrote on 2010/11/04 10:50:38:
>
> Dear Andre Schwarz,
>
> In message <4cc58b1b.8040...@matrix-vision.de> you wrote:
> >
> > Diffing both System.maps and U-Boot hexdump gives only trivial results :
> >
> > - "in_flash" and "_start_of_vectors" adress increment = 0x10.
>
> Hey, stop her
Jocke,
[snip]
>> finally I got both some time and hardware :
>>
>> 4 nops after _start does the trick, i.e. the board is up and running fine.
>>
>>
>> Diffing both System.maps and U-Boot hexdump gives only trivial results :
>>
>> - "in_flash" and "_start_of_vectors" adress increment = 0x10.
>> - o
Dear Joakim Tjernlund,
In message
you
wrote:
>
> > 4 nops after _start does the trick, i.e. the board is up and running fine.
...
> How is this going? If nothing else I think you should send
> a patch for 83xx, adding the 4 nop's as your(and mine) board is
> broken otherwise. Freescale guys see
Dear Andre Schwarz,
In message <4cc58b1b.8040...@matrix-vision.de> you wrote:
>
> Diffing both System.maps and U-Boot hexdump gives only trivial results :
>
> - "in_flash" and "_start_of_vectors" adress increment = 0x10.
Hey, stop here.
How can _start_of_vectors shift? It i supposed to be at a
Andre Schwarz wrote on 2010/10/25 15:50:19:
>
> Jocke,
>
> [snip]
>
> > You still haven't reported weather the 4 nop's helped or not, yet you
> > seek my help. I am just going to ignore you until you do test it.
> >
> >
>
> finally I got both some time and hardware :
>
> 4 nops after _start does t
Andre Schwarz wrote on 2010/10/26 14:34:57:
>
> All,
>
> >
> >> Having a look at include/asm/global_data.h gives some 40 ulongs for my
> >> MPC8377 system.
> >> Current CONFIG_SYS_GBL_DATA_SIZE= 0x100 which should be enough.
> >>
> > Indeed. I was asking because I just discovered that most of the
All,
>
>> Having a look at include/asm/global_data.h gives some 40 ulongs for my
>> MPC8377 system.
>> Current CONFIG_SYS_GBL_DATA_SIZE= 0x100 which should be enough.
>>
> Indeed. I was asking because I just discovered that most of the
> PowerPC boards are actually broken in this respect - 8
Wolfgang,
> Dear Andre Schwarz,
>
> In message<4cc5c226.8080...@matrix-vision.de> you wrote:
>
>> Having a look at include/asm/global_data.h gives some 40 ulongs for my
>> MPC8377 system.
>> Current CONFIG_SYS_GBL_DATA_SIZE= 0x100 which should be enough.
>>
> Indeed. I was asking because
Dear Andre Schwarz,
In message <4cc5c226.8080...@matrix-vision.de> you wrote:
>
> Having a look at include/asm/global_data.h gives some 40 ulongs for my
> MPC8377 system.
> Current CONFIG_SYS_GBL_DATA_SIZE= 0x100 which should be enough.
Indeed. I was asking because I just discovered that most of
Wolfgang,
> Dear Andre Schwarz,
>
> In message<4cc58b1b.8040...@matrix-vision.de> you wrote:
>
>> finally I got both some time and hardware :
>>
>> 4 nops after _start does the trick, i.e. the board is up and running fine.
>>
> This is probably completely unrelated - but check your
> CON
Dear Andre Schwarz,
In message <4cc58b1b.8040...@matrix-vision.de> you wrote:
>
> finally I got both some time and hardware :
>
> 4 nops after _start does the trick, i.e. the board is up and running fine.
This is probably completely unrelated - but check your
CONFIG_SYS_GBL_DATA_SIZE setting an
Andre Schwarz wrote on 2010/10/25 16:46:42:
>
> Jocke,
>
> > Andre Schwarz wrote on 2010/10/25 15:50:19:
> >
> >> Jocke,
> >>
> >> [snip]
> >>
> >>
> >>> You still haven't reported weather the 4 nop's helped or not, yet you
> >>> seek my help. I am just going to ignore you until you do test it.
>
Jocke,
> Andre Schwarz wrote on 2010/10/25 15:50:19:
>
>> Jocke,
>>
>> [snip]
>>
>>
>>> You still haven't reported weather the 4 nop's helped or not, yet you
>>> seek my help. I am just going to ignore you until you do test it.
>>>
>>>
>>>
>> finally I got both some time and har
Andre Schwarz wrote on 2010/10/25 15:50:19:
>
> Jocke,
>
> [snip]
>
> > You still haven't reported weather the 4 nop's helped or not, yet you
> > seek my help. I am just going to ignore you until you do test it.
> >
> >
>
> finally I got both some time and hardware :
>
> 4 nops after _start does t
Jocke,
[snip]
> You still haven't reported weather the 4 nop's helped or not, yet you
> seek my help. I am just going to ignore you until you do test it.
>
>
finally I got both some time and hardware :
4 nops after _start does the trick, i.e. the board is up and running fine.
Diffing both Sys
Jocke,
[snip]
> > You still haven't reported weather the 4 nop's helped or not, yet you
> seek my help. I am just going to ignore you until you do test it.
of course.
Will give it a try as soon as I'll be back to office and have a board at hand
...
Just wanted to collect some more feedback.
"Schwarz,Andre" wrote on 2010/10/24 22:33:44:
>
> Wolfgang,
>
> Wolfgang Denk hat am 24. Oktober 2010 um 22:18 geschrieben:
>
> > Dear "Schwarz,Andre",
> >
> > In message <1702240919.111.1287950899754.javamail.open-xcha...@proteus> you
> > wrote:
> > >
> > > Since I assume Wolfgang won't accept
Wolfgang Denk wrote on 2010/10/24 22:18:32:
>
> Dear "Schwarz,Andre",
>
> In message <1702240919.111.1287950899754.javamail.open-xcha...@proteus> you
> wrote:
> >
> > Since I assume Wolfgang won't accept a board specific "add 4 nops after
> > _start"-patch I'd like to solve this without trial and
Wolfgang,
Wolfgang Denk hat am 24. Oktober 2010 um 22:18 geschrieben:
> Dear "Schwarz,Andre",
>
> In message <1702240919.111.1287950899754.javamail.open-xcha...@proteus> you
> wrote:
> >
> > Since I assume Wolfgang won't accept a board specific "add 4 nops after
> > _start"-patch I'd like to s
Dear "Schwarz,Andre",
In message <1702240919.111.1287950899754.javamail.open-xcha...@proteus> you
wrote:
>
> Since I assume Wolfgang won't accept a board specific "add 4 nops after
> _start"-patch I'd like to solve this without trial and error.
To the best of my knowledge no board made use f thi
All,
Wolfgang Denk hat am 18. Oktober 2010 um 22:39 geschrieben:
> Dear Joakim Tjernlund,
>
> In message <1287049904-18917-1-git-send-email-joakim.tjernl...@transmode.se>
> you wrote:
> > The fixup routine must not fixup NULL pointers.
> > Problem can be seen by
> > char *testfun(void) __attr
Dear Joakim Tjernlund,
In message <1287049904-18917-1-git-send-email-joakim.tjernl...@transmode.se>
you wrote:
> The fixup routine must not fixup NULL pointers.
> Problem can be seen by
> char *testfun(void) __attribute__((weak));
> char *(*myfun)(void) = testfun;
>
> Then add
> printf("myfu
The fixup routine must not fixup NULL pointers.
Problem can be seen by
char *testfun(void) __attribute__((weak));
char *(*myfun)(void) = testfun;
Then add
printf("myfun:%p, &myfun:%p\n", myfun, &myfun);
before relocation and after relocation.
myfun should be NULL in both cases but it is not.
43 matches
Mail list logo
