Prev: PCB prototyping / copper metallization
Next: linux toosl for PIC32MX development
From: Paul E. Bennett on 13 Jun 2010 07:50
larwe wrote:

>
>> You sometimes have to think about indicator persistence of luminance.
>
> I knew I should have posted something about this, but when I say
> nothing is happening, I mean I scoped the P1.x pins that drive the
> LEDs and they are not changing state. Also I wrote a version that just
> turns on two LEDs and halts, and it still doesn't do anything. The
> code doesn't appear to be running.
>
> I loaded someone else's precompiled hex file for something and it
> works, so it's a compile/link problem on my end.

Apologies. I should have looked at OP details before responding where I
would have realised you would have already made those checks. I guess that
there may be some subtle settings in the compiler, linker, loader series
that need to be right for you to get working code across. I'll leave it to
the others more knowledgable about the products to assist you further.

--
********************************************************************
Paul E. Bennett...............<email://Paul_E.Bennett(a)topmail.co.uk>
Forth based HIDECS Consultancy
Mob: +44 (0)7811-639972
Tel: +44 (0)1235-510979
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************

From: Rich Webb on 13 Jun 2010 09:16
On Sat, 12 Jun 2010 08:06:13 -0700 (PDT), larwe <zwsdotcom(a)gmail.com>
wrote:

>On Jun 12, 10:57�am, Mel <mwil...(a)the-wire.com> wrote:
>
>> A Macgraigor Wiggler clone is easy to build, and Olimex advertises an even
>
>I own a real one bought many years ago, but have no PCs with parallel
>ports any more. And for that matter no desktop PCs - I work from
>laptops.
>
>I've stepped through the code in the simulator and it all appears to
>be sane - it's definitely running out of flash area, and everything
>seems to be inited properly. It just doesn't work on the target.
>
>Googling has yielded me other people with the same exact problem, but
>no solutions :(

I was skipping this thread since I didn't recognize what an "MCB2130"
processor was -- should have keyed on the 2130 piece!

One thing to look at is whether the loader you're using correctly sets
the pseudo-vector at 0x00000014 to be the two's complement of the
checksum of the actual interrupt vectors.

In the LPCs, the bootloader always runs and always checks that the sum
of the whole vector block is zero before it jumps to user code. It may
be that your toolchain is relying on the burner to handle setting the
correct value at 0x00000014 on the fly but your serial burner is
expecting it to already be set in the hex file.

--
Rich Webb Norfolk, VA
First  |  Prev  | 
Pages: 1 2 3
Prev: PCB prototyping / copper metallization
Next: linux toosl for PIC32MX development