From: Grahame J. <gb...@th...> - 2008-06-19 05:19:06
|
Hi, This is a general question on the direction of Gumstix as in the Build Environments being maintained. Buildroot does what I require, however I had to developed lots of support scripts for maintaining my specific requirements. However it does the job well. I can see many advantages in using OpenEmbedded. One it saves me writing lots of scripts to maintain my code but is slow to compile the simplest of things even on my quad core box :( Additionally it is poorly documented. The documentation on gumstix.net is rudimentary to say the least. It does get you started but presently is unable to help for more advanced usage. The helloworld.c example is OK for a very simple implementation, however lacks any substance required for a more complicated scenario. There is a need to have some advanced examples on writing Makefiles and .bb files and including files from other packages etc. I just want to clarify: 1, Is buildroot being maintained & for how long. 2, Is OE the way ahead for the long term. 3, Will the documentation for OE improve in the short term? Many Thanks Grahame Jordan |
From: Gordon K. <go...@gu...> - 2008-06-19 15:13:16
|
1, Is buildroot being maintained & for how long. Maintained but not grown is the best description. AS bugs are fixed they will be merged in. 2, Is OE the way ahead for the long term. Definitely. Steve, could you provide some more insight and rationale for our selection please? 3, Will the documentation for OE improve in the short term? We will get on that. Gordon > Hi, > > This is a general question on the direction of Gumstix as in the Build > Environments being maintained. > > Buildroot does what I require, however I had to developed lots of > support scripts for maintaining my specific requirements. > However it does the job well. > > I can see many advantages in using OpenEmbedded. > One it saves me writing lots of scripts to maintain my code but is slow > to compile the simplest of things even on my quad core box :( > Additionally it is poorly documented. The documentation on gumstix.net > is rudimentary to say the least. > It does get you started but presently is unable to help for more > advanced usage. > The helloworld.c example is OK for a very simple implementation, however > lacks any substance required for a more complicated scenario. > There is a need to have some advanced examples on writing Makefiles and > .bb files and including files from other packages etc. > > I just want to clarify: > 1, Is buildroot being maintained & for how long. > 2, Is OE the way ahead for the long term. > 3, Will the documentation for OE improve in the short term? > > > Many Thanks > > Grahame Jordan > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Borre v. D. <bor...@gm...> - 2008-06-20 00:57:42
|
On Thu, Jun 19, 2008 at 8:13 AM, Gordon Kruberg <go...@gu...> wrote: > 1, Is buildroot being maintained & for how long. > Maintained but not grown is the best description. AS bugs are fixed they > will be merged in. > > 2, Is OE the way ahead for the long term. > Definitely. Steve, could you provide some more insight and rationale for > our selection please? > > 3, Will the documentation for OE improve in the short term? > ------->>>>We will get on that. > YES PLEASE! - Borre > > Gordon > > > > > Hi, > > > > This is a general question on the direction of Gumstix as in the Build > > Environments being maintained. > > > > Buildroot does what I require, however I had to developed lots of > > support scripts for maintaining my specific requirements. > > However it does the job well. > > > > I can see many advantages in using OpenEmbedded. > > One it saves me writing lots of scripts to maintain my code but is slow > > to compile the simplest of things even on my quad core box :( > > Additionally it is poorly documented. The documentation on gumstix.net > > is rudimentary to say the least. > > It does get you started but presently is unable to help for more > > advanced usage. > > The helloworld.c example is OK for a very simple implementation, however > > lacks any substance required for a more complicated scenario. > > There is a need to have some advanced examples on writing Makefiles and > > .bb files and including files from other packages etc. > > > > I just want to clarify: > > 1, Is buildroot being maintained & for how long. > > 2, Is OE the way ahead for the long term. > > 3, Will the documentation for OE improve in the short term? > > > > > > Many Thanks > > > > Grahame Jordan > > > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Mark A. <m_a...@co...> - 2008-06-21 17:15:33
|
Hi - I believe the proper make file format for a dependency line is that the indentation is a tab and not spaces. Spaces won't typically work in a make file. 'mark Darren M wrote: > Just a thought on your missing separator problem - could be a space instead > of tab problem > > sertest: sertest.c > ${CC} ${CFLAGS} ${LDFLAGS} -o sertest sertest.c > ^^ > ^^------Are these spaces or a tab.. > > > |
From: Darren M <d_m...@op...> - 2008-06-22 05:18:10
|
After reading my post again I see that it might be taken two ways. So to make it clear... If you you use spaces to indent you WILL get a missing separator error when you run bitbake. Sorry for the confusion... (and for the thread abuse). Darren. -- View this message in context: http://www.nabble.com/OpenEmbedded-tp17997498p18051322.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: gmullin <gm...@in...> - 2008-07-08 17:59:50
|
Darren and Mark, I just got back to working on this. I copied and pasted to create the make file. I guess this turned tabs into spaces. When I edited the make file and made the indentation tabs instead of spaces I did not get missing separator errors. Thanks. Gerald -- View this message in context: http://www.nabble.com/OpenEmbedded-tp17997498p18345334.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Shane K. <ski...@uc...> - 2008-07-08 18:29:15
|
Hi, I'm using the i2c-io program...it seems to work inconsistently...I'm not sure why. Here is what i'm getting: root@gumstix-custom-verdex:/home$ i2c-io 0x0b info ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xce ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:/home$ i2c-io 0x0b info version: 2 minVersion: 1 SVN Revision: 1612 root@gumstix-custom-verdex:/home$ Does anyone have any idea why this is happening or how to fix it? ~Shane |
From: Dave H. <dhy...@gm...> - 2008-07-08 20:03:14
|
Hi Shane, > I'm using the i2c-io program...it seems to work inconsistently...I'm > not sure why. Here is what i'm getting: > > root@gumstix-custom-verdex:/home$ i2c-io 0x0b info > ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xce > ERROR: I2cReadBlock failed > ERROR: Unable to retrieve information from i2c address 0x0b > root@gumstix-custom-verdex:/home$ i2c-io 0x0b info > version: 2 > minVersion: 1 > SVN Revision: 1612 > root@gumstix-custom-verdex:/home$ Is this the stock i2c-io program? Or one with modifications? I've never seen that particular problem, except when there were bugs in one side or the other. It would be interesting to see the output of i2c-io -v -d 0x0b info when it fails (this causes all of the bytes sent or received to be printed out). -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Shane K. <ski...@uc...> - 2008-07-08 20:14:57
|
Hi Dave, Here's what I get for what you gave me root@gumstix-custom-verdex:/home$ i2c-io -v -d 0x0b info i2c-io: invalid option -- v ERROR: opt:63 maybe you wanted this: root@gumstix-custom-verdex:/home$ i2c-io --verbose --decimal 0x0b info version: 2 minVersion: 1 SVN Revision: 1612 It obviously works now...I'll try to get it to break again...I have stuff plugged PWM ports 3a-1a and all of port C... ~shane On Tue, 8 Jul 2008 13:03:03 -0700 "Dave Hylands" <dhy...@gm...> wrote: > Hi Shane, > >> I'm using the i2c-io program...it seems to work inconsistently...I'm >> not sure why. Here is what i'm getting: >> >> root@gumstix-custom-verdex:/home$ i2c-io 0x0b info >> ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xce >> ERROR: I2cReadBlock failed >> ERROR: Unable to retrieve information from i2c address 0x0b >> root@gumstix-custom-verdex:/home$ i2c-io 0x0b info >> version: 2 >> minVersion: 1 >> SVN Revision: 1612 >> root@gumstix-custom-verdex:/home$ > > Is this the stock i2c-io program? Or one with modifications? > > I've never seen that particular problem, except when there were bugs > in one side or the other. > > It would be interesting to see the output of > > i2c-io -v -d 0x0b info > > when it fails (this causes all of the bytes sent or received to be >printed out). > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source >project, > along with a healthy diet, reduces your potential for chronic >lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: gmullin <gm...@in...> - 2008-06-21 00:06:21
|
I second that! I have wasted a lot of time trying to bitbake sertest.c which I had no problems building in buildroot. I followed the helloworld example by deleting the do_compile lines in the helloworld_1.0.0.bb recipe and adding Makefile in the SRC_URI list. Makefile had the following contents: sertest: sertest.c ${CC} ${CFLAGS} ${LDFLAGS} -o sertest sertest.c Bitbake would stop with an error about a missing separator and did not compile. Gerald -- View this message in context: http://www.nabble.com/OpenEmbedded-tp17997498p18038354.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Shane K. <ski...@uc...> - 2008-07-08 20:18:57
|
Ok I'm killing the i2c-io with this script: Maybe there's something wrong with it: modprobe i2c-dev modprobe i2c-pxa i2c-load 0x0b --reset info i2c-load --reset 0x0b write i2c-io.hex i2c-io 0x0b info i2c-io 0x0b wr ddrg 0x18 i2c-io 0x0b portg 0 sleep 1 i2c-io 0x0b wr portg 0x08 i2c-io 0x0b wr TCCR1A 0xAA i2c-io 0x0b wr TCCR1B 0x1A i2c-io 0x0b wr ICR1 250 i2c-io 0x0b wr TCNT1 0 i2c-io 0x0b wr OCR1A 125 i2c-io 0x0b wr OCR1B 125 i2c-io 0x0b wr OCR1C 125 i2c-io 0x0b wr TCCR3A 0xAA i2c-io 0x0b wr TCCR3B 0x1A i2c-io 0x0b wr ICR3 250 i2c-io 0x0b wr TCNT3 0 i2c-io 0x0b wr OCR3A 125 i2c-io 0x0b wr OCR3B 125 i2c-io 0x0b wr OCR3C 125 #timer1 i2c-io 0x0b setdir b.5 out i2c-io 0x0b setdir b.6 out i2c-io 0x0b setdir b.7 out #timer 3 i2c-io 0x0b setdir e.3 out i2c-io 0x0b setdir e.4 out i2c-io 0x0b setdir e.5 out i2c-io 0x0b wr OCR3A 125 i2c-io 0x0b wr OCR3B 125 i2c-io 0x0b wr OCR3C 125 i2c-io 0x0b wr OCR1A 125 running this script doesn't make the Verdex very happy...any ideas... ~Shane On Tue, 08 Jul 2008 14:15:03 -0600 "Shane Kirkbride" <ski...@uc...> wrote: > Hi Dave, > > Here's what I get for what you gave me > root@gumstix-custom-verdex:/home$ i2c-io -v -d 0x0b info > i2c-io: invalid option -- v > ERROR: opt:63 > > maybe you wanted this: > root@gumstix-custom-verdex:/home$ i2c-io --verbose --decimal 0x0b >info > version: 2 > minVersion: 1 > SVN Revision: 1612 > > It obviously works now...I'll try to get it to break again...I have > stuff plugged PWM ports 3a-1a and all of port C... > ~shane > > On Tue, 8 Jul 2008 13:03:03 -0700 > "Dave Hylands" <dhy...@gm...> wrote: >> Hi Shane, >> >>> I'm using the i2c-io program...it seems to work inconsistently...I'm >>> not sure why. Here is what i'm getting: >>> >>> root@gumstix-custom-verdex:/home$ i2c-io 0x0b info >>> ERROR: I2cTransfer: CRC failed: Rcvd: 0x00, expecting: 0xce >>> ERROR: I2cReadBlock failed >>> ERROR: Unable to retrieve information from i2c address 0x0b >>> root@gumstix-custom-verdex:/home$ i2c-io 0x0b info >>> version: 2 >>> minVersion: 1 >>> SVN Revision: 1612 >>> root@gumstix-custom-verdex:/home$ >> >> Is this the stock i2c-io program? Or one with modifications? >> >> I've never seen that particular problem, except when there were bugs >> in one side or the other. >> >> It would be interesting to see the output of >> >> i2c-io -v -d 0x0b info >> >> when it fails (this causes all of the bytes sent or received to be >>printed out). >> >> -- >> Dave Hylands >> Vancouver, BC, Canada >> http://www.DaveHylands.com/ >> >> ------------------------------------------------------------------------- >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source >>project, >> along with a healthy diet, reduces your potential for chronic >>lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source >project, > along with a healthy diet, reduces your potential for chronic >lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2008-07-08 20:33:07
|
Hi Shane, On Tue, Jul 8, 2008 at 1:18 PM, Shane Kirkbride <ski...@uc...> wrote: > Ok I'm killing the i2c-io with this script: Maybe there's something wrong > with it: > modprobe i2c-dev > modprobe i2c-pxa > i2c-load 0x0b --reset info > i2c-load --reset 0x0b write i2c-io.hex > i2c-io 0x0b info You should have a little sleep between the load and the info request. You'll need to at least wait for the i2c bootloader timeout (which I think is 5 seconds). Actually, once you've programmed the flash once, there really isn't any need to do the i2c-load again. The syntax of the first i2c-load line is also incorrect: i2c-load --reset 0x0b info (the --reset have to come before the 0x0b) >> Here's what I get for what you gave me >> root@gumstix-custom-verdex:/home$ i2c-io -v -d 0x0b info >> i2c-io: invalid option -- v >> ERROR: opt:63 Sorry, that should have been --verbose and --debug -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Darren M <d_m...@op...> - 2008-06-21 08:36:20
|
Just a thought on your missing separator problem - could be a space instead of tab problem sertest: sertest.c ${CC} ${CFLAGS} ${LDFLAGS} -o sertest sertest.c ^^ ^^------Are these spaces or a tab.. -- View this message in context: http://www.nabble.com/OpenEmbedded-tp17997498p18041961.html Sent from the Gumstix mailing list archive at Nabble.com. |