[mc1322x] compiling webserver-ipv6 in contiki/examples folder

[Mariano Alvira]

On Thu, Apr 29, 2010 at 12:02:19PM -0700, Chol Su Kang wrote:
> >
> > The most important difference are the crystal trims --- without the
> > right trims you'll have transmission problems between different
> > boards/802.15.4 radios.
>
> Agree. It seems to be working using same crystal trims on both NCB and SRB now.
> But, I am not sure whether the same crystal trim values are optimal for both.

Ok. You need something with a very precise time base to measure to the
resolution of the fine trim (like a Hz out of 24MHz). That comment
links to my method for that measurement. Chances are that the layout
between the NCB and SRB is similar and they probably use the same
crystal. You might notice problems interacting with other boards
though...

> > The other reason to make another board is if the GPIO hookup or the
> > peripherals are different (such as if you want debug messages on UART2
> > instead of UART1)... etc..
> Yes, NCB has some extra peripheral such as LCD.

Cool. Defining those pins in the board file makes sense.

> > which would make foo.freescale-ncb (the elf) and foo_freescale-ncb.bin
> > (the image). The object directory would be obj_mc1322x_freescale-ncb.
> >
> Should the TARGET=FREESCALE and SUBPLATFORM=NCB OR SRB?

Not really... I'm trying to consolidate all of the board specific
mc1322x stuff. TARGET selects the platform in Contiki and pretty much
every mc1322x based TARGET is going to use the same contiki-conf.h and
main.c, but with different trims and GPIO hookup. TARGET=FREESCALE is
no good because Freescale makes many, many other processors. 

Shorting the SUBPLATFORM to just ncd, srb, econotag, module,
etc... makes sense although I like having the manufacturer name in
there too.

-Mar.