VNC2 *Viniculum II support needed*
renegadeandy
Posts: 3
Hey guys.
I have recently bought and started to code for the VNC2 board :
http://www.ftdichip.com/Products/ICs/VNC2.htm
Now it runs an OS called VOS and im having some difficulty getting it to do some of the things I want!
I was hoping somebody around this forum would have experiance with either coding against VOS or with the Viniculum boards!
Please reply if you have - and ill explain more about my rather interesting project! Hope this is the right forum - this parallax forum was the only one I could find on the internet where somebody had mentioned Viniculum II so its my only shot!
Help!
I have recently bought and started to code for the VNC2 board :
http://www.ftdichip.com/Products/ICs/VNC2.htm
Now it runs an OS called VOS and im having some difficulty getting it to do some of the things I want!
I was hoping somebody around this forum would have experiance with either coding against VOS or with the Viniculum boards!
Please reply if you have - and ill explain more about my rather interesting project! Hope this is the right forum - this parallax forum was the only one I could find on the internet where somebody had mentioned Viniculum II so its my only shot!
Help!
Comments
What were you hoping to do with it, exactly? I have a VNC2-48 chip and am just waiting for a parallax datalogger to dive in and see what can be done
What I want to do is plugin a keyboard and get the a program to work which will report back what device description and other information it can collect about it via setting info down through an emulated com port.
It works to the extent that I can get messages sent down to the com port perfectly well, but getting the info on the keyboard ive plugged in is not working at all.
All it does is freeze up and do nothing so im thinking Ive done something wrong somewhere
My code can be found here:
http://www.sendspace.com/file/1250hj
Its a Viniculum II project which can be openend usig the VNC2 toolchain.
Please help - been stuck for a week!
Andy
Andy, have you had any luck with this? I've found the VNC2 debugger to be relatively useful in tracking down problems of this nature, given that you can set hardware breakpoints, single step, and examine the contents of RAM.
I have also started a page cataloging some of the problems I have found with the VNC2 firmware, some of your problems may be the same or similar: http://joshp.no-ip.com:8080/vnc2/bugs.html
-Josh