profile
viewpoint
Qingyao Sun nalzok East China Normal University Shanghai, China A STAT major obsessed with machines.

AtomXT/ECNU-Course-Info 6

提供课程相关信息,便于ECNUer选课。

nalzok/Flask-CAS-ECNU 1

Flask extension for CAS

nalzok/kernod 1

A Q&A website written in C

nalzok/ok 1

ok.py supports programming projects by running tests, tracking progress, and assisting in debugging.

ecnu-stju/ecnu1 0

reservation

nalzok/Cal61CforFun 0

Get hands dirty learning 61C

nalzok/chisel-bootcamp 0

Generator Bootcamp Material: Learn Chisel the Right Way

startedProsusAI/finBERT

started time in 14 hours

startedguannan-he/Antminer_s9_pynq

started time in 3 days

startedMustangYM/WeChatExtension-ForMac

started time in 5 days

startedfedorova/pm

started time in 8 days

startedjanestreet/hardcaml

started time in 8 days

startedrclone/rclone

started time in 17 days

startedludovicchabant/vim-gutentags

started time in 19 days

issue commentloboris/MicroPython_K210_LoBo

Cannot flash the WiFi firmware to M1W

I have successfully flashed the firmware to the internal ESP8285 after soldering the pins. It took me tens of tries before finally succeeded, so you probably need to re-run the flash script a few times. In fact, I didn't follow the instruction in README thoroughly. The commands given are

./flash.sh -eo -t 1MB -m dout -P /dev/cu.usbserial-1430
./flash.sh -t 1MB -m dout -P /dev/cu.usbserial-1430

The first line will erase the flash, and the second one will erase the flash (yes, erase again) and then flash the firmware. It appears that you cannot erase/flash the device again without doing a power cycle, so I used the following commands instead

./flash.sh -eo -t 1MB -m dout -P /dev/cu.usbserial-1430
./flash.sh -ne -t 1MB -m dout -P /dev/cu.usbserial-1430

The second line now has an additional option -ne, which means "No erase", so it will do the flashing without erasing it again first.

Note that by close visual inspection, the pins touch the pad firmly, so the flashing errors like A fatal error occurred: Timed out waiting for packet header are probably not due to poor contact.

IMG_6442

nalzok

comment created time in 20 days

startedJohannesObermaier/f103-analysis

started time in 25 days

pull request commentolofk/serv

servant: add iCESugar board support

Glad you have found the problem! I can confirms that freq_out : 17 works at the baud rate of 57600 on iCESugar.

Maybe we should also use freq_out : 17 or freq_out : 32 for iCEBreaker? Not sure how things work on that board though, since I don't have an iCEBreaker at hand.

nalzok

comment created time in a month

push eventnalzok/serv

Qingyao Sun

commit sha f491bc456c0693f886279f821d4286650f9107e4

Add instructions for iCESugar to README.md

view details

push time in a month

pull request commentolofk/serv

servant: add iCESugar board support

It turns out that the maximum sampling frequency of my logic analyzer is 24MHz, so I divided the clock by 16 with

reg[3:0] counter = 0;
always @(posedge wb_clk)
begin
    counter <= counter + 1;
end

assign debug = &counter;

With freq_out : 32, the logic analyzer registers

libsigrok 0.6.0-git-400bc4f
Acquisition with 1/8 channels at 24 MHz
D6:00000001 00000000 00010000 00000001 00000000 00010000 00000001 00000000
D6:00010000 00000001 00000000 00010000 00000000 00000000 00000000 00000000
D6:00000000 00000000 00000000 00000000 00001000 00000000 10000000 00001000
D6:00000000 10000000 00001000 00000000 10000000 00001000 00000000 10000000
D6:00001000 00000000 10000000 00001000 00000000 10000000 00001000 00000000
D6:10000000 00001000 00000000 10000000 00000000 00000000 00000000 00000000
D6:00000000 00000000 00000000 00000000 01000000 00000100 00000000 01000000
D6:00000100 00000000 01000000 00000100 00000000 01000000 00000100 00000000

Since there is a 1 for every eleven 0, the frequency of debug is 24HMz / 12 = 2Mhz, and thus the real frequency of the CPU should be 2MHz * 16 = 32Mhz. Seems legitimate to me.

When changing to freq_out : 16, I'm getting

libsigrok 0.6.0-git-400bc4f
Acquisition with 1/8 channels at 24 MHz
D6:00001100 00000000 00000000 00001100 00000000 00000000 00001100 00000000
D6:00000000 00001100 00000000 00000000 00001100 00000000 00000000 00000100
D6:00000000 00000000 00000100 00000000 00000000 00000100 00000000 00000000
D6:00000100 00000000 00000000 00000100 00000000 00000000 00000110 00000000
D6:00000000 00000110 00000000 00000000 00000110 00000000 00000000 00000110
D6:00000000 00000000 00000110 00000000 00000000 00000010 00000000 00000000
D6:00000010 00000000 00000000 00000010 00000000 00000000 00000010 00000000
D6:00000000 00000010 00000000 00000000 00000011 00000000 00000000 00000011

The repetition is roughly two 1 followed by twenty-two 0, so yeah, the "real" clock is about 16MHz. You can see some imperfect repetitions which contains only one 1, though.

In the meantime, I'm happy to accept the PR if you change frequency to 32

The contributed icesugar target already runs at 32HMz. I have updated README.md to clarify.

nalzok

comment created time in a month

pull request commentolofk/serv

servant: add iCESugar board support

It looks like the baud rate is increased from 43200 to 115200 by doubling the PLL output frequency from 16 to 32 MHz. It makes no sense to me.

This is exactly what I have observed! When the CPU runs at 16MHz, the baud rate is ~43200. As soon as I set the CPU clock to 32MHz, the baud rate magically becomes 115200. Doesn't make sense to me too...

I'm going to use the logic analyzerr to find out the "real" CPU clock later!

nalzok

comment created time in a month

startedlingscale/cc01

started time in a month

PR opened olofk/corescore

Add iCESugar target with core score

iCESugar is quite similar to Upduino2, so supporting it didn't take much effort :)

Screen Shot 2020-10-02 at 15 35 52

+106 -0

0 comment

3 changed files

pr created time in a month

push eventnalzok/corescore

Qingyao Sun

commit sha 4d57afc66802487a04dba6f820313498161ed298

Add iCESugar target with core score

view details

push time in a month

fork nalzok/corescore

CoreScore

fork in a month

PR opened olofk/serv

servant: add iCESugar board support
+24 -0

0 comment

2 changed files

pr created time in a month

push eventnalzok/serv

Qingyao Sun

commit sha 8e02772fe0d0239d03f255850a631baf759d51c4

servant: add iCESugar board support

view details

push time in a month

fork nalzok/serv

SERV - The SErial RISC-V CPU

fork in a month

startedkoutto/hardware-hacking

started time in a month

PR opened wuxx/icesugar

Improvements on the PmodOLED example
+20 -32

0 comment

5 changed files

pr created time in a month

push eventnalzok/icesugar

wuxx

commit sha bd329f4b8a751ba64aa01b9cf8d00476b0664732

Merge pull request #10 from nalzok/master Added example for the PmodOLED module

view details

Qingyao Sun

commit sha fd0e3cbff5f88460966681744ce1a387deb79d2b

Merge https://github.com/wuxx/icesugar into master

view details

push time in a month

push eventnalzok/icesugar

Qingyao Sun

commit sha 320c2b915dbdea46c05251957fe38dcae3da9cfb

Improved documentation

view details

push time in a month

push eventnalzok/icesugar

Qingyao Sun

commit sha 1014e879ec134a1dd1e3b9c935c7e28ec1e853cd

Made LED constraints more sensible

view details

push time in a month

push eventnalzok/icesugar

wuxx

commit sha b9021aafd98d51c829f4da4eabd121d18b976185

Merge pull request #7 from nalzok/master Added RGB PWM hard IP example

view details

wuxx

commit sha 04cf15f3cbb57bb82904bb634884cd4072451418

Merge pull request #8 from nalzok/master Improved documentation

view details

wuxx

commit sha 98def124576b239189bac1e6928d1fa4b7f0e774

update README_en.md

view details

Qingyao Sun

commit sha 8a7ba9eb9b7ecddb57cf193cb184084dbd36a3c8

Merge https://github.com/wuxx/icesugar into master

view details

push time in a month

PR opened wuxx/icesugar

Added example for the PmodOLED module
+1035 -0

0 comment

19 changed files

pr created time in a month

push eventnalzok/icesugar

Qingyao Sun

commit sha 44c8d2540dcc5f0632f97d335432b4b70746c3a4

Added example for the PmodOLED module

view details

push time in a month

issue openedpavels/spektrum

Any plan for a macOS release?

Does this software depend on some library which is missing on macOS?

created time in a month

startedrevaldinho/opc

started time in a month

startedthuquant/awesome-quant

started time in a month

issue commentYosysHQ/yosys

Yosys stucks in an infinite loop when running synthesis

for a workaround, try changing the strings used in OledInit.v as state values to enumerated constants with sequential values.

It works! I had to replace the "state strings" in both Oledinit.v and OledEX.v with sequential integers to get yosys to run in a reasonable amount of time, though.

nalzok

comment created time in a month

issue openedYosysHQ/yosys

Yosys stucks in an infinite loop when running synthesis

Steps to reproduce the issue

  1. Download oled.zip
  2. Unzip it and cd into the directory
  3. make

Expected behavior

Some background first: I am trying to use Digilent's Pmod OLED with icesugar, an iCE40UP5k-powered development board by adapting the Nexys 3 Verilog Example - ISE 14.2 example. Chances are that I made some mistake so the attached code won't work, but I still expect yosys to either

  1. produce a JSON netlist on success, or
  2. emit an error on failure.

Actual behavior

It appears to stuck in an infinite loop. I have waited for more than half an hour and it didn't output anything. The last few log lines are

6.3. Executing PROC pass (convert processes to netlists).

6.3.1. Executing PROC_CLEAN pass (remove empty switches from decision trees).
Cleaned up 0 empty switches.

6.3.2. Executing PROC_RMDEAD pass (remove dead branches from decision trees).
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:1330$335 in module SB_DFFNES.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:1274$328 in module SB_DFFNESS.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:1199$324 in module SB_DFFNER.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:1143$317 in module SB_DFFNESR.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:1074$314 in module SB_DFFNS.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:1026$311 in module SB_DFFNSS.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:957$308 in module SB_DFFNR.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:909$305 in module SB_DFFNSR.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:753$297 in module SB_DFFES.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:697$290 in module SB_DFFESS.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:622$286 in module SB_DFFER.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:566$279 in module SB_DFFESR.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:497$276 in module SB_DFFS.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:449$273 in module SB_DFFSS.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:380$270 in module SB_DFFR.
Marked 1 switch rules as full_case in process $proc$/usr/local/bin/../share/yosys/ice40/cells_sim.v:332$267 in module SB_DFFSR.

created time in a month

startedlyhue1991/eat_pytorch_in_20_days

started time in a month

fork nalzok/eat_pytorch_in_20_days

Pytorch🍊🍉 is delicious, just eat it! 😋😋

fork in a month

issue commentYosysHQ/apicula

Update documentation

You mean I can contribute by just running a Docker image on my MacBook? That's cool. Will contribute some computational power when the instructions on how to contribute with Docker is ready :P

pepijndevos

comment created time in a month

issue commentYosysHQ/apicula

Update documentation

A quick demo of how to use this project would be nice. I'm on macOS so it's impossible to install the GoWin IDE as the current README instructs, but ideally this project should enables a cross-platform toolchain for GoWin FPGAs, just like Project IceStorm does for ICE40?

pepijndevos

comment created time in a month

issue openedYosysHQ/yosys

ERROR: Can't guess frontend for input file `-ql' (missing -f option)!

Steps to reproduce the issue

make test > test.log 2&>1

I'm using fish shell, so the stdout and stderr redirection syntax is a little different, but you get the idea.

Expected behavior

No errors

Actual behavior

created time in a month

issue commentmdegans/nano_build_opencv

Test failed with Jetpack 4.4 [L4T 32.4.3] and OpenCV 4.4.0

Thanks for the timely response!

I tried to fix the issue myself by modifying your script to this. I commented out the "prepare for the build" part and manually clone the opencv, opencv_contrib and opencv_extra repositories under the directory /home/qingyao/opencv instead, so that when something goes wrong I don't have to re-clone them again. The build script is also placed in /home/qingyao/opencv.

I have changed CMAKEFLAGS to enable more features, which may or may not have something to do with the error I got later. (Yeah I know that will cause more trouble for you to reproduce the issue. Sorry about that ):

The additional dependencies I installed (mostly for -D BUILD_DOCS=ON) are

sudo apt install doxygen graphviz openblas python-pip
pip install beautifulsoup4

I mounted a 4GB swap file and start the building process with ./build_opencv.sh foo test (the first argument is ignore now). It took ~12 hours to finish on my Jetson Nano. This time, tests took longer to run, but many eventually still failed.

You may download the full test report here. It's a 134.1 MB zip file including some image files.

There are a lot of different errors, but the "cuDNN did not return a suitable algorithm for convolution" error gets the most exposure. Here is an example of what it looks like

test-reports/accuracy/opencv_test_dnn.xml
8174:      <failure message="unknown file&#x0A;C++ exception with description &quot;OpenCV(4.4.0) /home/qingyao/opencv/opencv/modules/dnn/src/layers/../cuda4dnn/primitives/../csl/cudnn/convolution.hpp:303: error: (-217:Gpu API call) cuDNN did not return a suitable algorithm for convolution. in function &apos;ConvolutionAlgorithm&apos;&#x0A;&quot; thrown in the test body." type=""><![CDATA[unknown file
8440:      <failure message="unknown file&#x0A;C++ exception with description &quot;OpenCV(4.4.0) /home/qingyao/opencv/opencv/modules/dnn/src/layers/../cuda4dnn/primitives/../csl/cudnn/convolution.hpp:303: error: (-217:Gpu API call) cuDNN did not return a suitable algorithm for convolution. in function &apos;ConvolutionAlgorithm&apos;&#x0A;&quot; thrown in the test body." type=""><![CDATA[unknown file
8677:      <failure message="/home/qingyao/opencv/opencv/modules/dnn/test/test_common.impl.hpp:70&#x0A;Expected: (normL1) &lt;= (l1), actual: nan vs 1e-05" type=""><![CDATA[/home/qingyao/opencv/opencv/modules/dnn/test/test_common.impl.hpp:70
8684:      <failure message="/home/qingyao/opencv/opencv/modules/dnn/test/test_common.impl.hpp:70&#x0A;Expected: (normL1) &lt;= (l1), actual: nan vs 0.004" type=""><![CDATA[/home/qingyao/opencv/opencv/modules/dnn/test/test_common.impl.hpp:70
9230:      <failure message="unknown file&#x0A;C++ exception with description &quot;OpenCV(4.4.0) /home/qingyao/opencv/opencv/modules/dnn/src/layers/../cuda4dnn/primitives/../csl/cudnn/convolution.hpp:303: error: (-217:Gpu API call) cuDNN did not return a suitable algorithm for convolution. in function &apos;ConvolutionAlgorithm&apos;&#x0A;&quot; thrown in the test body." type=""><![CDATA[unknown file
9335:      <failure message="unknown file&#x0A;C++ exception with description &quot;OpenCV(4.4.0) /home/qingyao/opencv/opencv/modules/dnn/src/layers/../cuda4dnn/primitives/../csl/cudnn/convolution.hpp:303: error: (-217:Gpu API call) cuDNN did not return a suitable algorithm for convolution. in function &apos;ConvolutionAlgorithm&apos;&#x0A;&quot; thrown in the test body." type=""><![CDATA[unknown file

However, the OpenCV installation appears good

qingyao@jetson:~/opencv/opencv/build$ opencv_version --verbose

General configuration for OpenCV 4.4.0 =====================================
  Version control:               4.4.0

  Extra modules:
    Location (extra):            /home/qingyao/opencv/opencv_contrib/modules
    Version control (extra):     4.4.0

  Platform:
    Timestamp:                   2020-09-13T04:59:57Z
    Host:                        Linux 4.9.140-tegra aarch64
    CMake:                       3.10.2
    CMake generator:             Unix Makefiles
    CMake build tool:            /usr/bin/make
    Configuration:               RELEASE

  CPU/HW features:
    Baseline:                    NEON FP16
      required:                  NEON
      disabled:                  VFPV3

  C/C++:
    Built as dynamic libs?:      YES
    C++ standard:                11
    C++ Compiler:                /usr/bin/c++  (ver 7.5.0)
    C++ flags (Release):         -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wsuggest-override -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -fvisibility-inlines-hidden -fopenmp -O3 -DNDEBUG  -DNDEBUG
    C++ flags (Debug):           -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wsuggest-override -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -fvisibility-inlines-hidden -fopenmp -g  -O0 -DDEBUG -D_DEBUG
    C Compiler:                  /usr/bin/cc
    C flags (Release):           -fsigned-char -W -Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -fopenmp -O3 -DNDEBUG  -DNDEBUG
    C flags (Debug):             -fsigned-char -W -Wall -Werror=return-type -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections    -fvisibility=hidden -fopenmp -g  -O0 -DDEBUG -D_DEBUG
    Linker flags (Release):      -Wl,--gc-sections -Wl,--as-needed
    Linker flags (Debug):        -Wl,--gc-sections -Wl,--as-needed
    ccache:                      NO
    Precompiled headers:         NO
    Extra dependencies:          m pthread cudart_static -lpthread dl rt nppc nppial nppicc nppicom nppidei nppif nppig nppim nppist nppisu nppitc npps cublas cudnn cufft -L/usr/local/cuda/lib64 -L/usr/lib/aarch64-linux-gnu
    3rdparty dependencies:

  OpenCV modules:
    To be built:                 alphamat aruco bgsegm bioinspired calib3d ccalib core cudaarithm cudabgsegm cudacodec cudafeatures2d cudafilters cudaimgproc cudalegacy cudaobjdetect cudaoptflow cudastereo cudawarping cudev datasets dnn dnn_objdetect dnn_superres dpm face features2d flann freetype fuzzy gapi hfs highgui img_hash imgcodecs imgproc intensity_transform line_descriptor ml objdetect optflow phase_unwrapping photo plot python2 python3 quality rapid reg rgbd saliency shape stereo stitching structured_light superres surface_matching text tracking ts video videoio videostab xfeatures2d ximgproc xobjdetect xphoto
    Disabled:                    world
    Disabled by dependency:      -
    Unavailable:                 cnn_3dobj cvv hdf java js julia matlab ovis sfm viz
    Applications:                tests perf_tests examples apps
    Documentation:               doxygen python
    Non-free algorithms:         YES

  GUI:
    GTK+:                        YES (ver 3.22.30)
      GThread :                  YES (ver 2.56.4)
      GtkGlExt:                  NO
    OpenGL support:              NO
    VTK support:                 NO

  Media I/O:
    ZLib:                        /usr/lib/aarch64-linux-gnu/libz.so (ver 1.2.11)
    JPEG:                        /usr/lib/aarch64-linux-gnu/libjpeg.so (ver 80)
    WEBP:                        build (ver encoder: 0x020f)
    PNG:                         /usr/lib/aarch64-linux-gnu/libpng.so (ver 1.6.34)
    TIFF:                        /usr/lib/aarch64-linux-gnu/libtiff.so (ver 42 / 4.0.9)
    JPEG 2000:                   build Jasper (ver 1.900.1)
    OpenEXR:                     build (ver 2.3.0)
    HDR:                         YES
    SUNRASTER:                   YES
    PXM:                         YES
    PFM:                         YES

  Video I/O:
    DC1394:                      YES (2.2.5)
    FFMPEG:                      YES
      avcodec:                   YES (57.107.100)
      avformat:                  YES (57.83.100)
      avutil:                    YES (55.78.100)
      swscale:                   YES (4.8.100)
      avresample:                YES (3.7.0)
    GStreamer:                   YES (1.14.5)
    v4l/v4l2:                    YES (linux/videodev2.h)

  Parallel framework:            OpenMP

  Trace:                         YES (with Intel ITT)

  Other third-party libraries:
    Lapack:                      YES (/opt/OpenBLAS/lib/libopenblas.so)
    Eigen:                       YES (ver 3.3.4)
    Custom HAL:                  YES (carotene (ver 0.0.1))
    Protobuf:                    build (3.5.1)

  NVIDIA CUDA:                   YES (ver 10.2, CUFFT CUBLAS FAST_MATH)
    NVIDIA GPU arch:             53 62 72
    NVIDIA PTX archs:

  cuDNN:                         YES (ver 8.0)

  OpenCL:                        YES (no extra features)
    Include path:                /home/qingyao/opencv/opencv/3rdparty/include/opencl/1.2
    Link libraries:              Dynamic load

  Python 2:
    Interpreter:                 /usr/bin/python2.7 (ver 2.7.17)
    Libraries:                   /usr/lib/aarch64-linux-gnu/libpython2.7.so (ver 2.7.17)
    numpy:                       /usr/lib/python2.7/dist-packages/numpy/core/include (ver 1.13.3)
    install path:                lib/python2.7/dist-packages/cv2/python-2.7

  Python 3:
    Interpreter:                 /usr/bin/python3 (ver 3.6.9)
    Libraries:                   /usr/lib/aarch64-linux-gnu/libpython3.6m.so (ver 3.6.9)
    numpy:                       /home/qingyao/.local/lib/python3.6/site-packages/numpy/core/include (ver 1.19.1)
    install path:                lib/python3.6/dist-packages/cv2/python-3.6

  Python (for build):            /usr/bin/python2.7

  Java:
    ant:                         NO
    JNI:                         NO
    Java wrappers:               NO
    Java tests:                  NO

  Install to:                    /usr/local
-----------------------------------------------------------------

The Python binding looks good as well

qingyao@jetson:~/opencv/opencv/build$ python3
Python 3.6.9 (default, Jul 17 2020, 12:50:27)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cv2
>>> cv2.__version__
'4.4.0'
>>> cv2.cuda.printCudaDeviceInfo(0)
*** CUDA Device Query (Runtime API) version (CUDART static linking) ***

Device count: 1

Device 0: "NVIDIA Tegra X1"
  CUDA Driver Version / Runtime Version          10.20 / 10.20
  CUDA Capability Major/Minor version number:    5.3
  Total amount of global memory:                 3964 MBytes (4156780544 bytes)
  GPU Clock Speed:                               0.92 GHz
  Max Texture Dimension Size (x,y,z)             1D=(65536), 2D=(65536,65536), 3D=(4096,4096,4096)
  Max Layered Texture Size (dim) x layers        1D=(16384) x 2048, 2D=(16384,16384) x 2048
  Total amount of constant memory:               65536 bytes
  Total amount of shared memory per block:       49152 bytes
  Total number of registers available per block: 32768
  Warp size:                                     32
  Maximum number of threads per block:           1024
  Maximum sizes of each dimension of a block:    1024 x 1024 x 64
  Maximum sizes of each dimension of a grid:     2147483647 x 65535 x 65535
  Maximum memory pitch:                          2147483647 bytes
  Texture alignment:                             512 bytes
  Concurrent copy and execution:                 Yes with 1 copy engine(s)
  Run time limit on kernels:                     Yes
  Integrated GPU sharing Host Memory:            Yes
  Support host page-locked memory mapping:       Yes
  Concurrent kernel execution:                   Yes
  Alignment requirement for Surfaces:            Yes
  Device has ECC support enabled:                No
  Device is using TCC driver mode:               No
  Device supports Unified Addressing (UVA):      Yes
  Device PCI Bus ID / PCI location ID:           0 / 0
  Compute Mode:
      Default (multiple host threads can use ::cudaSetDevice() with device simultaneously)

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version  = 10.20, CUDA Runtime Version = 10.20, NumDevs = 1

>>> 
nalzok

comment created time in 2 months

issue openedmdegans/nano_build_opencv

Test failed with Jetpack 4.4 [L4T 32.4.3] and OpenCV 4.4.0

I'm building OpenCV 4.4.0 headlessly on a Jetson Nano with Jetpack 4.4 [L4T 32.4.3]. The build is successful but many tests failed. See attached logs.

build.log test.log install.log test-reports.zip

Apparently the cause is multiple missing input files like ./gpu/opticalflow/frame0.png. Any tips?

created time in 2 months

issue commentluxonis/depthai-hardware

BW1092: DepthAI ESP32 Reference Design | Embedded DepthAI Reference Design

Looks great! Is there any chance that we'll get a case for the WiFi variant?

Luxonis-Brandon

comment created time in 2 months

starteddexterleng/vimac

started time in 2 months

startedjschauma/cs631apue

started time in 2 months

PR opened wuxx/icesugar

Improved documentation
+18 -5

0 comment

20 changed files

pr created time in 2 months

push eventnalzok/icesugar

Qingyao Sun

commit sha ca2b79b7b16c3abb8c9e0a483e0c830543e65909

Improved documentation coverage

view details

Qingyao Sun

commit sha 7fe55a288ae295ce73e637e6c593dd6aedb41e1b

Added instructions for using prebuilt toolchains

view details

push time in 2 months

push eventnalzok/icesugar

Qingyao Sun

commit sha dc6f5220eaae646d45c1ad830fd564cd14440a3c

Retab

view details

push time in 2 months

push eventnalzok/icesugar

Qingyao Sun

commit sha 121b5f023d467c1ce3c6bc7afde666b8e0f04b34

Improved documentation for RGB PWM hard IP

view details

push time in 2 months

PR opened wuxx/icesugar

Added RGB PWM hard IP example
+209 -0

0 comment

2 changed files

pr created time in 2 months

push eventnalzok/icesugar

Qingyao Sun

commit sha 228fa3f289586822fd1b9f17fbf3e0b18895122d

Added RGB PWM hard IP example

view details

push time in 2 months

fork nalzok/icesugar

iCESugar FPGA Board (base on iCE40UP5k)

fork in 2 months

create barnchnalzok/mcve

branch : master

created branch time in 2 months

created repositorynalzok/mcve

created time in 2 months

issue commentpandas-dev/pandas

API/DEPR: Deprecate inplace parameter

inplace rarely actually does something inplace

@toobaz But why not? In other words, what is preventing methods with inplace=True from getting re-implemented at some point to use truly in-place operation? If the reason is some technical difficulty or lack of manpower, maybe we should leave the option as-is instead of eliminating the possibility of future improvements.

gfyoung

comment created time in 2 months

issue openedYosysHQ/nextpnr

No wire found for port LEDDRST on destination cell SB_LEDDA_IP_INST

I'm trying to use the SB_LEDDA_IP primitive on iCE40UP5k.

module top(
    output LED_R,
    output LED_G,
    output LED_B
);

    reg         innCLK;
    reg         dr_red_led;
    reg         dr_green_led;
    reg         dr_blue_led;
    reg         led_en;
    reg         led_cs;
    reg         led_exe;

    reg [3:0]   LEDD_ADR        = 4'b0000;
    reg [7:0]   DAT_Bits        = 8'b00000000;

    localparam  IDLE            = 4'b0000;
    localparam  LEDDBR          = 4'b0001;
    localparam  LEDDONR         = 4'b0010;
    localparam  LEDDOFR         = 4'b0011;
    localparam  LEDDBCRR        = 4'b0100;
    localparam  LEDDBCFR        = 4'b0101;
    localparam  LEDDPWRR        = 4'b0110;
    localparam  LEDDPWRG        = 4'b0111;
    localparam  LEDDPWRB        = 4'b1000;
    localparam  LEDDCR0         = 4'b1001;
    localparam  DONE            = 4'b1010;

    reg         PWM_state_reg   = IDLE;

    always @(posedge innCLK)
    begin
        case (PWM_state_reg)
            IDLE: begin
                led_en          <= 0;
                led_cs          <= 0;
                led_exe         <= 1;
                LEDD_ADR        <= 4'b0000;
                DAT_Bits        <= 8'b00000000;
                PWM_state_reg   <= LEDDBR;
            end
            LEDDBR: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b1001;
                DAT_Bits        <= 8'b11101101;
                PWM_state_reg   <= LEDDONR;
            end
            LEDDONR: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b1010;
                DAT_Bits        <= 8'b00010001;
                PWM_state_reg   <= LEDDOFR;
            end
            LEDDOFR: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b1011;
                DAT_Bits        <= 8'b00010001;
                PWM_state_reg   <= LEDDBCRR;
            end
            LEDDBCRR: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b0101;
                DAT_Bits        <= 8'b11100011;
                PWM_state_reg   <= LEDDBCFR;
            end
            LEDDBCFR: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b0110;
                DAT_Bits        <= 8'b10100011;
                PWM_state_reg   <= LEDDPWRR;
            end
            LEDDPWRR: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b0001;
                DAT_Bits        <= 8'b00000001;
                PWM_state_reg   <= LEDDPWRG;
            end
            LEDDPWRG: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b0010;
                DAT_Bits        <= 8'b11111111;
                PWM_state_reg   <= LEDDPWRB;
            end
            LEDDPWRB: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b0011;
                DAT_Bits        <= 8'b00011111;
                PWM_state_reg   <= LEDDCR0;
            end
            LEDDCR0: begin
                led_en          <= 1;
                led_cs          <= 1;
                led_exe         <= 0;
                LEDD_ADR        <= 4'b1000;
                DAT_Bits        <= 8'b11001010;
                PWM_state_reg   <= DONE;
            end
            DONE: begin
                led_en          <= 0;
                led_cs          <= 0;
                led_exe         <= 1;
                LEDD_ADR        <= 4'b0000;
                DAT_Bits        <= 8'b00000000;
                PWM_state_reg   <= DONE;
            end
        endcase
    end

    SB_HFOSC #(
        .CLKHF_DIV              ("0b00"),
    ) SB_HFOSC_INST(
        .CLKHFPU                (1'b1),
        .CLKHFEN                (1'b1),
        .CLKHF                  (innCLK)
    );

    SB_LEDDA_IP SB_LEDDA_IP_INST(
        .LEDDCS                 (led_cs),
        .LEDDCLK                (innCLK),
        .LEDDDAT7               (DAT_Bits[7]),
        .LEDDDAT6               (DAT_Bits[6]),
        .LEDDDAT5               (DAT_Bits[5]),
        .LEDDDAT4               (DAT_Bits[4]),
        .LEDDDAT3               (DAT_Bits[3]),
        .LEDDDAT2               (DAT_Bits[2]),
        .LEDDDAT1               (DAT_Bits[1]),
        .LEDDDAT0               (DAT_Bits[0]),
        .LEDDADDR3              (LEDD_ADR[3]),
        .LEDDADDR2              (LEDD_ADR[2]),
        .LEDDADDR1              (LEDD_ADR[1]),
        .LEDDADDR0              (LEDD_ADR[0]),
        .LEDDDEN                (led_en),
        .LEDDEXE                (led_exe),
        .LEDDRST                (1'b0),

        .PWMOUT0                (dr_red_led),
        .PWMOUT1                (dr_green_led),
        .PWMOUT2	            (dr_blue_led),
    );

    SB_RGBA_DRV #(
        .CURRENT_MODE           ("0b0"),
        .RGB0_CURRENT           ("0b000011"),
        .RGB1_CURRENT           ("0b000011"),
        .RGB2_CURRENT           ("0b000011"),
    ) SB_RGBA_DRV_INST(
        .CURREN                 (1'b1),
        .RGBLEDEN               (1'b1),
        .RGB0PWM                (dr_red_led),
        .RGB1PWM                (dr_green_led),
        .RGB2PWM                (dr_blue_led),
        .RGB0                   (LED_R),
        .RGB1                   (LED_G),
        .RGB2                   (LED_B)
  );

endmodule // top

Here is the Makefile I'm using

filename = hard_led
pcf_file = ../../../common/io.pcf

build:
	yosys -p "synth_ice40 -top top -json $(filename).json" $(filename).v
	nextpnr-ice40 \
		--up5k \
		--package sg48 \
		--json $(filename).json \
		--pcf $(pcf_file) \
		--asc $(filename).asc
	icepack $(filename).asc $(filename).bin

clean:
	rm -rf $(filename).blif $(filename).asc $(filename).bin

The error I got is

Info: Routing..
Info: Setting up routing queue.
ERROR: No wire found for port LEDDRST on destination cell SB_LEDDA_IP_INST.
ERROR: Routing design failed.
42 warnings, 2 errors
make: *** [build] Error 255

I noticed a comment saying LEDDRST doesn't exist. What does that mean? Has Lattice been lying in their document and the on-chip hard IP doesn't really take that parameter?

https://github.com/YosysHQ/nextpnr/blob/bb7358020928d0a26ab7becd123ccdc15b0206cb/ice40/cells.cc#L289-L290

The comment also mentions compatibility with iCEcube2, so I would prefer a warning instead of an error :)

created time in 2 months

startedZipCPU/sdspi

started time in 2 months

PR opened wuxx/VexRiscv

Include muraxDemo.hex as a Makefile dependency

No need to type make clean && make any longer! Just type make and Make will detect if muraxDemo.hex has changed and rebuild the whole thing if it does.

+2 -2

0 comment

1 changed file

pr created time in 2 months

push eventnalzok/VexRiscv

Qingyao Sun

commit sha 28de79b5705a56b7cfcc4e3fb016bde7bb6e19c5

Include muraxDemo.hex as a Makefile dependency

view details

push time in 2 months

fork nalzok/VexRiscv

A FPGA friendly 32 bit RISC-V CPU implementation

fork in 2 months

startedmetalcode-eu/darwin-riscv

started time in 2 months

startedOrsoEric/2020-07-26-Longan-Screen-Class-Demo

started time in 2 months

startedslmisc/gd32v-lcd

started time in 3 months

issue commentsipeed/Longan_GD32VF_examples

flashing logan nano give me a dfutil error *** [upload] Error 74

Same here. The relevant error message is

Uploading .pio/build/sipeed-longan-nano/firmware.bin
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device...
ID 28e9:0189
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
GD32 flash memory access detected
Device model: GD32VF103CB
Memory segment (0x08000000 - 0801ffff)(rew)
Erase size 1024, page count 128
Downloading to address = 0x08000000, size = 20140

Download	[                         ]   0%            0 bytes
Download	[                         ]   0%            0 bytes
Download	[==                       ]  10%         2048 bytes
Download	[=====                    ]  20%         4096 bytes
Download	[=======                  ]  30%         6144 bytes
Download	[==========               ]  40%         8192 bytes
Download	[============             ]  50%        10240 bytes
Download	[===============          ]  61%        12288 bytes
Download	[=================        ]  71%        14336 bytes
Download	[====================     ]  81%        16384 bytes
Download	[======================   ]  91%        18432 bytes
Download	[=========================] 100%        20140 bytes
Download done.
File downloaded successfully
dfu-util: dfuse_download: libusb_control_transfer returned -1
*** [upload] Error 74
teletubbiesarenotforpendingpandas

comment created time in 3 months

startedriscv-mcu/GD32VF103_Firmware_Library

started time in 3 months

more