ничерта не видно на изображении. Как обучаться то?

Zoom is to bad that you can’t see a thing 😢

11 years later and here I am, learning from you about implementing I2C in Verilog. Thanks for that, I needed this push to understand the FPGA better.

nice work sir,,, can you build like that for the I3C protocol

Great tutorial man!

Why didn't you use a 4K screen? The screen is so crowded.

Excellent tutorial and demonstration!

why in the first application compiling process not use the compiler in the yocto project

Helps a lot TQSm❤

its not called "get" you dont do get clone, get checkout etc, its called GIT file FIT but with a G not trying to be a troll its just confusion factor.

How did you download the repository file I need one for edge spartan 6 xc6slx9 tqg144 -2 board

Why in STATE_RW we are doing "icl_sda<=1", it is a Read or write byte then why are we only makinh it high(for read only)?

How I can run a dotnet app in the yocto image ? I am lost please help, I add the meta-mono layer for the dotnet recipe ...

Hi thank you for your nice tutorial, I am trying to run a dotnet app on yocto image but I didnt know how I need help please. I ve add a layer called meta-mono for the dotnet recipe , I ve edit also the bblayers config file, and run it withthe qemux86-64 My image is based on the kirkstone version I run the bitbake - k core-image-sato-dev and core-image-sato-sdk I am really confused and lost Thank you again for your nice tutorial

I know this is an old video but still applicable. Should introduce a series where you incorporate the device tree.

Great video - but please silence the keyboard ... when you start typing you can hear nothing else :)

perfect.🌟

FTP transfer is pointless. We need to add the module directly in yocto image. You should have done that in this video.

Hello, is it possible to build for the latest Yocto release (honister). I tried it and I got so many errors. I don't know how to handle it.!

Is there a step 5 video? Because the i2c_sda port is supposed to be inout and WACK states has not been changed to read ACK from slave device.

wonderful juz amazing demo to beginners

ive tried searching the internet on how to write network programs that commumicate over the public internet, and it suggested doing things like setting up a static ip address, enabling port forwarding etc. my question is how do browsers and games communicate over the public internet without having to change these settings. what sort of magic lies in their networking code?

Thanks for these videos. it's very fascinating

Hi Tom Thank you , Where can I access this code

Can you show us how your board looks up close? when I process mine, even after cleaning most of the ink as much as possible, I still end up with excess copper on the surface. How do you mitigate this from happening to your board?

Thank you for the excellent video!! This fills in some gaps that I couldn't get answered anywhere else.

þrðmð§m ✨

Great video!

@11:44 how do we know how many address states we went through?

when you rotate light through the LED array, you used "<=" instead of "="; could you explain the difference, I know the former is non-blocking(async) and the latter is blocking(sync or sequential by clock). But to the naked eye, will there be a visual difference if you used the "=" to do the rotation instead?

I do not have the board so I selected the same chip and tried to follow your demo as an exercise. I still did not successfully generate the bitstream after manually creating a constraint file; and I kept getting the same errors that you got in the video; the error was about the IOSTANDARD not being a specified value, even after I went into the "I/O ports" and selected specific values in the pull-down window. I think like you said it can get "absurd" in this issue. Why would Vivado make it so difficult and give users hard time like this.

This Series started out excellent for Steps 1 - 3 and up to the last few minutes of this Step 4 video. Then it fell way short of completion! I recommend you create a Step 5 video that continues to completion at least making the Simulation work with the new Dual clock FIFO. Best regards, JT

Guide to run Linux and Secure OS: kzbin.info/www/bejne/o2m6nYaXo6x3ras kzbin.info/www/bejne/eYiqY4qrhK-nf8U kzbin.info/www/bejne/fKXLdYiJjJish7s

[DRC ZPS7-1] PS7 block required: The PS7 cell must be used in this Zynq design in order to enable correct default configuration. Is there a Vivado setting, .xdc constraint parameter setting, or other remedy for this warning?

[Place 46-29] place_design is not in timing mode. Skip physical synthesis in placer [Power 33-232] No user defined clocks were found in the design! Power estimation will be inaccurate until this is corrected. Resolution: Please specify clocks using create_clock/create_generated_clock for sequential elements. For pure combinatorial circuits, please specify a virtual clock, otherwise the vectorless estimation might be inaccurate [Timing 38-313] There are no user specified timing constraints. Timing constraints are needed for proper timing analysis. What are the remedies for these warnings?

[Synth 8-7080] Parallel synthesis criteria is not met Am I missing some Vivado Setup setting that will remedy this warning? Or is this common and should ignore>

Send website and phone number

Speak up so we can hear you. You might want to have a monitor for a sound check. And the video side should be 720px or higher resolution. The current 480px resolution is far too fuzzy to triy and following along with your code changes without you significantly zooming in on those changes. Content is good.

Sir can you please provide link to download this book, thank you

WARNING: /home/subodh/Desktop/yocto/poky/meta-techveda/recipes-example/myhello/myhello.bb:do_compile is tainted from a forced runETA: 0:00:01 Initialising tasks: 100% |#####################################################################################################| Time: 0:00:02 Sstate summary: Wanted 3 Found 0 Missed 3 Current 1157 (0% match, 99% complete) NOTE: Executing Tasks ERROR: core-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs --setopt=logdir=/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp --repofrompath=oe-repo,/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo --nogpgcheck install myhello packagegroup-core-boot python3-multiprocessing run-postinsts' returned 1: DNF version: 4.2.2 cachedir: /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/var/cache/dnf Added oe-repo repo from /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo repo: using cache for: oe-repo not found other for: not found modules for: not found deltainfo for: not found updateinfo for: oe-repo: using metadata from Wed 22 Jun 2022 05:34:24 AM UTC. Last metadata expiration check: 0:00:01 ago on Wed 22 Jun 2022 05:34:25 AM UTC. No module defaults found No match for argument: myhello Error: Unable to find a match ERROR: Logfile of failure stored in: /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.22099 ERROR: Task (/home/subodh/Desktop/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 3157 tasks of which 3156 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/subodh/Desktop/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code.

subodh@subodh:~/Desktop/yocto/poky/build$ bitbake core-image-minimal Loading cache: 100% |##########################################################################################################| Time: 0:00:00 Loaded 1331 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.46.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.1.17" TUNE_FEATURES = "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp meta-techveda = "dunfell:238fb89434211b400f0201a8f3383babc5f9fa35" WARNING: /home/subodh/Desktop/yocto/poky/meta-techveda/recipes-example/myhello/myhello.bb:do_compile is tainted from a forced runETA: 0:00:01 Initialising tasks: 100% |#####################################################################################################| Time: 0:00:02 Sstate summary: Wanted 3 Found 0 Missed 3 Current 1157 (0% match, 99% complete) NOTE: Executing Tasks ERROR: core-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs --setopt=logdir=/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp --repofrompath=oe-repo,/home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo --nogpgcheck install myhello packagegroup-core-boot python3-multiprocessing run-postinsts' returned 1: DNF version: 4.2.2 cachedir: /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/var/cache/dnf Added oe-repo repo from /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo repo: using cache for: oe-repo not found other for: not found modules for: not found deltainfo for: not found updateinfo for: oe-repo: using metadata from Wed 22 Jun 2022 05:34:24 AM UTC. Last metadata expiration check: 0:00:01 ago on Wed 22 Jun 2022 05:34:25 AM UTC. No module defaults found No match for argument: myhello Error: Unable to find a match ERROR: Logfile of failure stored in: /home/subodh/Desktop/yocto/poky/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.22099 ERROR: Task (/home/subodh/Desktop/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 3157 tasks of which 3156 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/subodh/Desktop/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs Summary: There was 1 WARNING message shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code.

cat myhello/myhello.bb SUMMARY = "bitbake-layers recipe myhello" DESCRIPTION = "Recipe created by bitbake-layers" SECTION = "examples" PR = "r0" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302" SRC_URI = "file://myhello.c" S = "${WORKDIR}" do_compile(){ ${CC} ${LDFLAGS} myhello.c -o myhello } do_intall(){ install -d ${D}${bindir} install -m 0755 myhello ${D}${bindir} }

Thanks bro please do more of Vivado + Zedboard.

is this moore approach? can we make it using mealy?

480p? barely to see anything

Excellent thank you! I'm using Vivado 2021.2 with a Zedboard.

It's been 18 years since I used Virtuoso. I don't even recognize it! :-) Thanks for refreshing my memory on layout technique!

must be a mechanical keyboard. lots of clacking noise. haha. gamers love those keyboards

Are you hitting the keyboard with hammer?

Thank you! This was perfect!