After a successful power up, I moved on to the I2Cbus interface. On the I2C bus is the LED controller, LP5569, and the USB Power Controller, STUSB4500. The STUSB4500 was not in ready stock anywhere, so that was a DO NO INSTALL during assembly. The STUSB4500 is only accessed once and that is during PCB configuration, at least that is the current implementation. So I built the Harmony 2.0 driver around the LP5569. What I have now is a very basic driver that does the following:
- RESET
- Initialize
- Configuration (enable/disable)
- Register Dump
- Update all PWM registers
- Basic Write Register
- Basic Read Register
- Read/Modify/Write Register
There is still a lot of clean up work and optimization that needs to happen. This is a standalone program for now, which means it will need to be integrated with the other pieces. But I am quite happy with the current state.
There were some development issues. The PICKIT4 does not seem to like MPLAB 4.2 very much. It would hang occasionally and does not the PIC32 register or SFRs. Changing back to the PICKIT3, at least solved the register and SFR issue.
The LED control in Brick Controller 2 consists of 10 LED ports. In the original Brick Controller there were only four LED ports and this was not sufficient. The LP5569 will control 9 LEDS either individually or in up to 3 RGB groupings. Port 10 is under direct software control and is connected to a PWM port on the PIC32. The intention is to have ON/OFF, Burst, Cycle and the PWM functionality on all 10 LED ports, but we will see how this goes. The LP5569 is a much more capable device with multiple types of controls, but these advanced features will have to wait until the basic BC2 is done.
The next step is implement the PWM features of the PIC32 that will be used with the 4 motor ports and LED port 10. I will be using LED port 0 as the prototype, since in this implementation it is much easier to observe.
Here is a quick video of a single LED with varying intensity.
No comments:
Post a Comment