|
Vignesh Kumar Bagavathsingh
|
|
|
Vignesh Kumar Bagavathsingh
11/17/2008 8:57 AM
post16648
|
Hi I am involved in developing IPL for 8568. When I use the tlbre and tlbwe asm commands, i get an error "Error:
Unrecognized opcode: `tlbwe' " , " Error: Unrecognized opcode: `tlbre' ". What has to be done to fix this issue. I tried
to compile using the IDE 6.3.2 as well as IDE 6.4.0. I get the same bug. Please let me know.
Thanks and Regards,
Vignesh Kumar
|
|
|
|
|
|
Ryan Mansfield(deleted)
11/17/2008 9:07 AM
post16652
|
Vignesh Kumar Bagavathsingh wrote:
> Hi I am involved in developing IPL for 8568. When I use the tlbre and tlbwe asm commands, i get an error "Error:
Unrecognized opcode: `tlbwe' " , " Error: Unrecognized opcode: `tlbre' ". What has to be done to fix this issue. I tried
to compile using the IDE 6.3.2 as well as IDE 6.4.0. I get the same bug. Please let me know.
Specify -mbooke to the assembler or -Wa,-mbooke to qcc.
Regards,
Ryan Mansfield
|
|
|
|
|
|
Vignesh Kumar Bagavathsingh
|
|
|
Vignesh Kumar Bagavathsingh
11/17/2008 9:28 AM
post16657
|
Hi Ryan,
Thanks for the reply. Can you tell exactly where I should insert those option in the IDE.
If it is in IDE the options are to placed in common.mk. I am puting it here can u tell me where exactly.
Please help me.
Thanks
#
# General purpose makefile for building a Neutrino IPL
#
ifndef QCONFIG
QCONFIG=qconfig.mk
endif
include $(QCONFIG)
LIB_VARIANT=$(subst .o,,a.$(COMPOUND_VARIANT))
#===== INSTALLDIR - Subdirectory where the executable or library is to be installed.
INSTALLDIR=boot/sys
#===== LIBS - a space-separated list of library items to be included in the link.
LIBS=ipl
#===== NAME - name of the project (default - name of project directory).
NAME=ipl-cpusub
#===== USEFILE - the file containing the usage message for the application.
USEFILE=
#===== EXTRA_INCVPATH - a space-separated list of directories to search for include files.
EXTRA_INCVPATH=$(LIBIPL_ROOT)/$(CPU)/$(LIB_VARIANT) \
$(LIBIPL_ROOT)/$(CPU) $(LIBIPL_ROOT) \
$(PROJECT_ROOT)/../bsp-freescale-cdsmpc8568_prebuilt/usr/include
#===== EXTRA_LIBVPATH - a space-separated list of directories to search for library files.
EXTRA_LIBVPATH=$(LIBIPL_ROOT)/$(CPU)/$(LIB_VARIANT) \
$(PROJECT_ROOT)/../bsp-freescale-cdsmpc8568_prebuilt/$(CPUDIR)/lib \
$(PROJECT_ROOT)/../bsp-freescale-cdsmpc8568_prebuilt/$(CPUDIR)/usr/lib
## DEFFILE = $(LIBIPL_ROOT)/$(CPU)/$(LIB_VARIANT)/asmoff.def
LDF_+=-nostartfiles \
-T$(PROJECT_ROOT)/$(SECTION)/$(SECTION).lnk
LDF_qcc+=-M -nostartup \
-Wl -T$(PROJECT_ROOT)/$(SECTION)/$(SECTION).lnk
#===== LDFLAGS - add the flags to the linker command line.
LDFLAGS+=$(LDF_$(COMPILER_DRIVER)) -nostdlib
include $(MKFILES_ROOT)/qmacros.mk
-include $(PROJECT_ROOT)/roots.mk
ifndef LIBIPL_ROOT
LIBIPL_ROOT=$(PRODUCT_ROOT)/lib
endif
include $(PROJECT_ROOT)/$(SECTION)/pinfo.mk
# Don't try to add usage messages to ipl's.
define ADD_USAGE
endef
#
# Make sure *_reset.o gets linked _first_.
#
old_OBJS:=$(OBJS)
OBJS:=$(filter %_reset.o, $(old_OBJS)) \
$(filter-out %_reset.o, $(old_OBJS))
include $(QNX_INTERNAL)
include $(MKFILES_ROOT)/qtargets.mk
CCF_gcc_=-O2 -fomit-frame-pointer
CCF_gcc_qcc=-O2 -Wc,-fomit-frame-pointer
#===== CCFLAGS - add the flags to the C compiler command line.
CCFLAGS+=$(CCFLAGS_$(COMPILER_TYPE)_$(COMPILER_DRIVER))
#
# This particular little kludge is to stop GCC from using F.P. instructions
# to move 8 byte quantities around.
#
CC_nto_ppc_gcc+=-msoft-float
CC_nto_ppc_gcc_qcc+=-Wc,-msoft-float
|
|
|
|
|
|
Ryan Mansfield(deleted)
11/17/2008 9:47 AM
post16662
|
Vignesh Kumar Bagavathsingh wrote:
> Hi Ryan,
>
> Thanks for the reply. Can you tell exactly where I should insert those option in the IDE.
>
> If it is in IDE the options are to placed in common.mk. I am puting it here can u tell me where exactly.
Add:
ASFLAGS = -Wa,-mbooke.
Regards,
Ryan Mansfield
|
|
|
|
|
|
Vignesh Kumar Bagavathsingh
|
|
|
Vignesh Kumar Bagavathsingh
11/17/2008 9:56 AM
post16666
|
hi,
I am getting a similar error for dcbtls. What should I do?
Thanks,
|
|
|
|
|
|
Ryan Mansfield(deleted)
11/17/2008 10:04 AM
post16672
|
Vignesh Kumar Bagavathsingh wrote:
> hi,
>
> I am getting a similar error for dcbtls. What should I do?
Either install the updated binutils and add -me500 (-me500 will imply
-mbooke) to your assembler flags, or encode the instruction yourself.
Regards,
Ryan Mansfield
|
|
|
|
|
|
Vignesh Kumar Bagavathsingh
|
|
|
Vignesh Kumar Bagavathsingh
11/19/2008 8:01 AM
post16868
|
I have a query. Is it necessary to register all the interrupts in the
bootloader for MPC8568? Which are the minimum critically required
interrupt for the boot loader?
Which interrupts can be ignored? Let me know. Reply ASAP.
Regards,
Vignesh Kumar B
Member Technical Staff
HCL TECHNOLOGIES LTD.,
Mob: +91-9600015988
www.hcl.in
Disclaimer:
This message and any attachment(s) contained here are information that
is confidential, proprietary to HCL Technologies and its customers.
Contents may be privileged or otherwise protected by law. The
information is solely intended for the individual or the entity it is
addressed to. If you are not the intended recipient of this message, you
are not authorized to read, forward, print, retain, copy or disseminate
this message or any part of it. If you have received this e-mail in
error, please notify the sender immediately by return e-mail and delete
it from your computer.
-----Original Message-----
From: Ryan Mansfield [mailto:community-noreply@qnx.com]
Sent: Monday, November 17, 2008 8:35 PM
To: ostech-core_os
Subject: Re: IPL for 8568
Vignesh Kumar Bagavathsingh wrote:
> hi,
>
> I am getting a similar error for dcbtls. What should I do?
Either install the updated binutils and add -me500 (-me500 will imply
-mbooke) to your assembler flags, or encode the instruction yourself.
Regards,
Ryan Mansfield
_______________________________________________
OSTech
http://community.qnx.com/sf/go/post16672
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.
-----------------------------------------------------------------------------------------------------------------------
|
|
|
|
|
|
Brian Stecher
|
Re: Interrupts of MPC8568
|
|
Brian Stecher
11/19/2008 9:31 AM
post16880
|
Re: Interrupts of MPC8568
On Wed, Nov 19, 2008 at 08:02:00AM -0500, Vignesh Kumar Bagavathsingh wrote:
> I have a query. Is it necessary to register all the interrupts in the
> bootloader for MPC8568? Which are the minimum critically required
> interrupt for the boot loader?
> Which interrupts can be ignored? Let me know. Reply ASAP.
The only interrupt that the OS *needs* is the timer tick. You only
have to provide the more in the startup intr_intrinfo() function if
some user process (e.g. device driver) is eventually going to make use of
it. However, the startup program _is_ required to make sure that all
possible interrupt sources are masked off before handling control over
to the kernel whether or not they're listed in the syspage intrinfo section.
--
Brian Stecher (bstecher@qnx.com) QNX Software Systems
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
|
|
|
|
|
|
Vignesh Kumar Bagavathsingh
|
RE: Interrupts of MPC8568
|
|
Vignesh Kumar Bagavathsingh
11/19/2008 10:20 PM
post16946
|
RE: Interrupts of MPC8568
Hi,
Thanks for quick info.
So mean to say that the IPL doesnot require any interrupt handlers, but
the in the startup intr_intrinfo() can have timertick interrupt for the
OS and the other interrupt handlers??
Thanks & Regards,
Vignesh Kumar B
Member Technical Staff
HCL TECHNOLOGIES LTD.,
Mob: +91-9600015988
www.hcl.in
-----Original Message-----
From: Brian Stecher [mailto:community-noreply@qnx.com]
Sent: Wednesday, November 19, 2008 8:01 PM
To: ostech-core_os
Subject: Re: Interrupts of MPC8568
On Wed, Nov 19, 2008 at 08:02:00AM -0500, Vignesh Kumar Bagavathsingh
wrote:
> I have a query. Is it necessary to register all the interrupts in the
> bootloader for MPC8568? Which are the minimum critically required
> interrupt for the boot loader?
> Which interrupts can be ignored? Let me know. Reply ASAP.
The only interrupt that the OS *needs* is the timer tick. You only
have to provide the more in the startup intr_intrinfo() function if
some user process (e.g. device driver) is eventually going to make use
of
it. However, the startup program _is_ required to make sure that all
possible interrupt sources are masked off before handling control over
to the kernel whether or not they're listed in the syspage intrinfo
section.
--
Brian Stecher (bstecher@qnx.com) QNX Software Systems
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
_______________________________________________
OSTech
http://community.qnx.com/sf/go/post16880
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.
-----------------------------------------------------------------------------------------------------------------------
|
|
|
|
|
|
Brian Stecher
|
Re: Interrupts of MPC8568
|
|
Brian Stecher
11/20/2008 9:03 AM
post16964
|
Re: Interrupts of MPC8568
On Wed, Nov 19, 2008 at 10:20:25PM -0500, Vignesh Kumar Bagavathsingh wrote:
> Thanks for quick info.
> So mean to say that the IPL doesnot require any interrupt handlers, but
> the in the startup intr_intrinfo() can have timertick interrupt for the
> OS and the other interrupt handlers??
I don't believe the IPL requires any interrupts, but it's not my area of
expertise. The startup does not use any interrupts itself, it just tells
the OS what the interrupt controller hardware looks like on the board via
the intrinfo section of the system page. The OS requires a timer tick
interrupt, plus whatever other interrupts the device driver processes
what.
--
Brian Stecher (bstecher@qnx.com) QNX Software Systems
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
|
|
|
|
|
|
