{"action":"created","issue":{"url":"https://api.github.com/repos/nvdla/hw/issues/110","repository_url":"https://api.github.com/repos/nvdla/hw","labels_url":"https://api.github.com/repos/nvdla/hw/issues/110/labels{/name}","comments_url":"https://api.github.com/repos/nvdla/hw/issues/110/comments","events_url":"https://api.github.com/repos/nvdla/hw/issues/110/events","html_url":"https://github.com/nvdla/hw/issues/110","id":309539120,"node_id":"MDU6SXNzdWUzMDk1MzkxMjA=","number":110,"title":"NVDLA running on a FPGA platform","user":{"login":"ratnayak","id":35048817,"node_id":"MDQ6VXNlcjM1MDQ4ODE3","avatar_url":"https://avatars1.githubusercontent.com/u/35048817?v=4","gravatar_id":"","url":"https://api.github.com/users/ratnayak","html_url":"https://github.com/ratnayak","followers_url":"https://api.github.com/users/ratnayak/followers","following_url":"https://api.github.com/users/ratnayak/following{/other_user}","gists_url":"https://api.github.com/users/ratnayak/gists{/gist_id}","starred_url":"https://api.github.com/users/ratnayak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ratnayak/subscriptions","organizations_url":"https://api.github.com/users/ratnayak/orgs","repos_url":"https://api.github.com/users/ratnayak/repos","events_url":"https://api.github.com/users/ratnayak/events{/privacy}","received_events_url":"https://api.github.com/users/ratnayak/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":68,"created_at":"2018-03-28T21:30:28Z","updated_at":"2018-10-24T07:43:29Z","closed_at":null,"author_association":"NONE","body":"This is an inquiry to the wider audience who are working on getting NVDLA running on a FPGA platform--we'd like to share what we are doing and check progress on other groups out there .\r\n\r\nwe are putting nv_full (as nv_small is not available as yet) on Xilinx VU440 (largest FPGA by Xilinx). nv_full fits comfortably on VU440 utilizing about 82% LUTs as per Vivado implementation.\r\nwe'd have the host running on an ARM A53 processor on a Xilinx Zynq (ASIC ARM). the signalling between two FPGAs--Zynq(host) and VU440(nv_full) will be via direct parallel connections (simple & straightforward) and we have enough IOs for this.\r\n\r\na) we'd like to know if anyone out there has already implemented nv_full on a FPGA platform and successful in getting it running as expected.\r\nb) we would very much like to sync w you--either you got it running or still some distance to go-- perhaps we can discuss details, inputs on issues encountered, how resolved them etc.\r\n\r\nlook forward to hearing from you."},"comment":{"url":"https://api.github.com/repos/nvdla/hw/issues/comments/432548349","html_url":"https://github.com/nvdla/hw/issues/110#issuecomment-432548349","issue_url":"https://api.github.com/repos/nvdla/hw/issues/110","id":432548349,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMjU0ODM0OQ==","user":{"login":"mmaciag","id":35990175,"node_id":"MDQ6VXNlcjM1OTkwMTc1","avatar_url":"https://avatars3.githubusercontent.com/u/35990175?v=4","gravatar_id":"","url":"https://api.github.com/users/mmaciag","html_url":"https://github.com/mmaciag","followers_url":"https://api.github.com/users/mmaciag/followers","following_url":"https://api.github.com/users/mmaciag/following{/other_user}","gists_url":"https://api.github.com/users/mmaciag/gists{/gist_id}","starred_url":"https://api.github.com/users/mmaciag/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmaciag/subscriptions","organizations_url":"https://api.github.com/users/mmaciag/orgs","repos_url":"https://api.github.com/users/mmaciag/repos","events_url":"https://api.github.com/users/mmaciag/events{/privacy}","received_events_url":"https://api.github.com/users/mmaciag/received_events","type":"User","site_admin":false},"created_at":"2018-10-24T07:43:29Z","updated_at":"2018-10-24T07:43:29Z","author_association":"NONE","body":"Hi, \r\n\r\nI use following command for petalinux 2017.4, but the locations should be similar in 2018.2. Of course I cross-compile on PC machine.\r\n\r\n```\r\nmake KDIR=<petalinux_root_location>/build/tmp/work-shared/plnx_aarch64/kernel-build-artifacts ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-  && \\\r\n\tsudo cp port/linux/opendla.ko /tftpboot/nfsroot/opt/lib/modules/opendla.ko\r\n```\r\n\r\nAnd the Makefile:\r\n\r\n```\r\nKDIR ?= /lib/modules/`uname -r`/build\r\nMY_CFLAGS := -g -DDEBUG -DVERBOSE_PRINTK -DCONFIG_PRINTK -DDLA_SMALL_CONFIG -Wno-date-time\r\n#\t\tMY_CFLAGS := -DDLA_SMALL_CONFIG\r\n\r\n.PHONY: default\r\ndefault: modules\r\n\r\n%:\r\n\t$(MAKE) -C $(KDIR) M=$$PWD $@ EXTRA_CFLAGS=\"$(MY_CFLAGS)\"\r\n```\r\n\r\nFor UMD I use:\r\n\r\n```\r\nmake TOOLCHAIN_PREFIX=aarch64-linux-gnu- TOP=`pwd`\r\n```\r\n\r\n`aarch64-linux-gnu` resides in $PATH environment variable. It can be found too somewhere in petalinux directories.\r\n"}}
{"actor":{"display_login":"mmaciag"}}