Re: [U-Boot] Fix for a build ?
Hi Igor Luri, We solve this problem building U-Boot and failing projects passing -j 1 argument to Make (without running simultaneous jobs), and the rest of software with -j 9. Your suggestion solved the problem for us, thank you very much. Hope this helps. It did :) again thank you Peace. Have a wonderful day Sylvain ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Fix for a build ?
Dear Wolfgang Denk, We have about 650 Makefiles in the current U-Boot source tree; the top level Makefile alone has seen 371 commits since v1.3.4 [snip] I am not in a position to remember each and every of these changes, or their potential impact on building in SMP configurations. I understand that one person cannot remember the awesome lot of work that have been done since 1.3.4 and that many fundamental changes occurred during these two years. I gave you quick answer: use git bisect to find out which commit makes a difference for your build system. Of course this requires that you have some build target that is supported in mainline, and that shows the same problem like your out-of-tree port. I'm sorry I did not see the email related to this before sending the other one. This is a perfect suggestion and I'll probably setup a build configuration for the lite5200 board that is on my desk to see if my problem show itself. [snip] You seem to fail to understand how a free software project like U-Boot works. U-Boot is very easy to upgrade - we take great care not to break support for any of the supported boards, and we accept even exotic boards and include these into the mainline tree, even if there is most likely no other user ever. So if you want to be able to upgrade easily just make sure your code is part of the mainline distribution. Ok, I am now in the seat of someone that could push the idea of putting the next platform we develop into the mainline. But other MBA/Finance/Manager persons that really take decisions will surely ask my department why I would like to give internal informations of our product in a way that any of our competitors could get it easily. How could I give them an answer that would be aligned with the philosophy ? I understand how free software project works, I have participate in some and even worked to revive an old dead project (http://datavibe.net/~essiene/ale/) into something up-to-date while I was at University. (http://sonia.etsmtl.ca/index.php?id=553) I've also participate in some kernel janitor task in my free time because I care about open source and I'm passionate by technology. I was a quite active member in the french forum of gentoo to help new comers and find solutions to problems. I care about people and I want the people around me to improve as best as they can. I did not intend to be rude, but I have to admit that your attitude is not exactly in line how community projects like this work. Then I'm sorry, but for me this project sounds like it is directed by a bunch of elitist who would not accept someone that don't already know how the project work. Criticizing and judging questions asked by people that may never have work on or with something like U-Boot before. If you are afraid of getting to much dumb questions then this means that the documentation and the FAQ from the U-Boot website could be improve in a way that new comers would find easily the informations they need. I don't have the time to answer requests like yours in long prosa - Then you can simply skip the question, this mailing list have surely more than hundred persons that can answer if they think they could help. I don't think anybody ask that you answer to all emails, this is surely an extremely huge time consuming task. Maybe you want to read http://catb.org/esr/faqs/smart-questions.html And maybe you want to read http://www.reddit.com/r/linux/comments/9y9de/eric_raymonds_famous_how_to_ask_questions_the/ Have a nice day Sylvain ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Fix for a build ?
Hi everybody, We have recently installed an automated build system in our company and occasionally there is a problem when U-Boot is built. One build will work the other will not without any changes to the sources (it is not: 1 work, then other fail... it is more like 3 may work the 4 will not but the 5 will). Our build system guy says that the problem is probably a race condition with a dependency in the U-Boot make. Here is the error that trigger the failure. *[09:23:58]:* */home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/.depend:73: *** multiple target patterns. Stop.* *[09:23:58]:* *make: *** [/home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/start.o] Error 2* *[09:23:58]:* */home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/.depend:73: *** multiple target patterns. Stop.* *[09:23:58]:* *make: *** Waiting for unfinished jobs* *[09:23:58]:* *make: *** [/home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boot-1.3.4/cpu/mpc5xxx/libmpc5xxx.a] Error 2* *[09:24:01]:* *Process exited with code 2* It is not extremely problematic because everything is automated and next build after the failing one will work (when it is this error), but it's only that we get a notification email when a build fail and we are afraid that our developers will take the failure as a Boy Who Cried Wolf... if you know what I mean. Is there a way to fix this ? It could be putting some sleep somewhere... Any suggestion ? Sylvain * Also, upgrading U-Boot is not an option... since we don't have the need nor resources to port a new version of U-Boot to this product. So please don't suggest that. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Fix for a build ?
And do you know what was the fix so that I could apply it to our version ? On Mon, May 3, 2010 at 2:52 PM, Mike Frysinger vap...@gentoo.org wrote: On Monday 03 May 2010 09:51:29 Sylvain Lamontagne wrote: We have recently installed an automated build system in our company and occasionally there is a problem when U-Boot is built. One build will work the other will not without any changes to the sources (it is not: 1 work, then other fail... it is more like 3 may work the 4 will not but the 5 will). Our build system guy says that the problem is probably a race condition with a dependency in the U-Boot make. Here is the error that trigger the failure. *[09:23:58]:* */home/slamon/server/TeamCity/buildAgent/work/19b40828dc62d35d/build/u-boo t-1.3.4/cpu/mpc5xxx/.depend:73: *** multiple target patterns. Stop.* this should already be fixed in the latest version -mike ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Fix for a build ?
Is there a way to fix this ? It could be putting some sleep somewhere... Please upgrade to a recent version. Thank you for suggesting ... * Also, upgrading U-Boot is not an option... since we don't have the need nor resources to port a new version of U-Boot to this product. So please don't suggest that. Heh. So what do you want? A solution, but no changes? I was asking in case someone remembered and could have been an easy fix. Something like: Yes, Sylvain If I remember there was a race condition with MakefileX in Y specially on an SMP machine. That would have been a perfectly correct answer. We will not fix for free any bugs in old versions of the code. That was absolutely not what I was asking for ... I did not want anybody of you to fix this for me. I was asking for pointers and it was a quick question that should have get a quick answer, nothing more. - stick with the obsolete code you have and stop complaining Again, I was not complaining. Reading the archive of this mailing list, it seems that you, Wolfgang, tend to often take what people ask as a complaint and I suggest that you should work on this aspect if you want people to contribute by their free will. - update to the current release and ask again if there should still be problems (which I doubt) - fix the problems yourself - hire somebody else to fix the problems (and most probably the most efficient way to fix the problem will be an update to the current release) You may have never been in this situation, but I work for a company that is big enough to not let me change something that work fine only for some failure from time to time related to a race condition on a new automated build server. I did try to update U-Boot in the past few month but I always end-up with problem related to variables that changes names (CFG vs CONFIG) or to bizarre memory config created by my predecessor that make the new version unworkable. I am not an electronician and there is still aspect of embedded development that I don't yet understand. I have an IT degree and I'm currently learning embedded in the field since my predecessor was laid off. If giving chance to people is not in your nature, then I'm sorry to have been taking your time. Make it easy to upgrade and people may then upgrade more often. The Linux kernel 2.4 is still supported in some way for people that have very old hardware that work only with it, so why wouldn't it be legitimate to keep a tested version of U-Boot on a running product only because it's 2 year old ? Anyway thx for answering even if the answer was a bit rude... Sylvain ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Problem with flash on a MPC5200B board
Humm ... Nobody can help me ? If you need more informations I can get them, I would really like to understand the debug output I'm seeing. Thank you Sylvain 2008/10/7 Sylvain Lamontagne [EMAIL PROTECTED] Hi Everyone I'm pretty new to U-Boot and Embedded system globally, but in the last few weeks I have learn a lot and I'm now trying to port correctly U-Boot v 1.3.4 to a custom board based on a Icecube. I'm able to boot a linux kernel with it when I use the RAM with the bootm command. Unfortunately, I must make it work with the FLASH. The chip used for the flash is a S29GL128 or a S29GL256 from Spansion, they are 16bits chips but the bus is only 8bits. By reading the datasheet, these chips are supposed to support the Common Flash Interface so I'm trying to make then work with the CFI driver of U-Boot. Here is what I get when booting with DEBUG activated: U-Boot 1.3.4 (Oct 7 2008 - 16:39:49) CPU: MPC5200B v2.2, Core v1.4 at 378 MHz Bus 84 MHz, IPB 84 MHz, PCI 21 MHz Board: Icecube Based Board I2C: 93 kHz, ready DRAM: 64 MB Top of RAM usable for U-Boot at: 0400 Reserving 551k for U-Boot at: 03f76000 Reserving 130k for malloc() at: 03f55800 Reserving 68 Bytes for Board Info at: 03f557bc Reserving 60 Bytes for Global Data at: 03f55780 Stack Pointer at: 03f55768 New Stack Pointer is: 03f55768 Now running in RAM - U-Boot at: 03f76000 FLASH: flash detect cfi fwc addr ff00 cmd f0 f0 8bit x 8 bit fwc addr ff00 cmd f0 f0 8bit x 8 bit fwc addr ff55 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr ff10 is= 0 51 fwc addr ff000555 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr ff10 is= 0 51 fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ffaa cmd 98 9898 16bit x 8 bit is= cmd 51(Q) addr ff20 is= 5151 5151 is= cmd 52(R) addr ff22 is= 5252 5252 is= cmd 59(Y) addr ff24 is= 5959 5959 device interface is 2 found port 2 chip 1 port 16 bits chip 8 bits 00 : 51 52 59 02 00 40 00 00 00 00 00 27 36 00 00 06 [EMAIL PROTECTED]'6... 10 : 06 09 13 03 05 03 02 19 02 00 06 00 01 ff 00 00 20 : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 ... fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ff001554 cmd aa 16bit x 8 bit fwc addr ff000aaa cmd 55 16bit x 8 bit fwc addr ff001554 cmd 90 9090 16bit x 8 bit fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ffaa cmd 98 9898 16bit x 8 bit manufacturer is 2 manufacturer id is 0x5 device id is 0x56 device id2 is 0x0 cfi version is 0x3133 size_ratio 1 port 16 bits chip 8 bits found 1 erase regions erase region 0: 0x02ff erase_region_count = 256 erase_region_size = 131072 ERROR: too many flash sectors fwc addr ff00 cmd f0 f0 8bit x 8 bit flash_protect ON: from 0xFFF0 to 0xFFF43FFF flash_protect ON: from 0xFFFE to 0x 32 MB basetask = 0, tasks = 2 task_org = 0x03fb4c00 TDT start = 0x0040, end = 0x01b8 PCI: Bus Dev VenId DevId Class Int PCI Scan: Found Bus 0, Device 24, Function 0 00 18 168c 001b 0200 00 PCI Scan: Found Bus 0, Device 26, Function 0 00 1a 1057 5809 0680 00 In:serial Out: serial Err: serial U-Boot relocated to 03f76000 Net: mpc5xxx_fec_init_phy... Begin mpc5xxx_fec_init_phy... Done FEC ETHERNET Type boot to boot to Linux (default) Type help for a list of commands So I got an ERROR: too many flash sectors and a 32 MB size ... I know for sure that the chip is 16 MB so there is a kind of inconsistency... I'm also a bit confuse about what #define I should use to force my board to communicate in 8bit even if it's capable of 16bit. I though that I simply had to #undef FLASH_CFI_16BIT but that doesn't seem to do the trick. I'm not sure to understand the debug output I got... fwc addr ff00 cmd f0 f0 8bit x 8 bit ... fwc addr ff00 cmd f0 f0f0 16bit x 8 bit Also is the value of erase_region_count = 256 should be the number of sector on the chip Because I know that the ship have a maximum of 128 sectors... If someone could brief me a bit about the debug output posted above I would greatly appreciate. I'm pretty sure I have nearly complete the port except for this FLASH issue... Help/Suggestion/Comments are welcome Thank you Sylvain ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Problem with flash on a MPC5200B board
Hi Everyone I'm pretty new to U-Boot and Embedded system globally, but in the last few weeks I have learn a lot and I'm now trying to port correctly U-Boot v 1.3.4 to a custom board based on a Icecube. I'm able to boot a linux kernel with it when I use the RAM with the bootm command. Unfortunately, I must make it work with the FLASH. The chip used for the flash is a S29GL128 or a S29GL256 from Spansion, they are 16bits chips but the bus is only 8bits. By reading the datasheet, these chips are supposed to support the Common Flash Interface so I'm trying to make then work with the CFI driver of U-Boot. Here is what I get when booting with DEBUG activated: U-Boot 1.3.4 (Oct 7 2008 - 16:39:49) CPU: MPC5200B v2.2, Core v1.4 at 378 MHz Bus 84 MHz, IPB 84 MHz, PCI 21 MHz Board: Icecube Based Board I2C: 93 kHz, ready DRAM: 64 MB Top of RAM usable for U-Boot at: 0400 Reserving 551k for U-Boot at: 03f76000 Reserving 130k for malloc() at: 03f55800 Reserving 68 Bytes for Board Info at: 03f557bc Reserving 60 Bytes for Global Data at: 03f55780 Stack Pointer at: 03f55768 New Stack Pointer is: 03f55768 Now running in RAM - U-Boot at: 03f76000 FLASH: flash detect cfi fwc addr ff00 cmd f0 f0 8bit x 8 bit fwc addr ff00 cmd f0 f0 8bit x 8 bit fwc addr ff55 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr ff10 is= 0 51 fwc addr ff000555 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr ff10 is= 0 51 fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ffaa cmd 98 9898 16bit x 8 bit is= cmd 51(Q) addr ff20 is= 5151 5151 is= cmd 52(R) addr ff22 is= 5252 5252 is= cmd 59(Y) addr ff24 is= 5959 5959 device interface is 2 found port 2 chip 1 port 16 bits chip 8 bits 00 : 51 52 59 02 00 40 00 00 00 00 00 27 36 00 00 06 [EMAIL PROTECTED]'6... 10 : 06 09 13 03 05 03 02 19 02 00 06 00 01 ff 00 00 20 : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 ... fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ff001554 cmd aa 16bit x 8 bit fwc addr ff000aaa cmd 55 16bit x 8 bit fwc addr ff001554 cmd 90 9090 16bit x 8 bit fwc addr ff00 cmd f0 f0f0 16bit x 8 bit fwc addr ffaa cmd 98 9898 16bit x 8 bit manufacturer is 2 manufacturer id is 0x5 device id is 0x56 device id2 is 0x0 cfi version is 0x3133 size_ratio 1 port 16 bits chip 8 bits found 1 erase regions erase region 0: 0x02ff erase_region_count = 256 erase_region_size = 131072 ERROR: too many flash sectors fwc addr ff00 cmd f0 f0 8bit x 8 bit flash_protect ON: from 0xFFF0 to 0xFFF43FFF flash_protect ON: from 0xFFFE to 0x 32 MB basetask = 0, tasks = 2 task_org = 0x03fb4c00 TDT start = 0x0040, end = 0x01b8 PCI: Bus Dev VenId DevId Class Int PCI Scan: Found Bus 0, Device 24, Function 0 00 18 168c 001b 0200 00 PCI Scan: Found Bus 0, Device 26, Function 0 00 1a 1057 5809 0680 00 In:serial Out: serial Err: serial U-Boot relocated to 03f76000 Net: mpc5xxx_fec_init_phy... Begin mpc5xxx_fec_init_phy... Done FEC ETHERNET Type boot to boot to Linux (default) Type help for a list of commands So I got an ERROR: too many flash sectors and a 32 MB size ... I know for sure that the chip is 16 MB so there is a kind of inconsistency... I'm also a bit confuse about what #define I should use to force my board to communicate in 8bit even if it's capable of 16bit. I though that I simply had to #undef FLASH_CFI_16BIT but that doesn't seem to do the trick. I'm not sure to understand the debug output I got... fwc addr ff00 cmd f0 f0 8bit x 8 bit ... fwc addr ff00 cmd f0 f0f0 16bit x 8 bit Also is the value of erase_region_count = 256 should be the number of sector on the chip Because I know that the ship have a maximum of 128 sectors... If someone could brief me a bit about the debug output posted above I would greatly appreciate. I'm pretty sure I have nearly complete the port except for this FLASH issue... Help/Suggestion/Comments are welcome Thank you Sylvain ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
