List of common errors in IAR

Source: Internet
Author: User
Tags arrays
list of common errors in IARMany friends for the IAR is not very familiar with the use of IAR programming error even more do not know where to start, first found on the internet on the "IAR common Error List" article, readers.
This article was transferred from http://zhenling.chen.blog.163.com/blog/static/194085192009713101043668/


(1) Error:copy protection Check, No valid license found for this product
Reason: The installation of the time did not put the registration machine 0x ..... The lowercase letter of the string is changed to uppercase.

(2) Warning:last line of file ends without a newline F:\emoTion\IAR\PK upgrade \cc1110-8\main.c
Reason: When using iar often pops up like such a warning, in fact, as long as the last line to add a carriage return will not have this warning.

(3) Error:segment bank_relays must is defined in a Segment definition option (-Z,-b or-p)
Cause: This is a 730B compilation error, possibly due to the fact that the target project version is too high, and instead 720H is used, no error occurred.

(4) Error:could not open source file "Stdio.h"
Cause: The header file path is incorrect, and the correct method is to add $toolkit_dir$\inc\clib\ to the include paths in the preprocessor option in the Compiler. C + + box in the Settings tab.

(5) Error:could not open source file "hal.h" C:\Users\user\Desktop\ example program \ Wireless Communication Comprehensive test \library\cc2430\hal\source\ Settimer34period.c
Reason: First check C:\Users\user\Desktop\ example program \ Wireless Communication Comprehensive test \library\cc2430\hal\source\ There is no settimer34period.c this file, if any, it is because the IAR to the Chinese path support is not good reason, the project copied to the English path compiled without error.

(6) Error:segment Code_c (size:0x1869 align:0) is too a long for Segment definition. At least 0x1259 more bytes needed.
Reason: CODE is not enough, modify its size in the Xcl file, 0x28ff+0x1259=0x3b58, set to-d_code_end=0x3b58.

(7) Error:segment xdata_z (Size:0x1ea7 align:0) is too a long for Segment definition. At least 0x2a7 more bytes
Cause: Modify the segment size in the Xcl file,-d_ixdata_end=0xfd53//Revison D (This setting was safe for all revisions) there may be too many large arrays defined, sometimes the arrays defined in some functions have Point is large and will not be an error when testing the function individually in the main function.

(8) Error:segment Cstack (size:0x50 align:0x1) is too a long for Segment definition. At least 0x50 more bytes needed. The problem occurred while processing the segment placement command "-Z (DATA) cstack+_stack_size#",
Cause: This error is caused by the amount of RAM that is defined by the global variable and the array buffer, which exceeds the hardware support, size:0x50 is out of size. As long as you reduce the global variables and minimize the array buffer.

(9) error:undefined external "onboard_sendphoto::?relay" referred in Hal_key (C:\Texas instruments\zstack-1.4.3-1.2.1\ PROJECTS\ZSTACK\SAMPLES\SIMPLEAPP\CC2430DB\SIMPLECONTROLLEREB\OBJ\HAL_KEY.R51)
Reason: Only the definition of the function is not found Onboard_sendphoto (), only declaration and use. This error generally occurs at link time.

(Error:too much object code produced (more than 0x1000 bytes)
Cause: 4K Limited Edition, please use non-restricted version.

Common errors in IAR please start with the following:
1, the serial number is correct.
2, the use of the correct version, you should use 7.30B open project files can not be opened with 7.20H.
3, try not to use Chinese path.
4, the ZigBee protocol stack folder needs to be placed in the IAR installation packing directory.
5. Please determine if the current compiled folder has read and write permissions.

6. Whether the version used is limited edition.

(11) Fatal error[e72]: Segment zignv_address_space must be defined in a Segment definition option (-Z,-b or-p)

Solution: Re-install zstack-2007, in the project option inside do not move anything, directly compiled on the line.


Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.