 |
|
|
MAEC TOOL NEWS:
MAECT-M3T-CC32R-020501D
A Note on Cross-Tool Kit
M3T-CC32R V.3.00 Release 1 and V.3.10 Release 1
for HP9000/700
|
|---|
Please take note of the following problem in using cross-tool kit M3T-CC32R for the M32R family MCUs:
- On making the prototype declaration of and defining a function after calling it
- Product and Versions Concerned
M3T-CC32R V.3.00 Release 1 -- V.3.10 Release 1 for HP9000/700
- Note: The products for Windows ME, 98, 95, 2000, and NT4.0 and Solaris 2.X are not concerned with this problem.
- Description
In compilation of a source file, debug information cannot properly be generated in the absolute load module file. If any improper absolute load module is downloaded using emulator debugger M3T-PD32R or simulator debugger M3T-PD32RSIM, an error arises during downloading, resulting in the debugger being terminated forcefully.
- Conditions
- This problem may occur if the following three conditions are satisfied:
- (1) First, function A is called.
- (2) After calling function A, its prototype declaration is made.
- (3) Then, function A is defined.
- 3.1 Example
[Source file: sample.c]
--------------------------------------------------------------------
void foo(void)
{
func(); /* Condition (1) */
}
void func(void); /* Condition (2) */
void func(void) /* Condition (3) */
{
;
;
}
--------------------------------------------------------------------
- Workaround
- Make the prototype declaration of a function before calling it.
[Example of modified source file sample.c]
--------------------------------------------------------------------
void func(void); /* Prototype declaration */
void foo(void)
{
func(); /* Function call */
}
void func(void)
{
;
;
}
--------------------------------------------------------------------
- Schedule of Fixing the Problem
We plan to fix this problem in our next release.
|
|
