On Thu, Oct 11, 2012 at 08:42:37AM +0200, Michiel Konstapel wrote:
> > Hi Michiel,
> >
> > Looks like perhaps I have broken something, though I can't see what it
> > might be. Does the first attempt at identification always fail with
> > 0.20, and never fail with 0.18?
>
> That does seem to be the case:
> Anything else I can do to help you out?
> Michiel
If you have time to spare, a git bisect would be really helpful. It'll
probably take about half an hour of testing, though. If you have an
up-to-date git repository sitting there, start with:
git bisect start
git bisect bad v0.20
git bisect good v0.18
After that, you'll be shown a message telling you how many commits are
in the range. Test the current one (you probably only need to check for
the identification issue at startup):
make clean && make && mspdebug uif -j
If that works, type "git bisect good", otherwise "git bisect bad". After
about 9ish tests, the range should hopefully be narrowed to a single
commit which broke support for your chip.
- Daniel
--
Daniel Beer <dlb...@gmail.com> www.dlbeer.co.nz
IRC: inittab (Freenode) PGP key: 2048D/160A553B
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
