Search found 10 matches

right, the chip is a dsPIC33EP512MU810, my bad

I haven't dug too far into why enabling PSV gave me issues, but I was able to use a const array by first copying the function pointer into ram ...

To the site which called 'validate_symargs'

The define was created as a way to reuse the construct in different functions. Since these are goto/label pairs, they are scoped to the function where t ...

Ttelmah: It looks like the array of function pointers is probably going to win out here.

I've resumed testing the switch statements as I've never seen the compiler produce either a jump table, or e ...

*** note, the case values in the previous post are sequential enum values, placed in order. Presently both the enum and switch statement are generated by a separate tool from a specification.

Alri ...

Greetings all!

I'm looking at using a large switch statement for a binary parser using the PCD 5.081 compiler. After reading about some of the tricks to get the PCH compiler to generate jump table ...

Yes and no.

You can use it with a literal argument and get the 16-bit behavior from the documentation. eg:
setup_pwm5_duty(100)

However, if you need to set your duty cycle from a variable inst ...

Just an update on my progress working through this...

It is indeed the interrupt vector, as defined by the #build line which is colliding with the rom modifier array. The same error appears even i ...

Happy to see you have it sorted, sad to see that you had to resort to a direct register write to pull it off.

This part is odd:

0054: MOVF @78,W
0055: MOVLB 0C
0056: MOVW ...

MotoDan: I believe the issue is that set-pwm5_duty is an overloaded function supporting either an 8-bit or 16-bit argument. Looking at the documentation, the 16-bit variant produces a duty-cycle that ...

Greetings all!

I'm currently working through an issue with a bootloader I'm building, and am hoping for some insight.

Currently I'm targeting the dsPIC33EP512MU810, and one of the details with t ...