All the modules in the Essentials kit lack a LDR button. According to the documentation, to put a module into DFU mode and load firmware, you can use a paper clip or opt for the erase all option in the firmware loader of the Console.
I opted for the erase all option, and after loading the DFU driver, updating the firmware was straightforward.
However, I didn’t realize that erase all truly erased everything! It erased the resident firmware and also the board-specific driver. After the erase all and loading of the current firmware, all the devices were in the same state. They could handle a few common commands like Sel() and StatLed(). The board-specific drivers were gone.
Unless I’ve overlooked something, I now have to reload all the board-specific drivers.
The documentation clearly outlines how to load the drivers. But, I believe the user should be informed about the erasure of the board drivers when using the erase all functionality. Had I known, I would have used a paper clip.
Loading the board drivers might be a future enhancement to the Console app? Additionally, the release notes should include any drivers that have undergone changes.
When you erase all, there is no need for a paper clip or for a button. This erase all was just added a few days ago so it is possible the docs are not clear. I think the loader page needs a complete review. Any other pages you remember were not clear in this regard?
About the “drivers” (not USB drivers), the “Programmer” Windows app Programmer | DUELink does handle the driver, but the console does not just yet! We plan to update the console to handle module drivers soon.
I did notice two things to look at with the programmer…
If the target module is the only thing attached to the USB→DueLink adapter then after loading the firmware, driver and test program, an error message saying “Task Failed: Downlink Error” appears and there are no test results displayed. The Stat LED is blinking. If another module is attached downstream to the target module, then testing works correctly. I suspect this is related to the test jig used in the factory?
The Rotary driver needs reviewing. It appears to not be fully handling bounce noise. Slightly turning the knob back and forward, but not a full detent, results in a count increase in one direction but not the other. I would expect no count change until there is a detent click?
Onward to my goal of developing aDueLink library for another language…..
We are updating the programmer as we speak. It was mainly made for production but then we decided to make it available for public. It is going to be simplified and cleaned up a bit.
