Closed emanueledelsozzo closed 8 years ago
You may have version skew between connectal and the drivers in zynq-boot. We're adding a runtime check so that android.exe can query the driver to make sure that they are in sync.
If you run "adb shell ls /dev/portal*", are there entries such as /dev/portal_0_1 ?
Are you installing connectal from the Ubuntu packages or from git? I generally recommend the packages.
If I run "adb shell ls /dev/portal*", there are no entries such /dev/portal_0_1. After I load the kernel modules portalmem.ko and zynqportal.ko, the new entries in /dev/ are just portalmem and connectal. Am I missing something? I am using the Connectal IDE web interface in order to generate the bitstream and android.exe and load them on the zedboard. I am trying the led example. The bitstream gets loaded on the zedboard (the blue led lights up on the board), but, when it is time to execute android.exe, it just returns me the error I posted previously. I also tried the run.android script, but the result is the same.
I need to update the version of connectal installed on the build server to match the most recent zynq-boot. Done. Please rebuild the example and give it another try. I will run a test also.
On Wed, Apr 1, 2015 at 4:51 AM emanuele notifications@github.com wrote:
If I run "adb shell ls /dev/portal*", there are no entries such /dev/portal_0_1. After I load the kernel modules portalmem.ko and zynqportal.ko, the new entries in /dev/ are just portalmem and connectal. Am I missing something? I am using the Connectal IDE web interface in order to generate the bitstream and android.exe and load them on the zedboard. I am trying the led example. The bitstream gets loaded on the zedboard (the blue led lights up on the board), but, when it is time to execute android.exe, it just returns me the error I posted previously. I also tried the run.android script, but the result is the same.
— Reply to this email directly or view it on GitHub https://github.com/cambridgehackers/zynq-boot/issues/3#issuecomment-88399201 .
Ok, thank you. I won't get access to the zedboard until next week. If you could give me a feedback about your test, I would be glad. Just one last question: maybe I am missing something but it is still not clear to me which kernel module is in charge of loading portal_0_1 in /dev/. I thought it was zynqportal.ko, but it just loads /dev/connectal.
zynqportal implements /dev/connectal and /dev/portal*, but it does not probe the programmable logic until /dev/connectal is opened.
In the current version of connectal, the bitstream is embedded into android.exe, which runs fpgajtag to program the logic (via /dev/xdevcfg) and to read /dev/connectal and wait until the /dev/portal* entries are created.
On Wed, Apr 1, 2015 at 7:19 AM emanuele notifications@github.com wrote:
Ok, thank you. I won't get access to the zedboard until next week. If you could give me a feedback about your test, I would be glad. Just one last question: maybe I am missing something but it is still not clear to me which kernel module is in charge of loading portal_0_1 in /dev/. I thought it was zynqportal.ko, but it just loads /dev/connectal.
— Reply to this email directly or view it on GitHub https://github.com/cambridgehackers/zynq-boot/issues/3#issuecomment-88444648 .
The sequence is: 1) insmod zynqportal.ko, creating /dev/connectal 2) run android.exe, which: 2.1) runs /mnt/sdcard/fpgajtag -x android.exe, which programs the fpga 2.2) opens, reads /dev/connectal, which causes zynqportal to: 2.2.1) scan fixed addresses on the GP0 AXI port from the ARM processor to the FPGA design 2.2.2) for each portal it discovers, zynqportal creates /dev/portal_0_xx, where xx is portal number in decimal 2.3) when (2.2) is done, the design opens /dev/portal_0_xx for each portal it is using.
Although we have automated a bunch of steps into android.exe startup, they can each be run manually: a) /mnt/sdcard/fpgajtag -x android.exe , to program the device b) cat /dev/connectal , causes the directory to be read linux devices to be created c) ls /dev/portal_* shows what devices the fpga design supports
Does this help? jca
On Wed, Apr 1, 2015 at 7:19 AM, emanuele notifications@github.com wrote:
Ok, thank you. I won't get access to the zedboard until next week. If you could give me a feedback about your test, I would be glad. Just one last question: maybe I am missing something but it is still not clear to me which kernel module is in charge of loading portal_0_1 in /dev/. I thought it was zynqportal.ko, but it just loads /dev/connectal.
— Reply to this email directly or view it on GitHub https://github.com/cambridgehackers/zynq-boot/issues/3#issuecomment-88444648 .
Thank you for your help guys! I'll try as soon as possible!
Are you using the buildbot interface (build.connectal.org)?
Or are you using build.connectal.org/ui/index.html ?
On Wed, Apr 1, 2015 at 10:43 AM emanuele notifications@github.com wrote:
Thank you for your help guys! I'll try as soon as possible!
— Reply to this email directly or view it on GitHub https://github.com/cambridgehackers/zynq-boot/issues/3#issuecomment-88510247 .
I am using build.connectal.org/ui/index.html
When I had a chance to test it this afternoon, it would not even build. I'm moving it to a new server, and now it is building. Tomorrow I will verify that the executables it builds run on zedboard and zybo.
Great! So, I wait your news, thanks!
Hello, sorry for the delay! I am trying to make the led example work without success. If I use Connectal IDE, when I try to run the example, it tells me: "Error running sh: No such file or directory". On the other hand, if I try manually, when i type: "cat /dev/connectal", it returns me "connectal_open:407" and then I cannot insert any other command, it is like the shell freezes or something. What do you suggest me to do?
Hi,
Sorry for the delay in looking into this problem.
We reduced the steps required to run android.exe and I had not updated the web client to match.
I'm moving the web client to a new server, and that also caused problems.
However, I was just able to build and run examples/simple from the connectal repo on a local zybo.
Please try http://ide.connectal.org/index.html and let me know if it works for you.
On Wed, Apr 15, 2015 at 6:44 AM emanuele notifications@github.com wrote:
Hello, sorry for the delay! I am trying to make the led example work without success. If I use Connectal IDE, when I try to run the example, it tells me: "Error running sh: No such file or directory". On the other hand, if I try manually, when i type: "cat /dev/connectal", it returns me "connectal_open:407" and then I cannot insert any other command, it is like the shell freezes or something. What do you suggest me to do?
— Reply to this email directly or view it on GitHub https://github.com/cambridgehackers/zynq-boot/issues/3#issuecomment-93317340 .
Hi, if I try to build the led example using the link you provided me, it returns me this error during the building phase:
Error: "/home/ubuntu/webui/user38195/leds/Top.bsv", line 29, column 8: (S0000)
Cannot find package MemPortal' Error: "./LedControllerRequest.bsv", line 26, column 8: (S0000) Cannot find package
MemPortal'
make[1]: * [verilog/mkZynqTop.v] Error 1
make: * [build.zedboard] Error 2
None
2
That example was out of date. I updated it so it builds and runs in bluesim. Out network is partially disassembled so I cannot test it on zedboard right now.
On Thu, Apr 16, 2015 at 5:14 PM emanuele notifications@github.com wrote:
Hi, if I try to build the led example using the link you provided me, it returns me this error during the building phase:
Error: "/home/ubuntu/webui/user38195/leds/Top.bsv", line 29, column 8: (S0000) Cannot find package MemPortal' Error: "./LedControllerRequest.bsv", line 26, column 8: (S0000) Cannot find packageMemPortal' make[1]: * [verilog/mkZynqTop.v] Error 1 make: * [build.zedboard] Error 2 None 2
— Reply to this email directly or view it on GitHub https://github.com/cambridgehackers/zynq-boot/issues/3#issuecomment-93841097 .