STAR Firmware by JonnyC - Source Code and Explanation

I looked into it, but I needed something with fairly precise timing so I didn’t use it.

I used the HTML ‘pre’ tag.
(insert code here)

Helios made me a kewl Roche F6 driver (momentary switch) with two battery level indicators, but I have zero clue how to add whatever to the FW to make them work. They're run by MCU pin 3 & pin 5, circuits for both are totally separate so it's possible to use them one at a time or both together, to get a third color. Any suggestions for what the LEDs should do? Keep the original low voltage behavior (blink + ramp down) or ditch it?

Depends on your preference I suppose. In order to get the most mileage out of those indicators it seems that removing the ramp/step-down makes sense. Replace that with warning indications… but really I probably wouldn’t do it unless I could make the indicators pretty visible.

OTOH there’s nothing wrong with having both systems in place - a red indicator is just a confirmation that the stepdown is due to LVP.

I could use some help. I’m not sure what I need to do to move PWM from PB1 to PB0.

Here is what I have so far.

I changed:

  • the PWM_PIN define
  • the PWM_LVL define (output compare register)

I did not change the TCCR0A or TCCR0B stuff.

This is for the LD-29 project. In retrospect it may have made more sense to hookup the normal PWM pin… maybe that’s what I’ll end up doing.

Thanks in advance.

Bump. I could still use some help with this. Even if I hookup PB1 to the PWM input on the LD-29, I would still like to know about how this would be done. I have another project (17mm DD+7135 — linear regulated driver w/ FET turbo) which would benefit from the ability to use two PWM outputs (not simultaneously). The PCB for that project is already laid out for using both PB0 and PB1.

Dunno, but I’ll be quite happy if anyone has an answer… because when I get time I’d rather like to make a RGBW light with each color controlled individually… and I’m hoping I can use PWM arbitrarily on any two colors at the same time (most likely will need a better MCU though, with two PWM channels).

It might be a while before I can start on that though… too many other projects.

Sorry guys, was hoping someone else would chime in ;)

I've never changed the PWM from PB1 to PB0, but it looks like, along with what you changed already, you need to change TCCR0A to this...

TCCR0A = 0x83; // phase corrected PWM is 0x81 for PB0, fast-PWM is 0x83

That's my guess looking at the datasheet, which I've never been the best at reading. I just searched for TCCR0A and the first two bits relate to COM0A (PB0), and the next two bits relate to COM0B (PB1). So instead of it being "0010", it's "1000".

An outstanding thing for me to look into for RMM is the ability to change the PWM output pin based on the mode selected (so you could have a single 7135 on one pin, the rest on the other), and/or be able to change the PWM mode between phase correct and fast PWM based on the mode as phase correct does a better job with lower levels. I'm sure this was discussed before, I just haven't been paying attention lately :(

Thanks JonnyC, I’ll try that and continue to poke around in that vein if it doesn’t work by itself.

If there was a discussion about the minimum level that Fast PWM vs Phase Correct PWM could sustain, I missed it too.

I was thinking of using a 2D array to store pin states (including PWM levels) for modes. I think that could be implemented in a reasonably flexible way in order to facilitate drivers which need to do various pin sequences for modes. We currently have drivers with one PWM pin, plus drivers which operate like the DQG 26650 driver (a run pin + several pins which should be turned on exclusively for different modes), and in the future I’d really like to have a driver which operates the way I described here (#32). I think it might be possible for us to describe the modes for each of those drivers (plus the DD+7135 one I linked to before) using the same array format.

Tried to compile SRK no ramp firmware with this result.
Any ideas?

Did you by chance have 'word wrap' enabled when you copied the source to paste it into Atmel Studio?

Have no idea about that.
Please elaborate.

Did you open the .c/.txt file directly with Atmel Studio? What changes did you make before attempting to build it?

Copied it, pasted, no changes.

OK, so, what did you copy it from? Notepad? Was 'word wrap' enabled in notepad when you copied it? Atmel Studio chokes on the line breaks if you paste in source that's using 'word wrap'. That frequently causes those kind of errors - some variable ends up being placed on a new line by itself when it really belongs at the end of the previous line. 'Word wrap' is the cause of that.

Also, your screenshot is not showing the line with the error in it (line 59), please take another shot showing what's on line 59 (double click the entry in the 'errors' list at the bottom, it will scroll the upper window to the problem line automatically).

Will do that when I return home.
I just copied it from browser’s page.

Showing lines 55 to 62, line 59 highlighted...

And it only showed one error? That's pretty amazing. Save it to an actual real local file.

.c or .txt doesn't matter, if you're copy/pasting. Atmel Studio can open the .c files directly without pasting.

Hmm, I don't get that error when I compile. The line in question must be this...

PROGMEM uint8_t modes[] = { MODES };

Maybe try just adding "const" in there, as it is constant (doesn't change at runtime), so it doesn't hurt for me to add that too.

PROGMEM const uint8_t modes[] = { MODES };

Maybe you're on a slightly newer version of ARV Studio than me (5.0.1223) so it's providing better warnings? I tried enabling all warnings and it still wasn't giving me that error.

If that's the fix I'll have to add that into the file posted on my site.

I don't get that or any errors when building the same source, nothing wrong on your end. But, I'm also not copying straight from a browser window.

Yup, must be using AVR Studio 6.;file=viewtopic&amp;t=141164

"ok, I see what is going on here. newer avr-gcc versions demand that everything put in progmem is defined const [1]. So I had to add a cost in front of the first error line."