-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ULX3S (85f?) IO connections change upon loading etc. #533
Comments
Hello, This may be the same issue discussed here #499 in short, the problem is that icestudio mixes the pins when all the characters in the name of one pin are also included in the name of another pin. in your case, : "gn1" is included "gn19" , "gp1" is included "gp19", .... A workaround (that i am similarly using for my colorlight i5 board) is to modify the pinout.json file of you ulx3 board ( in folder ...\icestudio\resources\boards\ulx3s-85f ) by renaming pins : "gn1" --> "gn1_" |
I think the issue you mentioned seems very similar It would nevertheless be nice if a proper fix for this issue could be found. |
Hello, Preliminary remark: i think i found the problem. it is in file joint.shapes.js, in the for loop starting at line 1176 so in the end of loading process we will see the last affected value (gp19) The reason for those successive affectations is that the at the line 1182-1183
is not exactly what we need. I replaced it with something found on the web:
At it seem it does the trick. But Carlos, Juan and all javascript aficionados please, check that modification! Corresponding pull request : #535 |
Thanks a lot Jo! it's a perfect solution! i think all should work fine. |
Version Info:
Icestudio Version: 0.7.0
OS: Windows 8.1
When connecting certain inputs and outputs for the ULX3S 85F (in my case, but is probably similar for other models of the ULX3S), the connections change when loading and changing the "name"of the connection.
I have made a minimalist example demonstrating the problem, I have connected all the IO pins which I have found which demonstrate this problem, and connected them as shown in the image below:
If the project is now saved, the program closed, restarted, and the project reopened, we get the result as shown in the image below.
It turns out that the same problem occurs when changing the name of an in- or output block. For example changing >GN1 to something else will change the IO pin it is connected to.
Right now I manually fix these changes each time I open a project, but this is somewhat error prone.
I have attached the project which demonstrates this problem (in a zipped format, so github allows me to attach it to the bug)
testfile_for_IO_bug_ULX3S_85f.zip
The text was updated successfully, but these errors were encountered: