N. Coesel wrote:
At 05:35 04-04-08 -0700, Vitaly Luban wrote:
So what? It does not change the fact that I have all the BDM details for
all the processors I need,
I have my own JTAG supporting ARMs (OpenOCD) and Freescale, and what do
you have for
latest MSPs? Closed source windoze dll?
If Freescale go down the sink I can easily switch to STM, albeit STM is
a bit more expensive...
If you write you code portable, you can use and CPU you want.
That is not true. First of all, certain "features" of the mspgcc make it
difficult to
use even highly portable code on MSP w/o additional sizable effort.
Second, in real world (not school) project one always limited by budgets
monetary or otherwise, required functionality and performance.
Besides,
debugging on an embedded device is not the fastest way to debug.
This is also not exactly true. While it is possible to do the "proof of
concept" this way,
real embedded code on a production board will have totally different
timing profile, so
any possible timing bug /race will possible be unnoticed in a PC
implementation, Then,
peripherals, like a/d and d/a converters etc. one can use on a PC will
have different
charaqcteristics like linearity, error magins, noise... That makes it
impossible to do real
world debugging using simulation.
Just write
for Windows/Linux first and then port your code to the embedded device.
You'll find you won't need JTAG for debugging at all.
Have you done any real project so far? Real device that's produced in
enough quantity
to force you to shave fractions of cents from the design as every extra
0.1 cent in the BOM
means some $100,000.00 loss for you? Try it and you'll see for yourself
that you're wrong
here.
Vit.
