| 00:03 | Bertl | again, ideally adjustments are done all the time, e.g during idle periods
|
| 00:03 | Bertl | but for a start, that's probably fine
|
| 00:05 | apurvanandan[m] | okay
|
| 01:46 | Nira | changed nick to: Nira|away
|
| 02:16 | apurvanandan[m] | I will try making DDRx4 work again as handling 64bits words from 5 channels is going to be difficult i think
|
| 02:18 | Guest47049 | joined the channel |
| 02:29 | Bertl | okay
|
| 03:22 | Bertl | off to bed now ... have a good one everyone!
|
| 03:22 | Bertl | changed nick to: Bertl_zZ
|
| 03:22 | apurvanandan[m] | Good night
|
| 05:28 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 05:32 | Guest47049 | left the channel |
| 06:56 | illwieckz_ | left the channel |
| 07:12 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 07:18 | illwieckz | joined the channel |
| 08:57 | illwieckz | left the channel |
| 10:14 | aombk | left the channel |
| 13:46 | Bertl_zZ | changed nick to: Bertl
|
| 13:46 | Bertl | morning folks!
|
| 13:51 | aSobhy | Good morning Bertl :)
|
| 13:54 | aSobhy | I've a question: how can I trace the wire from the MaxhXO2 to ZYNQ?
|
| 13:56 | aSobhy | I want to connect the LVDS wires and the reset from the pins I specified at the MachXO2 side to the corresponding ZYNQ pins
|
| 13:58 | Bertl | ah, you need to check the wire names on the schematic
|
| 13:58 | Bertl | they use similar names to the MicroZed names
|
| 13:59 | aSobhy | that's great :)
|
| 13:59 | Bertl | for the RFW it is BANK13_01_{P,N}
|
| 14:00 | Bertl | for the RFE JX1_05_{P,N} and JX2_04_{P,N}
|
| 14:00 | Bertl | (for the LVDS)
|
| 14:00 | aSobhy | yes yes I found them
|
| 14:01 | Bertl | for the MicroZed there is a pinout table
|
| 14:01 | Bertl | where you can see the Zynq Pin numbers for each name
|
| 14:02 | Bertl | there the names are slightly longer with _LVDS_ between JX1/JX2/BANK13 and the number
|
| 14:03 | aSobhy | OK
|
| 14:04 | Bertl | all sorted or something still missing?
|
| 14:05 | aSobhy | yeah their is another question
|
| 14:05 | Bertl | let's hear then
|
| 14:07 | aSobhy | I cant find the pins name of the top module as to continue assigning as in the user guide
|
| 14:07 | aSobhy | the top module doesn't show its pins in the Netlist
|
| 14:09 | aSobhy | I've created a top file top hold the train file(main) and the output was the same
|
| 14:09 | aSobhy | It makes it nested and didn't show the pins?!!
|
| 14:10 | aSobhy | I'm following that
|
| 14:10 | aSobhy | https://www.xilinx.com/support/documentation/sw_manuals/xilinx2012_2/ug945-vivado-using-constraints-tutorial.pdf
|
| 14:10 | Bertl | okay, please upload/commit the project, I'll take a look
|
| 14:10 | Bertl | (paste a link here or via pm)
|
| 14:12 | aSobhy | yeah Its up to date
|
| 14:12 | aSobhy | https://github.com/aabdosobhy/Bi-Direction-packet-protocol/tree/master/Training/ZYNQ
|
| 14:28 | Bertl | the tcl script fails here for me
|
| 14:28 | Bertl | ERROR: [Common 17-53] User Exception: No open project. Please use Save Project As to save your work and re-do this operation.
|
| 14:28 | Bertl | what vivado version do you use and how do you build it?
|
| 14:30 | aSobhy | 17.4
|
| 14:31 | Bertl | okay, that's the same here
|
| 14:32 | Bertl | vivado -mode tcl -source vivado.tcl
|
| 14:32 | Bertl | (is what I used)
|
| 14:35 | aSobhy | actually I don't use the tcl for now
|
| 14:35 | aSobhy | its doing the same thing at my side
|
| 14:35 | Bertl | so how do you build it?
|
| 14:36 | aSobhy | from the GUI
|
| 14:36 | Bertl | don't see any project file either
|
| 14:37 | Bertl | please give some instructions how to replicate your issue
|
| 14:40 | aSobhy | OK I'll fix the TCL file
|
| 15:07 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 17:07 | illwieckz | joined the channel |
| 17:23 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 17:57 | Bertl | off for now ... bbl
|
| 17:57 | Bertl | changed nick to: Bertl_oO
|
| 18:43 | Fares | joined the channel |
| 19:02 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 20:01 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 20:01 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 20:07 | Fares | left the channel |
| 20:08 | Fares | joined the channel |
| 20:10 | Fares | left the channel |
| 20:15 | Bertl_oO | changed nick to: Bertl
|
| 20:16 | Bertl | aSobhy: what's the status?
|
| 21:16 | aSobhy | I generated the TCL using:
|
| 21:16 | aSobhy | write_project_tcl top.tcl
|
| 21:16 | aSobhy | It generates the tcl but It is for my pc only with my paths I tried with absolute_path It is the same with little changes
|
| 21:17 | Bertl | so what is the plan now?
|
| 21:18 | aSobhy | I'm trying to set them like in that file https://github.com/apertus-open-source-cinema/axiom-beta-firmware/blob/master/peripherals/soc_main/pin_spi_ibc.xdc
|
| 21:18 | Bertl | which obviously works
|
| 21:20 | aSobhy | and Its running now I'll tell you if it fails or pass after it finishes
|
| 21:20 | aSobhy | ok I hope so
|
| 21:20 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 21:20 | Bertl | so I'm more curious, how do you plan to address the 'nobody except you can build your project' part?
|
| 21:22 | aSobhy | I didn't catch !
|
| 21:22 | Bertl | currently your repository is useless as nobody (except you) can rebuild it
|
| 21:22 | Bertl | how do you plan to change this?
|
| 21:26 | aSobhy | It took alot of time and I managed to fix it after that test
|
| 21:26 | Bertl | so it can now be built by somebody else?
|
| 21:26 | aSobhy | should it differ from windows to Linux
|
| 21:27 | aSobhy | I think no
|
| 21:27 | Bertl | depends on what you did :)
|
| 21:28 | Bertl | in any case, it would be a good idea to setup a Linux VM and install the tools there to simply test your repository when you think it 'should work'
|
| 21:29 | aSobhy | but "write_project_tcl" generates the tcl with the local paths from my pc
|
| 21:29 | aSobhy | should I remove it manually ?
|
| 21:30 | aSobhy | by comparing it with the file vivado.tcl it has the absolute paths
|
| 21:31 | Bertl | personally I'd suggest you write the build tcl yourself
|
| 21:31 | aSobhy | I have linux beside windows but I failed to install it
|
| 21:31 | Bertl | similar to the vivado.tcl used in the AXIOM Beta sources
|
| 21:32 | Bertl | but of course you can adjust the generated tcl as well as long as it works
|
| 21:36 | aSobhy | ok I'll give a try that night
|
| 21:36 | Bertl | "but I failed to install it": what didn't work?
|
| 21:37 | aSobhy | It takes too much time installation comparing to the time it takes on windows
|
| 21:37 | aSobhy | and its the offline version
|
| 21:39 | Bertl | I don't know how long the Microsoft Windows version takes, but the Linux version took about 8 minutes for a complete install here
|
| 21:39 | Bertl | (talking about Vivado)
|
| 21:40 | aSobhy | it take about 2 hours so I terminate it on ubuntu
|
| 21:40 | aSobhy | yes I'm talking about Vivado
|
| 21:41 | Bertl | was that in a VM or on real hardware?
|
| 21:42 | aSobhy | real HW
|
| 21:42 | aSobhy | windows along side with ubuntu 18
|
| 21:42 | Bertl | that sounds very unusual, you sure you didn't run out of memory or disk space?
|
| 21:43 | Bertl | I know that Vivado is quite demanding (space wise)
|
| 21:43 | aSobhy | I give ubuntu 100 GB
|
| 21:43 | aSobhy | gave*
|
| 21:44 | Bertl | that should suffice
|
| 21:44 | aSobhy | and tried with ubuntu 16 & 18
|
| 21:45 | Bertl | maybe next time try with a different distro
|
| 21:46 | Bertl | also check the Xilinx forum for installation issues
|
| 21:46 | Bertl | I remember that there have been some problems with certain releases
|
| 22:09 | illwieckz_ | joined the channel |
| 22:12 | illwieckz | left the channel |
| 22:14 | aSobhy | the run failed :/
|
| 22:14 | aSobhy | the pins didn't change from their places
|
| 22:14 | aSobhy | I'll fix the tcl file so you can help me
|
| 22:15 | Bertl | please do so
|
| 22:15 | Bertl | let me know when you encounter issues with the tcl
|
| 22:17 | aSobhy | OK I'm on it now
|