Error 1347 Hi Tech
Visited Search Results View More Blog Recent Blog Posts View More PMs Unread PMs Inbox Send New PM View More Page Extras Menu Forum Themes Elegant Mobile Home » All Forums » [Development Tools] » HI-TECH C Compilers » Error [1347], who can tell me the reason,thanks Mark Thread UnreadFlat Reading Mode❐ Error [1347], who can tell me the reason,thanks Author Post Essentials Only Full Version bojin@eaton.com New Member Total Posts : 4 Reward points : 0 Joined: 2010/09/20 02:25:58Location: 0 Status: offline 2010/10/18 19:45:01 (permalink) 0 Error [1347], who can tell me the reason,thanks Hi when I use Compiler: HI-TECH C for PIC10/12/16 Lite Mode MCU: PIC16F876A it shows that : Error [1347] ; 0. can't find 0x28 words (0x28 withtotal) for psect "text1083" in segment "CODE" (largest unused contiguous range 0x24) I can not find the reason. what is that mean? out of memory? who can tell me the real reason, thanks Jacob Email:bojin@eaton.com #1 2 Replies Related Threads sborden Super Member Total Posts : 1932 Reward points : 0 Joined: 2010/08/05 02:12:53Location: 0 Status: offline Re:Error [1347], who can tell me the reason,thanks 2010/10/18 19:58:17 (permalink) 0 Yeah, pretty much. You need to split up long routines and tables or it cannot fit them in one page and blows a gasket. #2 Stefan99 Super Member Total Posts : 234 Reward points : 0 Joined: 2010/07/19 01:50:01Location: Germany Status: offline Re:Error [1347], who can tell me the reason,thanks 2010/10/19 00:04:21 (permalink) 0 - use the smallest possible datatypes (best 8bit-variables) - use local variables and functions. - avoid big arrays. - try to use reusable functions. OR use a bigger PIC [8)] post edited by Stefan99 - 2010/10/19 00:05:32 #3 Jump to: Jump to - - - - - - - - - - [Development Tools] - - - - MPLAB X IDE - - - - MPLAB Xpress - - - - MPLAB 8 IDE - - - - MPLAB Harmony - - - - MPLAB X IPE - - - - MPLAB® Code Configurator - - - - MPLAB REAL ICE - - - - MPLAB ICD In Circuit Debuggers - - - - MPLAB Simulator - - - - MPASM, MPLINK, MPLIB (assembler, linker, librarian) - - - - MPLAB XC8 - - - - HI-TECH C Compilers - - - - MP
Posts Today's Posts 1Next > Oct 31, 2013 #1 kuannygohcheetatt Thread Starter Member Oct 31, 2013 61 0 Code ( (Unknown Language)): //bimary 0b110 //hexadecimal 0xA //dec imal 110 #define XTAL_FREQ 4MHZ #include
Help Rules Groups Blogs What's New? Teardown Videos Datasheets Advanced Search Forum Digital Design and Embedded Programming Microcontrollers [SOLVED] PIC12F Comiler Problem with http://www.edaboard.com/thread194216.html HI-Tech compiler + Post New Thread Results 1 to 4 of 4 PIC12F Comiler Problem with HI-Tech compiler LinkBack LinkBack URL About LinkBacks Thread Tools Show Printable Version Download http://cboard.cprogramming.com/c-programming/132503-pic16f684-interfacing-hitachi-44780-a-3.html This Thread Subscribe to this Thread… Search Thread Advanced Search 24th November 2010,04:53 #1 g_shyam1682 Full Member level 4 Join Date Jan 2010 Location Udaipur-Rajshan-India Posts 206 Helped error 1347 53 / 53 Points 2,341 Level 11 PIC12F Compiler Problem with HI-Tech compiler Hi Friend I am programming in MPLAB and my compiler is Hi-Tech. I am using pic12f675. I write my code in C language. When my code is limited to 75% of program memory space, it is work OK. But when my code is more than error 1347 hi 75%, It give following error message at build time. Error [1347] ; 0. can't find 0x0 words (0x0 withtotal) for psect "strings" in segment "CODE" (largest unused contiguous range 0xB5) Please Help me to solve this error. Thanks in advance Shyam INDIA. Last edited by g_shyam1682; 24th November 2010 at 05:00. 24th November 2010,04:53 24th November 2010,17:22 #2 ZASto Advanced Member level 2 Achievements: Join Date Jan 2008 Location Messy Corner, 44°47'31.56"N, 20°28'9.16"E Posts 533 Helped 108 / 108 Points 4,197 Level 15 Re: PIC12F Comiler Problem with HI-Tech compiler Do not program those tiny (10Fxx 12Fxx) controllers in C. There is not enough program and RAM memory. 24th November 2010,17:22 24th November 2010,18:46 #3 Tahmid Advanced Member level 5 Achievements: Join Date Jun 2008 Location Cornell University, Ithaca, New York, USA (from Dhaka, Bangladesh) Posts 4,756 Helped 1768 / 1768 Points 37,370 Level 47 Blog Entries22 Re: PIC12F Comiler Problem with HI-Tech compiler Hi, I think zasto is right. What I think is, it's not a problem with the
Programming Boards C Programming PIC16F684 Interfacing with Hitachi 44780 Getting started with C or C++ | C Tutorial | C++ Tutorial | C and C++ FAQ | Get a compiler | Fixes for common problems Thread: PIC16F684 Interfacing with Hitachi 44780 Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-08-2010 #31 anduril462 View Profile View Forum Posts Registered User Join Date Nov 2010 Location Long Beach, CA Posts 5,879 So I Googled for that error message and found a few things of interest: HI-TECH Software Frequently Asked Questions HI-TECH Software Forums: error in MPLAB HI-TECH Software Forums: Error [1347] ; 0. can't find 0x1 words (0x1 withtotal) for psect Read through those. One suggests the printf family of functions may be the culprit. More on optimizing that later. My first suggestion would be to look at compiler settings. Embedded compilers usually let you specify code, data, stack and heap sizes, so maybe you could adjust that. You also have a few quirks in your code. First, you're putting an extra null character at the end of some of your sprintf commands (sprintf puts a null for you). Also, I don't know why you're using goto, you could just put the code below LOCATION1: inside the while loop, like so: Code: do { strcpy(TopMessage, "Input Stride"); sprintf(BotMessage, "%d cm \0", stridelength); LCDWrite(0b00000001, 0); for (i = 0; i < Delay; i++); for (i = 0; TopMessage[i] != 0; i++) LCDWrite(TopMessage[i], 1); LCDWrite(0b11000000, 0); for (i = 0; BotMessage[i] != 0; i++) LCDWrite(BotMessage[i], 1); if (UP == 1) ... } while (FORWARD != 1); It might help if you get rid of more global variables by moving them into functions so they only exist on the stack when the function is active (i, j,