Search found 18 matches

Got it sorted -- two modules. THX!

Thanks Ttelmah, I assumed I was missing something fundamental! i did read the examples, but misunderstood something basic.

It's a single program, that I'm trying to make bootloadable. That's the ...

Using the CCS bootloader and get an unexpected conflict between the global ISR they use to replace the default, now relocated, handler and #INT_TIMER0.

Do I have to handle the timer ISRs manually i ...

Well, found it. bootloader.h has in pertinent part:

#ifndef _bootloader
#if defined(__PCM__)
#build(reset=LOADER_END+1, interrupt=LOADER_END+5)
#elif defined(__PCH__)
#build(reset=LOADER ...

The hard part it's a moving target. I comment out everything in the offending routine and it's all good. Then I break it up, and the erro moves to another place. It's like #ORGing the bootloader sp ...

Git it to compile by commenting out large blocks of code. I'll separate them, slim the big ones down, and post the procedure.

Wish there was a place to see how big each offending chunk was.

G

It's a lot of code! I'll post the top chunk that it's complaining about first.

Looks like we've got plenty of space, just not sure how to get the compiler to use it! If I comment out most of the c ...

Just took a long look, doesn't ake sense just yet. Without the bootloader #ORGing up 0x33F or low ROM, everything fits with two segments of 2048 bytes still unused.

Adding the little bootloader co ...

Shuffloing things about I get:

*** Error 71 "C:\xxx\acc.c" Line 553(1,2): Out of ROM, A segment or the program is too large @DIVFF
Seg 0001E-0033F, 0019 left, need 000CC
Seg 0034 ...

I'm that old too... I've read a your posts (and ~Hamlett, and
PCM for decades now. :-)

I know break 'em up, but you'll note that function is a tiny little thing. Is there anyplace helpful to l ...

I've searched and read about optimizations but I'm not understanding how to solve this one.

Clean compile on a 16F1517, 46% ROM used. To the working code I added in the bootloader header and loade ...

Got this sorted -- FYI all:

Multicast does quite a lot of thrashing in the Ember stack and is, in fact, slow as molasses. Unicast is blazing fast, so you're better off doing the multi's yourself u ...

Looks like for each Multicast message from the Coordinator there are three packets -- the one you sent, the reply and the acknowledge.

Slow the data rate down to almost nothing. The Unicast messag ...

One more bit -- looks like there are ACK packets coming back and you can't send another before the first gets ACK'ed. Sniffing it from the RF side.

Off to check the ACK parts of the stack, I suppo ...

The example code in the CCS guide has a quirk with Multicast that I'm trying to work around. The CCS example 14 works a treat from the SED going back to the Coordinator, you can hold the button down ...