Closed arblake closed 3 years ago
You'd need to put the silice executable in a path where the command line can find it.
Which project are you trying to build? My changes to the frameworks aren't included in the silice project yet, but @sylefeb is looking at them.
Rob.
On Thu, 1 Oct 2020 at 17:01, Adrian Blake notifications@github.com wrote:
when trying to build I get an error: -- Parsing build.v' using frontend verilog' -- ERROR: Can't open input file `build.v' for reading: No such file or directory ERROR: Failed to open JSON file 'build.json'. 0 warnings, 1 error but this is because it cannot find silice. Where, what directory, should the project be located given that silice is in $HOME/silice/bin ... the default location? can I install the silice exectutable into something like /usr/local/bin ?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT75DLC6UDCIWEK627TSISRWLANCNFSM4SATZ22A .
The build script needs to the source file included, like this: . . silice -f frameworks/fomu_USB_SPRAM.v $1 -o build.v j1eforth.ice
(as a side note, I just started work to port the design to the new Silice build system, will be simpler, hope to get this ready in the next few days!)
I have uploaded using dfu-util but only device found is /dev/tty, not the usual ttyACM0 or ttyUSB0
What do you get in your dmesg? Do you have a FOMU HACKER?
On Fri, 2 Oct 2020 at 03:30, Adrian Blake notifications@github.com wrote:
I have uploaded using dfu-util but only device found is /dev/tty, not the usual ttyACM0 or ttyUSB0
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702493884, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYTZKKVCHVAQXNXDGZNDSIU3KRANCNFSM4SATZ22A .
This: [19360.307355] usb 1-3.4: new full-speed USB device number 22 using xhci_hcd [19360.412024] usb 1-3.4: New USB device found, idVendor=1209, idProduct=5bf0, bcdDevice= 1.01 [19360.412030] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [19360.412034] usb 1-3.4: Product: Fomu PVT running DFU Bootloader v1.9.1 [19360.412038] usb 1-3.4: Manufacturer: Foosn
Do you have a FOMU HACKER? No ... looking now
Sorry, I miss understood you question. I have the Fomu device
Is it the HACKER version?
On Fri, 2 Oct 2020 at 07:28, Adrian Blake notifications@github.com wrote:
Sorry, I miss understood you question. I have the Fomu device
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702551837, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYTYWZ6YOVGCQNBJOG7TSIVXI5ANCNFSM4SATZ22A .
Apologies, I don't know where the "No ... looking now" came from. Must have wrongly clicked paste.
On Fri, 2 Oct 2020 at 08:03, Rob Shelton rob.s.ng15@googlemail.com wrote:
Is it the HACKER version?
On Fri, 2 Oct 2020 at 07:28, Adrian Blake notifications@github.com wrote:
Sorry, I miss understood you question. I have the Fomu device
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702551837, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYTYWZ6YOVGCQNBJOG7TSIVXI5ANCNFSM4SATZ22A .
What branch of Silice are you? It was working on the WIP branch.
On Fri, 2 Oct 2020 at 08:06, Rob Shelton rob.s.ng15@googlemail.com wrote:
Apologies, I don't know where the "No ... looking now" came from. Must have wrongly clicked paste.
On Fri, 2 Oct 2020 at 08:03, Rob Shelton rob.s.ng15@googlemail.com wrote:
Is it the HACKER version?
On Fri, 2 Oct 2020 at 07:28, Adrian Blake notifications@github.com wrote:
Sorry, I miss understood you question. I have the Fomu device
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702551837, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYTYWZ6YOVGCQNBJOG7TSIVXI5ANCNFSM4SATZ22A .
I simply purchased the device from crowd supply ... CS-FOMU-01
I will try WIP branch later today
There are several versions of the FOMU. I have a HACKER one so my pcf (pinout file) matches the HACKER. If you have a different board, you'd need a different pcf file.
On Fri, 2 Oct 2020 at 08:24, Adrian Blake notifications@github.com wrote:
I simply purchased the device from crowd supply ... CS-FOMU-01
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702572239, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYTZ2UMLJRJ6GZO7BI7LSIV53DANCNFSM4SATZ22A .
I am trying to load eforth
That's different to my board, probably a production version, so you'll need a different pcf file.
On Fri, 2 Oct 2020, 09:26 Adrian Blake, notifications@github.com wrote:
I am trying to load eforth [image: ECJr-cdUwAEnhwt] https://user-images.githubusercontent.com/185642/94903172-1183de80-04a2-11eb-864e-b51f2c59da04.jpg
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702597360, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT4LGDH5VVWGINKODSLSIWFDTANCNFSM4SATZ22A .
Hmmm , so I need to investigate.
This is the pcf file for the PVT FOMU that you have:
https://github.com/im-tomu/fomu-workshop/blob/master/verilog/pcf/fomu-pvt.pcf
I have updated the github to include this file along with a fomu_pvt_USB_SPRAM.sh file to build for the FOMU PVT.
On Fri, 2 Oct 2020 at 10:12, Adrian Blake notifications@github.com wrote:
Hmmm , so I need to investigate.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702617596, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT2P56BWH4NAPS5RIMDSIWKPHANCNFSM4SATZ22A .
build successful, upload IDLE, continuing DFU mode device DFU version 0101 Device returned transfer size 1024 Copying data from PC to DFU device Download [=========================] 100% 104090 bytes Download done. state(7) = dfuMANIFEST, status(0) = No error condition is present state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present Done!
dmesg shows New USB device found, idVendor=1d50, idProduct=6130, bcdDevice= 0.00 [13757.647580] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [13757.656462] cdc_acm 1-3.4:1.0: ttyACM0: USB ACM device [13858.149495] wlp108s0: cannot understand ECSA IE operating class, 4, ignoring [13858.149505] wlp108s0: cannot understand ECSA IE operating class, 4, ignoring
ls -l shows the port. Then I try to open it and it has gone. another ls -l and there is no ttyACM0. I take out the device and reinsert and dmesg shows new full-speed USB device number 30 using xhci_hcd [14179.668413] usb 1-3.4: New USB device found, idVendor=1209, idProduct=5bf0, bcdDevice= 1.01 [14179.668422] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [14179.668427] usb 1-3.4: Product: Fomu PVT running DFU Bootloader v1.9.1 [14179.668432] usb 1-3.4: Manufacturer: Foosn
Looks like the writing to the device was not permanent.
I'll compile for the Pvt tomorrow and upload for you to try. I can't test, as I don't have the hardware.
On Fri, 2 Oct 2020, 18:50 Adrian Blake, notifications@github.com wrote:
build successful, upload IDLE, continuing DFU mode device DFU version 0101 Device returned transfer size 1024 Copying data from PC to DFU device Download [=========================] 100% 104090 bytes Download done. state(7) = dfuMANIFEST, status(0) = No error condition is present state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present Done!
dmesg shows New USB device found, idVendor=1d50, idProduct=6130, bcdDevice= 0.00 [13757.647580] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [13757.656462] cdc_acm 1-3.4:1.0: ttyACM0: USB ACM device [13858.149495] wlp108s0: cannot understand ECSA IE operating class, 4, ignoring [13858.149505] wlp108s0: cannot understand ECSA IE operating class, 4, ignoring
ls -l shows the port. Then I try to open it and it has gone. another ls -l and there is no ttyACM0. I take out the device and reinsert and dmesg shows new full-speed USB device number 30 using xhci_hcd [14179.668413] usb 1-3.4: New USB device found, idVendor=1209, idProduct=5bf0, bcdDevice= 1.01 [14179.668422] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [14179.668427] usb 1-3.4: Product: Fomu PVT running DFU Bootloader v1.9.1 [14179.668432] usb 1-3.4: Manufacturer: Foosn
Looks like the writing to the device was not permanent.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702871875, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT4G7CBAEIJGYNTJQ5DSIYHGVANCNFSM4SATZ22A .
I have compiled a j1eforth-FOMU-PVT.dfu for you if you'd be so kind as to test it. I cannot as I do not have the appropriate unit.
On Fri, 2 Oct 2020 at 19:17, Rob Shelton rob.s.ng15@googlemail.com wrote:
I'll compile for the Pvt tomorrow and upload for you to try. I can't test, as I don't have the hardware.
On Fri, 2 Oct 2020, 18:50 Adrian Blake, notifications@github.com wrote:
build successful, upload IDLE, continuing DFU mode device DFU version 0101 Device returned transfer size 1024 Copying data from PC to DFU device Download [=========================] 100% 104090 bytes Download done. state(7) = dfuMANIFEST, status(0) = No error condition is present state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present Done!
dmesg shows New USB device found, idVendor=1d50, idProduct=6130, bcdDevice= 0.00 [13757.647580] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [13757.656462] cdc_acm 1-3.4:1.0: ttyACM0: USB ACM device [13858.149495] wlp108s0: cannot understand ECSA IE operating class, 4, ignoring [13858.149505] wlp108s0: cannot understand ECSA IE operating class, 4, ignoring
ls -l shows the port. Then I try to open it and it has gone. another ls -l and there is no ttyACM0. I take out the device and reinsert and dmesg shows new full-speed USB device number 30 using xhci_hcd [14179.668413] usb 1-3.4: New USB device found, idVendor=1209, idProduct=5bf0, bcdDevice= 1.01 [14179.668422] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [14179.668427] usb 1-3.4: Product: Fomu PVT running DFU Bootloader v1.9.1 [14179.668432] usb 1-3.4: Manufacturer: Foosn
Looks like the writing to the device was not permanent.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-702871875, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT4G7CBAEIJGYNTJQ5DSIYHGVANCNFSM4SATZ22A .
I uploaded successfully. dmsg reports a device /dev/ttyACM0 , as expected. The I try minicom and it reports "inicom: cannot open /dev/ttyACM0: No such file or directory" . ls no longer shows /dev/ttyACM0 It is as if the code is not correctly written and permantely stored.
I'm stuck as I don't have that hardware, and I know that it works on the HACKER board.
Have you asked on the forum if anyone has it working on the Pvt board?
On Sat, 3 Oct 2020, 17:07 Adrian Blake, notifications@github.com wrote:
I uploaded successfully. dmsg reports a device /dev/ttyACM0 , as expected. The I try minicom and it reports "inicom: cannot open /dev/ttyACM0: No such file or directory" . ls no longer shows /dev/ttyACM0 It is as if the code is not correctly written and permantely stored.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-703126164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT2I4VCDGKOHFPSK6WTSI5D4PANCNFSM4SATZ22A .
No and I shall do soon. BTW where are you? I am in Estonia, but I am an Australian
Inverness, Scotland
On Sat, 3 Oct 2020, 17:11 Adrian Blake, notifications@github.com wrote:
No and I shall do soon. BTW where are you? I am in Estonia, but I am an Australian
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-703126663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT26V4CXTRVZUPYCA3LSI5EKDANCNFSM4SATZ22A .
Rob, No progress. I also tried on a windows machine.
Hi Adrian,
I am sorry about this. Not having the hardware, I'd need someone else who has it, or maybe Tim, who is really an expert on the FOMU to help.
Rob.
On Tue, 6 Oct 2020 at 14:25, Adrian Blake notifications@github.com wrote:
Rob, No progress. I also tried on a windows machine.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-704266780, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT24CMKFHD3HDEW7M63SJMLDPANCNFSM4SATZ22A .
Tim Ansell notifications@github.com 4:30 AM (7 hours ago)  to im-tomu/fomu-workshop, me, Author  The hacker and pvt devices have different pin out configurations and a few other small changes
Hi Tim,
I've tried a pinout file for the pvt device that I found, but not having a pvt device I cannot test.
On Wed, 7 Oct 2020 at 10:27, Adrian Blake notifications@github.com wrote:
Tim Ansell notifications@github.com 4:30 AM (7 hours ago)  to im-tomu/fomu-workshop, me, Author  The hacker and pvt devices have different pin out configurations and a few other small changes
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-704812087, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT6KGNRIHUEG2VWEZDTSJQX73ANCNFSM4SATZ22A .
I have looked at the .pcf file and circuit diagrams and cannot see any problems. Maybe it is in the build process.
dfu-suffix had the wrong product id , changed, but that did not help. I have tried again on a windows machine to write the code without success. Windows device manager "This device cannot start"
Just for info, so that I can build versions with the correct ID using the WIP branch of Silice which has many improvements, what is the correct ID for the PVT?
Rob.
I've uploaded builds for the hacker and pvt using the updated Silice, but the PVT one for now will have the wrong suffix. I'll do a new one later.
On Wed, 7 Oct 2020 at 19:15, Adrian Blake notifications@github.com wrote:
dfu-suffix had the wrong product id , changed, but that did not help. I have tried again on a windows machine to write the code without success. Windows device manager "This device cannot start"
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-705109080, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT7BQQOK3YEITNJCRI3SJSV4DANCNFSM4SATZ22A .
dmesg shows: New USB device found, idVendor=1209, idProduct=5bf0, bcdDevice= 1.01
That USB is the same as I have.
Need to know what the parameters are for the command: dfu-suffix -v 1209 -p 70b1 -a build.dfu
On Thu, 8 Oct 2020 at 15:29, Adrian Blake notifications@github.com wrote:
dmesg shows: New USB device found, idVendor=1209, idProduct=5bf0, bcdDevice= 1.01
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-705609285, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT234UUSFXECUD2JMG3SJXEDPANCNFSM4SATZ22A .
Some success ...... Upgraded to bootloader v2.0.2 I uploaded the forth ... same error hmmmm This time I kept GTKterm running and uploaded forth again ... then in GTKterm I see the "ok" prompt. Take out FPGA and put in again ... not working I need to upload forth, but terminal programme must be running, if not when I start it then ttyACM0 is lost .. or .. rather the initialisation of the the port "upsets" the FPGA. So, am I missing something in the necessary steps for successful operation. BTW "ledtest" works.
Good news on the ledtest
I've always been able to start the terminal program after the upload of the dfu file. Have you tried using putty?
Rob.
On Sun, 11 Oct 2020 at 16:10, Adrian Blake notifications@github.com wrote:
Some success ...... Upgraded to bootloader v2.0.2 I uploaded the forth ... same error hmmmm This time I kept GTKterm running and uploaded forth again ... then in GTKterm I see the "ok" prompt. Take out FPGA and put in again ... not working I need to upload forth, but terminal programme must be running, if not when I start it then ttyACM0 is lost .. or .. rather the initialisation of the the port "upsets" the FPGA. So, am I missing something in the necessary steps for successful operation. BTW "ledtest" works.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-706719152, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT6E2RKEUSIMNEFGS4TSKHDGFANCNFSM4SATZ22A .
Problem partially solved. It would appear that the serial port implementation is the problem. It can be resolved later. I can now at least have fun and learn more about fpga programming and try to extend the capabilities of this eforth. Adrian
Excellent news. Thanks for looking into this Adrian. I'm sorry I've not been able to help as much as I could. Hopefully, a solution to the USB UART can be found.
On Thu, 15 Oct 2020 at 18:40, Adrian Blake notifications@github.com wrote:
Problem partially solved. It would appear that the serial port implementation is the problem. It can be resolved later. I can now at least have fun and learn more about fpga programming and try to extend the capabilities of this eforth. Adrian
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-709483666, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT4YLZRLAXZ7HNEUAKTSK4XYXANCNFSM4SATZ22A .
Do you have time to talk on Whatsapp or Skype to help me understand in detail the Silice code ? Adrian
I can't at the moment, as we have a friend staying with us for the weekend. I'll see what I can do next week.
Rob.
On Fri, 16 Oct 2020 at 14:56, Adrian Blake notifications@github.com wrote:
Do you have time to talk on Whatsapp or Skype to help me understand in detail the Silice code ? Adrian
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rob-ng15/Silice-Playground/issues/1#issuecomment-710063033, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN4SYT6DOD7WQZ7M4HTZYBLSLBGIBANCNFSM4SATZ22A .
OK,
when trying to build I get an error: -- Parsing
build.v' using frontend
verilog' -- ERROR: Can't open input file `build.v' for reading: No such file or directory ERROR: Failed to open JSON file 'build.json'. 0 warnings, 1 error but this is because it cannot find silice. Where, what directory, should the project be located given that silice is in $HOME/silice/bin ... the default location? can I install the silice exectutable into something like /usr/local/bin ?