* [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200
@ 2008-11-29 13:14 Linux RegaTech
2008-12-01 7:51 ` Mohamed Thalib .H
2008-12-01 10:34 ` Jean-Christophe PLAGNIOL-VILLARD
0 siblings, 2 replies; 4+ messages in thread
From: Linux RegaTech @ 2008-11-29 13:14 UTC (permalink / raw)
To: u-boot
Hello UBOOT mailinglist
I have encountered a problem when i try to compile any newer version of UBOOT than V1.2.0 for AT91RM9200,
below is given the output from console when i try to compile the UBOOT V1.3.4 for AT91RM9200,
could anybody please give me a hint what a solution to this problem might could be:
In file included from fdt_host.h:25,
from mkimage.h:36,
from mkimage.c:25:
../include/libfdt.h: In function `fdt_set_magic':
../include/libfdt.h:162: warning: implicit declaration of function `__cpu_to_be32'
In file included from mkimage.c:26:
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:202: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:224: error: parse error before '}' token
/home/Rene/uboot134/include/image.h:334: error: parse error before "image_get_data"
/home/Rene/uboot134/include/image.h: In function `image_get_data':
/home/Rene/uboot134/include/image.h:336: error: `ulong' undeclared (first use in this function)
/home/Rene/uboot134/include/image.h:336: error: (Each undeclared identifier is reported only once
/home/Rene/uboot134/include/image.h:336: error: for each function it appears in.)
/home/Rene/uboot134/include/image.h:336: error: parse error before "hdr"
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:343: error: parse error before "image_get_image_end"
/home/Rene/uboot134/include/image.h: In function `image_get_image_end':
/home/Rene/uboot134/include/image.h:345: error: `ulong' undeclared (first use in this function)
/home/Rene/uboot134/include/image.h:345: error: parse error before "hdr"
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:402: error: parse error before "image_multi_count"
/home/Rene/uboot134/include/image.h:403: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:477: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:479: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:493: error: parse error before "fit_get_size"
/home/Rene/uboot134/include/image.h:505: error: parse error before "fit_get_end"
/home/Rene/uboot134/include/image.h: In function `fit_get_end':
/home/Rene/uboot134/include/image.h:507: error: `ulong' undeclared (first use in this function)
/home/Rene/uboot134/include/image.h:507: error: parse error before "fit"
/home/Rene/uboot134/include/image.h: At top level:
/home/Rene/uboot134/include/image.h:532: error: parse error before "ulong"
/home/Rene/uboot134/include/image.h:533: error: parse error before "ulong"
make[1]: *** [mkimage.o] Error 1
make: *** [tools] Error 2
Thanks in advance.
Best regards
Ren?
^ permalink raw reply [flat|nested] 4+ messages in thread* [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200
2008-11-29 13:14 [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200 Linux RegaTech
@ 2008-12-01 7:51 ` Mohamed Thalib .H
2008-12-01 10:34 ` Jean-Christophe PLAGNIOL-VILLARD
1 sibling, 0 replies; 4+ messages in thread
From: Mohamed Thalib .H @ 2008-12-01 7:51 UTC (permalink / raw)
To: u-boot
On Sat, 2008-11-29 at 14:14 +0100, Linux RegaTech wrote:
> Hello UBOOT mailinglist
>
> I have encountered a problem when i try to compile any newer version of UBOOT than V1.2.0 for AT91RM9200,
> below is given the output from console when i try to compile the UBOOT V1.3.4 for AT91RM9200,
> could anybody please give me a hint what a solution to this problem might could be:
>
> In file included from fdt_host.h:25,
> from mkimage.h:36,
> from mkimage.c:25:
> ../include/libfdt.h: In function `fdt_set_magic':
> ../include/libfdt.h:162: warning: implicit declaration of function `__cpu_to_be32'
> In file included from mkimage.c:26:
> /home/Rene/uboot134/include/image.h: At top level:
> /home/Rene/uboot134/include/image.h:202: error: parse error before "ulong"
> /home/Rene/uboot134/include/image.h:224: error: parse error before '}' token
> /home/Rene/uboot134/include/image.h:334: error: parse error before "image_get_data"
> /home/Rene/uboot134/include/image.h: In function `image_get_data':
> /home/Rene/uboot134/include/image.h:336: error: `ulong' undeclared (first use in this function)
> /home/Rene/uboot134/include/image.h:336: error: (Each undeclared identifier is reported only once
> /home/Rene/uboot134/include/image.h:336: error: for each function it appears in.)
> /home/Rene/uboot134/include/image.h:336: error: parse error before "hdr"
> /home/Rene/uboot134/include/image.h: At top level:
> /home/Rene/uboot134/include/image.h:343: error: parse error before "image_get_image_end"
> /home/Rene/uboot134/include/image.h: In function `image_get_image_end':
> /home/Rene/uboot134/include/image.h:345: error: `ulong' undeclared (first use in this function)
> /home/Rene/uboot134/include/image.h:345: error: parse error before "hdr"
> /home/Rene/uboot134/include/image.h: At top level:
> /home/Rene/uboot134/include/image.h:402: error: parse error before "image_multi_count"
> /home/Rene/uboot134/include/image.h:403: error: parse error before "ulong"
> /home/Rene/uboot134/include/image.h:477: error: parse error before "ulong"
> /home/Rene/uboot134/include/image.h:479: error: parse error before "ulong"
> /home/Rene/uboot134/include/image.h:493: error: parse error before "fit_get_size"
> /home/Rene/uboot134/include/image.h:505: error: parse error before "fit_get_end"
> /home/Rene/uboot134/include/image.h: In function `fit_get_end':
> /home/Rene/uboot134/include/image.h:507: error: `ulong' undeclared (first use in this function)
> /home/Rene/uboot134/include/image.h:507: error: parse error before "fit"
> /home/Rene/uboot134/include/image.h: At top level:
> /home/Rene/uboot134/include/image.h:532: error: parse error before "ulong"
> /home/Rene/uboot134/include/image.h:533: error: parse error before "ulong"
> make[1]: *** [mkimage.o] Error 1
> make: *** [tools] Error 2
>
> Thanks in advance.
> Best regards
> Ren?
> _______________________________________________ U-Boot mailing list U-Boot at lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot\
I think some file inclusion is missing try to inclue it.. the typedef of
ulong is in include/linux/types.h
--
Regards,
Mohamed Thalib .H
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200
2008-11-29 13:14 [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200 Linux RegaTech
2008-12-01 7:51 ` Mohamed Thalib .H
@ 2008-12-01 10:34 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-01 12:59 ` [U-Boot] Uboot AS Space in MPC85xx Start.S Vignesh Kumar B
1 sibling, 1 reply; 4+ messages in thread
From: Jean-Christophe PLAGNIOL-VILLARD @ 2008-12-01 10:34 UTC (permalink / raw)
To: u-boot
On 14:14 Sat 29 Nov , Linux RegaTech wrote:
> Hello UBOOT mailinglist
>
> I have encountered a problem when i try to compile any newer version of UBOOT than V1.2.0 for AT91RM9200,
> below is given the output from console when i try to compile the UBOOT V1.3.4 for AT91RM9200,
> could anybody please give me a hint what a solution to this problem might could be:
please use the last release or the rc
I've test it yesterday
Best Regards,
J.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Uboot AS Space in MPC85xx Start.S
2008-12-01 10:34 ` Jean-Christophe PLAGNIOL-VILLARD
@ 2008-12-01 12:59 ` Vignesh Kumar B
0 siblings, 0 replies; 4+ messages in thread
From: Vignesh Kumar B @ 2008-12-01 12:59 UTC (permalink / raw)
To: u-boot
Hi,
I am working on the Start.S in the Bootloader code for MPC8572. I find
that At some point of time we say we switch to AS=1 when setting TLB.
After cpu_early_init_f we switch back to AS=0. So we do this to avoid
some mismatch. But when we shift back to AS=0, I want to know what is
there in that Address Space 0. Can some one help me on this. Suppose I
am modifying the code of u-boot into just one function board_init_f
without the previous call then what operations should be done on AS=0
and AS=1.
Let me know.
Actual Code Snippet:
bl cpu_init_early_f ---> This is happening in AS
= 1
/* switch back to AS = 0 */
lis r3,(MSR_CE|MSR_ME|MSR_DE)@h
ori r3,r3,(MSR_CE|MSR_ME|MSR_DE)@l
mtmsr r3
isync
bl cpu_init_f ---> This is happening in AS = 0
bl board_init_f
isync
My Code :
#AS=1
TLB Mapping
..
..
..
#switch back to AS = 0
lis %r3,(MSR_CE|MSR_ME|MSR_DE)@h
ori %r3,%r3,(MSR_CE|MSR_ME|MSR_DE)@l
mtmsr %r3
isync
bl main # Jump to main() for board & cpu init
Thanks & Regards,
Vignesh Kumar B
DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.
-----------------------------------------------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-12-01 12:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-29 13:14 [U-Boot] Error compiling UBOOT 1.3.4 for AT91RM9200 Linux RegaTech
2008-12-01 7:51 ` Mohamed Thalib .H
2008-12-01 10:34 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-01 12:59 ` [U-Boot] Uboot AS Space in MPC85xx Start.S Vignesh Kumar B
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox