Search found 51 matches

Sheesh ! 4004, 8008, Dinosaurs !

in 1978/79, I was 1 of 3 guys at Mattel Toys that created the
hand held electronic games.

The only processors were PMOS and NMOS and they ate batteries.
Nat ...

int1 are created from a byte,
therefore whether you have 1 int1 or 8, both conditions use a byte.

struct {
int1 F4Khz,F2KHz,F1KHz,Blink;
int1 FastBlink,SlowBli ...

I try to avoid any floating point math due to the
speed hit and inacurracy.
Convert your formula into large integers for enough accuracy as needed.
Likely, you only need 1 degree C accuracy since t ...

My code error in a for loop accessed an area beyond an array.
I was complacent in expecting the compiler error checking to find my error.

Lessons learned, any SRAM area can be corrupted when acces ...

yes,
zeroram is in code.

For loop over ran assigned struct data area, uncaught in error reporting.
I found the only solution was
#reserve data space above assigned data space
until the code error was found.

PICC 5093 & 5094

Found a For Loop goin out of bounds overwriting data in following addresses,
but no compiler error reported.

Compiler = PICC 5.085
Device = 16F1788 with 256 bytes of EEROM

Interest is to preload EEROM space with data;

Code:

#DEFINE EEMEMSTART getenv("EEPROM_ADDRESS")
#DEFINE EESTATMEM ...

Most of my applications might benefit from a separate engine handling live communications while another is busy with work.
Protocol parsing can use up too much time while a control loop is active. I ...

Old is relative.

40's years an EE, but have been programmer since 1970.

I prefer "Seasoned"... in many areas.

Wink

Thanks Ttelmah, but I haven't got that method to work.... yet.
It seems the 16F1769 has a personality and may require
something else in setups, some bit in the register to see the
PWM as input.
...

I agree, never trust defaults.
My list of #Defines get so nested sometimes, I
think I'm programming in Forth.

I agree, the COG is somewhat complicated to apply,
but MicroChip doesn't have power ...

The odd thing is that a command to change the duty doesn't work properly if the duty wasn't initially specified in the #use statement.

I have found in the past a number of bugs with MicroChips that ...

Still buggy. Duty cycle misbehaves on COG1.

#DEFINE PWM1SET TIMER=2,FREQUENCY=250Khz,DUTY=50,PWM_OFF //,OUTPUT=PWMout1 // use pin select instead

#use PWM(PWM5,PWM1SET,STREAM=Buck ...

My application is a two stage proprietary power converter.

This is what I have working, but the pwm outputs must be defined:

#pin_select COG1A=PIN_C5
#pin_select COG1B=PIN_C4
#pin_select COG2A ...