Fix for BeMicro CV LEDs
jac_goudsmit
Posts: 418
Hi All,
I finally had a chance to play with my BeMicro CV board and noticed that the LEDs were still out of order (as reported in the BeMicroCV thread), and I couldn't find any posts with a fix, so I decided to "try my luck" at fixing it. A simple Spin program that launched a do-nothing subroutine in each cog in sequence was enough to figure out what the order should be, and it was fairly easy to find out where those LEDs are connected: in the top.qsf file.
I tried various ways to compensate for the fact that the LEDs are pulled HIGH instead of LOW, but I couldn't find a way to do it in the .qsf file so the fact that they're ON when LOW (not HIGH) cannot be made transparent to the top.tdf file as far as I know. So I just inverted the LEDs in the .tdf file.
My first contribution to the P1V sources. An exclamation point in an AHDL file and 8 numbers in a .tdf file. Yay! :-)
You can download my changes from my Github page. If you don't use Github, simply click on the "Download Zip" button.
If you have a better way to fix it, I'd like to hear it of course.
===Jac
I finally had a chance to play with my BeMicro CV board and noticed that the LEDs were still out of order (as reported in the BeMicroCV thread), and I couldn't find any posts with a fix, so I decided to "try my luck" at fixing it. A simple Spin program that launched a do-nothing subroutine in each cog in sequence was enough to figure out what the order should be, and it was fairly easy to find out where those LEDs are connected: in the top.qsf file.
I tried various ways to compensate for the fact that the LEDs are pulled HIGH instead of LOW, but I couldn't find a way to do it in the .qsf file so the fact that they're ON when LOW (not HIGH) cannot be made transparent to the top.tdf file as far as I know. So I just inverted the LEDs in the .tdf file.
My first contribution to the P1V sources. An exclamation point in an AHDL file and 8 numbers in a .tdf file. Yay! :-)
You can download my changes from my Github page. If you don't use Github, simply click on the "Download Zip" button.
If you have a better way to fix it, I'd like to hear it of course.
===Jac
Comments
If you are ready to send a pull, I'll start the changes you have up the repository chain.
You knkw it's not how many lines of code, it's the end results!
I'll set up a pull request but in case you don't know, you can pull my branch without me requesting... :-)
EDIT: You still have an open pull request; as far as I can see, it will pull the latest changes in too.
By the way I just found out that "6581" put the changes into the BeMicro CV thread, in slightly different order. Sorry I missed that.
===Jac