[quote author="robots"]Toolchain is great. Gcc 4.x works good, but there have been reports that the generated code is not optimal (slightly larger than CCS generated code).
There is an opensource debugger (i think i used http://mspdebug.sourceforge.net/) that works fine, i can act as gdbserver, flash binaries, load ram, act as standalone debugger - pretty neat tool.[/quote]
Now mspgcc is under heavy development, this summer mspgcc4 changed to uniarch, so now I think they are more focused on extending the compatibility to newer families and devices than in optimization issues. There's also needed more work on mspdebug, it's work fine for flashing but I couldn't debug well with it. At this point, works a lot better the legacy msp430-gdbproxy (but no 64-bit binaries available) and using the MSP-FET430UIF debugger. Does anybody of you have a succesful intregation with an IDE on linux? Before the uniarch migration I used Code::Blocks, but now is a bit tricky to get it working again (at least with the msp430-gcc Debian package).
Here in Spain, in every electronics shop have this flux: It's no-clean, smelly and you need something to apply it. But in my modest opinion is really great for the price, almost 2 euros. Ian, if you want to try it I'll gladly send you one.
First of all, pin 40 is the BMS and is connected to 3v3, but I think we need to put a jumper to select the boot source. Having a 1 on BMS forces to boot always from the internal ROM.
Due to my experience with the analog's Blackfin, a usable uCLinux compressed image with a minimal BusyBox needs 3.2MB of flash and nearly twice uncompressed in RAM.
[quote author="rsdio"] [quote author="Remorilla"]Freerouting is very easy to configure and works very well. Once the pcb is already routed, it continues optimizing[/quote]I have not compared them, but Eagle continues optimizing after finding a complete routing. You have control over how many passes there are. Usually, Eagle uses about 5 passes, and you can alter the costs/weights separately for each phase.
[quote author="nowait"]I just had a quick play with the software. You can assign rules to spercific nets, nice! (Im sure you can also do that with eagle)[/quote]Yes, Eagle allows you to create names for net classes, and then set rules for each class. For example, you could have a Power class with wider traces, and assign all your GND and power signals to that. But beware that you don't make traces wider than your chip pins, because that will confuse the autorouter - it doesn't understand how to connect a wide trace directly to a pin that is smaller. The latter is usually done by hand. [/quote]
I didn't say that the autorouter of the eagle is bad, what I mean is that freerouting is pretty easy to understand and configure for more novice users. I have very good results with it, but usually i have to rework the wires to fit my cosmetic needs ^^
[quote author="nowait"] Yeah its used outside Eagle but the routing is alot faster. I only stumbled across it randomly. [/quote]
I think is not a question of speed. Freerouting is very easy to configure and works very well. Once the pcb is already routed, it continues optimizing ^^
Hi Ian, to prevent any missing message I'm using the en_US translation file as guide, is that right? Your request me about the improvement of the character handling, is not posible to compare right now becouse all the special characters used on the previus translation were wrong (I think the italian keyboard map, used by Pastus, can't handle the spanish characters) so you'll need to wait for the first revision (perhaps today).
I think the spanish translation needs some major corrections, and probably I work in it soon. So becouse I'm not familiar with de C30 compiler, there is any limitation with special characters?
