From richard at imagecraft.com Tue Jul 14 13:17:48 2009 From: richard at imagecraft.com (Richard Man) Date: Tue Jul 14 14:28:23 2009 Subject: [Icc-430] OT: My Book Signing this Friday, July 17th Message-ID: <200907142128.n6ELSM4R046970@mail.imagecraft.com> Sorry for spamming, but I know some of you work in the Bay Area: **** I was in the Stanford's Continuing Education class Self Publishing Your Photo Book this past Spring, and now the fruits of our labor are ready to be unleashed into the world :-) The course was taught by Brigitte Carnochan and there are about 20 people in the class. For a few people, they had the book practically all planned at the start of the class. For others, it took a bit more work. For me personally, at the 3rd session when we were presenting our materials to our peers and when we should already have most of the images nailed down, I was looking at just a dozen images that I didn't know what to do with. One of co-instructors said to me, "Richard, I feel like you are holding out on me, these are (good) images but they are not cohesive to tell a story." It was definitely a "uh oh, what do I do now" moment. And so it goes. I learned a lot about pacing, editing, and presentation. My book combines my love for photography and calligraphy, and the theme of Asian Spiritual worship in its core. You can get a 15 page preview of my book Full Circle here: http://www.blurb.com/bookstore/detail/745963 A special edition of 10 copies is available for $100, each comes with an archival print and a hand written calligraphy of "Full Circle." I hope you can join us this Friday from 7-10PM at the Modern Book Gallery, 494 University Ave., Palo Alto, CA. http://www.modernbook.com. You may purchase the books at that time. // richard w: http://www.rfman.com blog: http://rfman.wordpress.com book: http://www.blurb.com/bookstore/detail/745963 From bgarmer at ambientalert.com Tue Jul 21 10:00:52 2009 From: bgarmer at ambientalert.com (Bill Garmer) Date: Tue Jul 21 11:10:47 2009 Subject: [Icc-430] Problem compiling for a MSP430F5437 In-Reply-To: <200907151900.n6FJ012F081534@mail.imagecraft.com> Message-ID: <94C5A1526E432B469C9E047B917B0D972C9D5F@ACSDC1.ambient.corp> I get the following error: !ERROR file 'crt430.o': undefined symbol '_main' Never seen this error before - any clues as to what it means? From jdurand at interstellar.com Tue Jul 21 10:15:04 2009 From: jdurand at interstellar.com (Jerry Durand) Date: Tue Jul 21 11:26:32 2009 Subject: [Icc-430] Problem compiling for a MSP430F5437 In-Reply-To: <94C5A1526E432B469C9E047B917B0D972C9D5F@ACSDC1.ambient.corp> References: <94C5A1526E432B469C9E047B917B0D972C9D5F@ACSDC1.ambient.corp> Message-ID: <4A65F798.2010708@interstellar.com> Bill Garmer wrote: > I get the following error: > !ERROR file 'crt430.o': undefined symbol '_main' > > Never seen this error before - any clues as to what it means? > I've had some odd errors show up when I accidentally had spaces in the file/folder names. I've also seen some oddities (mainly with NoICE) when the files are on a Linux server and I'm running ICC/NoICE on a Windows machine. -- Jerry Durand, Durand Interstellar, Inc. www.interstellar.com tel: +1 408 356-3886, USA toll free: 1 866 356-3886 Skype: jerrydurand From bgarmer at ambientalert.com Tue Jul 21 11:13:26 2009 From: bgarmer at ambientalert.com (Bill Garmer) Date: Tue Jul 21 12:23:20 2009 Subject: [Icc-430] Solution In-Reply-To: <200907211900.n6LJ01Dd007243@mail.imagecraft.com> Message-ID: <94C5A1526E432B469C9E047B917B0D972C9D63@ACSDC1.ambient.corp> That was it. It wasn't linking in the file with main because of a space in the name. Didn't run into that before - thanks for the heads up. From jdurand at interstellar.com Tue Jul 21 11:36:44 2009 From: jdurand at interstellar.com (Jerry Durand) Date: Tue Jul 21 12:48:24 2009 Subject: [Icc-430] Solution In-Reply-To: <94C5A1526E432B469C9E047B917B0D972C9D63@ACSDC1.ambient.corp> References: <94C5A1526E432B469C9E047B917B0D972C9D63@ACSDC1.ambient.corp> Message-ID: <4A660ABC.7090309@interstellar.com> Bill Garmer wrote: > That was it. It wasn't linking in the file with main because of a space > in the name. Didn't run into that before - thanks for the heads up. > > Yes, my Apple ][ could handle spaces in file names, Windows software tends to fall apart. -- Jerry Durand, Durand Interstellar, Inc. www.interstellar.com tel: +1 408 356-3886, USA toll free: 1 866 356-3886 Skype: jerrydurand From richard-lists at imagecraft.com Tue Jul 21 12:02:59 2009 From: richard-lists at imagecraft.com (Richard Man) Date: Tue Jul 21 13:13:59 2009 Subject: [Icc-430] Solution In-Reply-To: <94C5A1526E432B469C9E047B917B0D972C9D63@ACSDC1.ambient.corp > References: <200907211900.n6LJ01Dd007243@mail.imagecraft.com> <94C5A1526E432B469C9E047B917B0D972C9D63@ACSDC1.ambient.corp> Message-ID: <200907212013.n6LKDxig009004@mail.imagecraft.com> Bill, was the space just in the filename itself? It should work. What's the name of the file in question and its complete file path? Thanks. At 11:13 AM 7/21/2009, you wrote: >That was it. It wasn't linking in the file with main because of a space >in the name. Didn't run into that before - thanks for the heads up. > // richard // photo book: http://www.blurb.com/bookstore/detail/745963 From bgarmer at ambientalert.com Wed Jul 22 11:09:37 2009 From: bgarmer at ambientalert.com (Bill Garmer) Date: Wed Jul 22 12:19:33 2009 Subject: [Icc-430] Re: Solution In-Reply-To: <200907221900.n6MJ010N039568@mail.imagecraft.com> Message-ID: <94C5A1526E432B469C9E047B917B0D972C9D68@ACSDC1.ambient.corp> The file name was FireALERT Mk II RMT main.c it is now FireALERT_Mk_II_RMT_main.c The path is S:\projects\FireALERT_Mk_II\software\RMT\ it was S:\projects\FireALERT Mk II\software\RMT\ So there were spaces in both the file name and the path that I removed. Don't know which did it but that fixed the problem. From llchisho at paradise.net.nz Mon Jul 27 00:30:07 2009 From: llchisho at paradise.net.nz (llchisho@paradise.net.nz) Date: Mon Jul 27 01:40:28 2009 Subject: [Icc-430] _PUT_SR intrinsic Message-ID: <1248679807.4a6d577f8fbdd@www.paradise.net.nz> Hi all, While fiddling with the _GET_SR and _PUT_SR intrinsics the other day in V7.10A, I found that no code was emitted for _PUT_SR in the simplest scenarios - storing SR in a C variable assigned to a register by the compiler to protect a couple of instructions. It was OK if a physical memory location had been assigned to the variable defined for storing the SR, if a for loop occurred between saving and restoring SR, or if the instructions in question were surrounded by a do ... while(0) construct. ----------------------------------- void func2a(void) { unsigned int mysr; mysr = _GET_SR(); DINT(); P2OUT = 1; P2OUT = 0; _PUT_SR(mysr); } ----------------------------------- generates: ----------------------------------- .dbfunc e func2a _func2a fV ; mysr -> R4 .even _func2a:: push R4 .dbline -1 .dbline 34 ; } ; ; void func2a(void) { .dbline 36 ; unsigned int mysr; ; mysr = _GET_SR(); mov R2,R14 mov R14,r11 mov r14,R4 .dbline 37 ; DINT(); dint nop .dbline 38 ; P2OUT = 1; mov.b #1,&0x29 .dbline 39 ; P2OUT = 0; mov.b #0,&0x29 .dbline 40 ; _PUT_SR(mysr); .dbline -2 L4: pop R4 .dbline 0 ; func end ret .dbsym r mysr 4 i .dbend ----------------------------------- When the compiler could be tricked into emitting code for _PUT_SR, it was of the form: ----------------------------------- ; _PUT_SR(mysr); mov R4,R14 mov R14,R2 .dbline -2 L5: pop R4 ----------------------------------- Has anybody else seen this sort of behavior? Len Chisholm. From bailey at peak.org Mon Jul 27 01:01:32 2009 From: bailey at peak.org (bailey@peak.org) Date: Mon Jul 27 02:11:49 2009 Subject: [Icc-430] _PUT_SR intrinsic In-Reply-To: <1248679807.4a6d577f8fbdd@www.paradise.net.nz> References: <1248679807.4a6d577f8fbdd@www.paradise.net.nz> Message-ID: <3817.69.59.200.77.1248681692.squirrel@webmail.peak.org> Len, I hadn't run into this, but it definitely needs fixing! As you probably also noticed the code generation for the primitives is something you don't want too look to closely at... If I recall correctly, Richard had cleaning up this code generation on the list already, perhaps it can be folded into fixing the bug??? Of course, this is easy for me to say since I don't have a clue what the back-end code generator looks like :) Kirk Bailey bailey@peak.org Willamette RF, Inc. > Hi all, > > While fiddling with the _GET_SR and _PUT_SR intrinsics the other day in > V7.10A, > I found that no code was emitted for _PUT_SR in the simplest scenarios - > storing > SR in a C variable assigned to a register by the compiler to protect a > couple of > instructions. > It was OK if a physical memory location had been assigned to the variable > defined for storing the SR, if a for loop occurred between saving and > restoring > SR, or if the instructions in question were surrounded by a do ... > while(0) > construct. > > ----------------------------------- > void func2a(void) { > unsigned int mysr; > mysr = _GET_SR(); > DINT(); > P2OUT = 1; > P2OUT = 0; > _PUT_SR(mysr); > } > ----------------------------------- > generates: > ----------------------------------- > .dbfunc e func2a _func2a fV > ; mysr -> R4 > .even > _func2a:: > push R4 > .dbline -1 > .dbline 34 > ; } > ; > ; void func2a(void) { > .dbline 36 > ; unsigned int mysr; > ; mysr = _GET_SR(); > mov R2,R14 > mov R14,r11 > mov r14,R4 > .dbline 37 > ; DINT(); > dint > nop > .dbline 38 > ; P2OUT = 1; > mov.b #1,&0x29 > .dbline 39 > ; P2OUT = 0; > mov.b #0,&0x29 > .dbline 40 > ; _PUT_SR(mysr); > .dbline -2 > L4: > pop R4 > .dbline 0 ; func end > ret > .dbsym r mysr 4 i > .dbend > ----------------------------------- > When the compiler could be tricked into emitting code for _PUT_SR, it was > of the > form: > ----------------------------------- > ; _PUT_SR(mysr); > mov R4,R14 > mov R14,R2 > .dbline -2 > L5: > pop R4 > ----------------------------------- > > Has anybody else seen this sort of behavior? > > Len Chisholm. > _______________________________________________ > Icc-430 mailing list > Icc-430@imagecraft.com > http://dragonsgate.net/mailman/listinfo/icc-430 > From jdurand at interstellar.com Mon Jul 27 08:00:33 2009 From: jdurand at interstellar.com (Jerry Durand) Date: Mon Jul 27 09:11:43 2009 Subject: [Icc-430] _PUT_SR intrinsic In-Reply-To: <1248679807.4a6d577f8fbdd@www.paradise.net.nz> References: <1248679807.4a6d577f8fbdd@www.paradise.net.nz> Message-ID: <4A6DC111.8040006@interstellar.com> llchisho@paradise.net.nz wrote: > Hi all, > > While fiddling with the _GET_SR and _PUT_SR intrinsics the other day in V7.10A, > I found that no code was emitted for _PUT_SR in the simplest scenarios - storing > SR in a C variable assigned to a register by the compiler to protect a couple of > instructions. > While not a general work-around, for functions like that I use the monitor pragma #pragma monitor GetTime long GetTime() { // get real time clock return RTC; } -- Jerry Durand, Durand Interstellar, Inc. www.interstellar.com tel: +1 408 356-3886, USA toll free: 1 866 356-3886 Skype: jerrydurand