http://tech.groups.yahoo.com/group/68HC12/ 68HC12 Fri, 06 Nov 2009 09:41:55 GMT jpdi http://tech.groups.yahoo.com/group/68HC12/message/16521 http://tech.groups.yahoo.com/group/68HC12/message/16521 Hi, Below, the vector interrupt table I use for DP256... Note the address I put it is 0xff80, not 0xef80... I use ICC12 too, and it run OK for interrupt. When Fri, 06 Nov 2009 01:31:51 GMT jssimbe http://tech.groups.yahoo.com/group/68HC12/message/16520 http://tech.groups.yahoo.com/group/68HC12/message/16520 I'm using and HCS12 with icc12 compiler. I'm using SCI1 to communicate to a touch screen LCD. This program loads the LCD GUI. When I try loading the program Sun, 01 Nov 2009 16:52:18 GMT Bill Auerbach http://tech.groups.yahoo.com/group/68HC12/message/16519 http://tech.groups.yahoo.com/group/68HC12/message/16519 ... Technically "Hello World" mixes an array used with printf which takes a pointer. ... Agree. ... Yes. I might not be wrong to say it's always more Sat, 31 Oct 2009 20:56:12 GMT tom_almy2000 http://tech.groups.yahoo.com/group/68HC12/message/16518 http://tech.groups.yahoo.com/group/68HC12/message/16518 Hmm, for some reason I'm not getting about half of the posts here in my inbox, including this one I discovered by going to the yahoo site. ... His program: ldx Sat, 31 Oct 2009 15:57:59 GMT Tom Almy http://tech.groups.yahoo.com/group/68HC12/message/16517 http://tech.groups.yahoo.com/group/68HC12/message/16517 ... This struck me as particularly strange since I've been mixing pointers and arrays since 1980 (when I first used C) and have never caused any kind of Sat, 31 Oct 2009 14:54:54 GMT Bill_CT http://tech.groups.yahoo.com/group/68HC12/message/16516 http://tech.groups.yahoo.com/group/68HC12/message/16516 ... You say "probably cause all kinds of damage". Before anyone here thinks that's a really bad thing and it means they are doing something wrong, perhaps you Fri, 30 Oct 2009 02:23:38 GMT Andrei Chichak http://tech.groups.yahoo.com/group/68HC12/message/16515 http://tech.groups.yahoo.com/group/68HC12/message/16515 ... [Non-text portions of this message have been removed] Fri, 30 Oct 2009 01:54:50 GMT Bill Auerbach http://tech.groups.yahoo.com/group/68HC12/message/16514 http://tech.groups.yahoo.com/group/68HC12/message/16514 ... There is no harm to use pointers and arrays and no damage results from doing so. They are equivalent - the only time a problem will occur is when a Wed, 28 Oct 2009 14:10:50 GMT Robert http://tech.groups.yahoo.com/group/68HC12/message/16513 http://tech.groups.yahoo.com/group/68HC12/message/16513 As stated by others it is folly to use malloc/free in simple embedded systems. The best solution is to implement asynchronous static ring buffers for rx/tx Wed, 28 Oct 2009 06:21:20 GMT Andrei Chichak http://tech.groups.yahoo.com/group/68HC12/message/16512 http://tech.groups.yahoo.com/group/68HC12/message/16512 Okay, let's take a look at the output and the evidence and make some wild ass guesses. You can assume that SCI_OutString is okay since 1) the "Hello World" Wed, 28 Oct 2009 02:40:53 GMT Bill_CT http://tech.groups.yahoo.com/group/68HC12/message/16511 http://tech.groups.yahoo.com/group/68HC12/message/16511 Zach, The code for the serial port looks OK, although for production code it would benefit from a code review. SCI_OutStatus(1); // Is it clear to send (buffer Wed, 28 Oct 2009 01:39:07 GMT zach.r.long@... http://tech.groups.yahoo.com/group/68HC12/message/16510 http://tech.groups.yahoo.com/group/68HC12/message/16510 Thanks everyone, your comments on not using malloc make sense for this system, however I am still left with the issue of incorrect output, and the thought of Tue, 27 Oct 2009 06:26:11 GMT Andrei Chichak http://tech.groups.yahoo.com/group/68HC12/message/16509 http://tech.groups.yahoo.com/group/68HC12/message/16509 I agree that malloc failed and it is passing back 0 to indicate that it failed, and you are using that as an address of your string. Please have some empathy Tue, 27 Oct 2009 05:02:04 GMT Bill Auerbach http://tech.groups.yahoo.com/group/68HC12/message/16508 http://tech.groups.yahoo.com/group/68HC12/message/16508 ... Both points are good. Furthermore, for this series of processors or smaller and generally in embedded systems, avoid malloc and free. These smaller Tue, 27 Oct 2009 04:52:08 GMT Edward Karpicz http://tech.groups.yahoo.com/group/68HC12/message/16507 http://tech.groups.yahoo.com/group/68HC12/message/16507 Probably malloc didn't succeed char* outData =(char*) malloc (sizeof (char*)* 5); // make room for 5 char BTW comment is wrong, should be make room for 5