home.social

#goboard β€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #goboard, aggregated by home.social.

fetched live
  1. #fpga In the #nandland #goboard tutorial below, there is code like this:

    always ... begin
    b <= a
    if (a == 0 && b == 1)
    do something
    end

    How could this possibly work? always() is sequential, so shouldn't a and b always be equal after the assignment? (It does work, I just don't understand how.)

    youtu.be/_7K-ty3Mffg?list=PLnA

  2. #fpga In the #nandland #goboard tutorial below, there is code like this:

    always ... begin
    b <= a
    if (a == 0 && b == 1)
    do something
    end

    How could this possibly work? always() is sequential, so shouldn't a and b always be equal after the assignment? (It does work, I just don't understand how.)

    youtu.be/_7K-ty3Mffg?list=PLnA

  3. In the tutorial below, there is code like this:

    always ... begin
    b <= a
    if (a == 0 && b == 1)
    do something
    end

    How could this possibly work? always() is sequential, so shouldn't a and b always be equal after the assignment? (It does work, I just don't understand how.)

    youtu.be/_7K-ty3Mffg?list=PLnA

  4. #fpga In the #nandland #goboard tutorial below, there is code like this:

    always ... begin
    b <= a
    if (a == 0 && b == 1)
    do something
    end

    How could this possibly work? always() is sequential, so shouldn't a and b always be equal after the assignment? (It does work, I just don't understand how.)

    youtu.be/_7K-ty3Mffg?list=PLnA

  5. #fpga In the #nandland #goboard tutorial below, there is code like this:

    always ... begin
    b <= a
    if (a == 0 && b == 1)
    do something
    end

    How could this possibly work? always() is sequential, so shouldn't a and b always be equal after the assignment? (It does work, I just don't understand how.)

    youtu.be/_7K-ty3Mffg?list=PLnA

  6. I'm really impressed with the #opensource #icestudio #fpga programmer so far. And I usually *hate* #guis.

    The workflow in the #nandland #goboard tutorials looks so extremely painful compared to this.

    I'm definitely still bracing for "my" way to turn out harder/worse in the long run, tho.

    The top row is basically a direct copy of the tutorial (still had to figure out how the gui does this, tho). The bottom row is me reverse engineering how to do this with #icestudio blocks.

    #babyfpga

  7. I'm really impressed with the #opensource #icestudio #fpga programmer so far. And I usually *hate* #guis.

    The workflow in the #nandland #goboard tutorials looks so extremely painful compared to this.

    I'm definitely still bracing for "my" way to turn out harder/worse in the long run, tho.

    The top row is basically a direct copy of the tutorial (still had to figure out how the gui does this, tho). The bottom row is me reverse engineering how to do this with #icestudio blocks.

    #babyfpga

  8. I'm really impressed with the programmer so far. And I usually *hate* .

    The workflow in the tutorials looks so extremely painful compared to this.

    I'm definitely still bracing for "my" way to turn out harder/worse in the long run, tho.

    The top row is basically a direct copy of the tutorial (still had to figure out how the gui does this, tho). The bottom row is me reverse engineering how to do this with blocks.

  9. I'm really impressed with the #opensource #icestudio #fpga programmer so far. And I usually *hate* #guis.

    The workflow in the #nandland #goboard tutorials looks so extremely painful compared to this.

    I'm definitely still bracing for "my" way to turn out harder/worse in the long run, tho.

    The top row is basically a direct copy of the tutorial (still had to figure out how the gui does this, tho). The bottom row is me reverse engineering how to do this with #icestudio blocks.

    #babyfpga

  10. I'm really impressed with the #opensource #icestudio #fpga programmer so far. And I usually *hate* #guis.

    The workflow in the #nandland #goboard tutorials looks so extremely painful compared to this.

    I'm definitely still bracing for "my" way to turn out harder/worse in the long run, tho.

    The top row is basically a direct copy of the tutorial (still had to figure out how the gui does this, tho). The bottom row is me reverse engineering how to do this with #icestudio blocks.

    #babyfpga

  11. #icestudio has all the #nandland #goboard #fpga tutorial projects built into it, so I assume that means it is capable enough for this. That's great!

    I feel like I'm learning #icestudio instead of #verilog or #vhdl, tho.

    It's all open source, so probably the "raw" files it produces aren't going to be hidden from me. I'll just see if I can following a verilog tutorial to make an icestudio project...

  12. #icestudio has all the #nandland #goboard #fpga tutorial projects built into it, so I assume that means it is capable enough for this. That's great!

    I feel like I'm learning #icestudio instead of #verilog or #vhdl, tho.

    It's all open source, so probably the "raw" files it produces aren't going to be hidden from me. I'll just see if I can following a verilog tutorial to make an icestudio project...

  13. has all the tutorial projects built into it, so I assume that means it is capable enough for this. That's great!

    I feel like I'm learning instead of or , tho.

    It's all open source, so probably the "raw" files it produces aren't going to be hidden from me. I'll just see if I can following a verilog tutorial to make an icestudio project...

  14. #icestudio has all the #nandland #goboard #fpga tutorial projects built into it, so I assume that means it is capable enough for this. That's great!

    I feel like I'm learning #icestudio instead of #verilog or #vhdl, tho.

    It's all open source, so probably the "raw" files it produces aren't going to be hidden from me. I'll just see if I can following a verilog tutorial to make an icestudio project...

  15. #icestudio has all the #nandland #goboard #fpga tutorial projects built into it, so I assume that means it is capable enough for this. That's great!

    I feel like I'm learning #icestudio instead of #verilog or #vhdl, tho.

    It's all open source, so probably the "raw" files it produces aren't going to be hidden from me. I'll just see if I can following a verilog tutorial to make an icestudio project...

  16. I got a #nandland #goboard because it looked like a good way to learn #fpga. Nice simple tutorials, built-in peripherals, etc. And the guy says the dev env is one of the simplest.

    #lattice #icecube2 is some of the *worst* software it's been my misfortune to install. Among other problems:

    1. required me to make a symlink in /lib32 because it somehow couldn't honor LD_LIBRARY_PATH

    2. needs me to change NIC name to "eth0" because license module can't find my MAC otherwise

    #linux

  17. I got a #nandland #goboard because it looked like a good way to learn #fpga. Nice simple tutorials, built-in peripherals, etc. And the guy says the dev env is one of the simplest.

    #lattice #icecube2 is some of the *worst* software it's been my misfortune to install. Among other problems:

    1. required me to make a symlink in /lib32 because it somehow couldn't honor LD_LIBRARY_PATH

    2. needs me to change NIC name to "eth0" because license module can't find my MAC otherwise

    #linux

  18. I got a because it looked like a good way to learn . Nice simple tutorials, built-in peripherals, etc. And the guy says the dev env is one of the simplest.

    is some of the *worst* software it's been my misfortune to install. Among other problems:

    1. required me to make a symlink in /lib32 because it somehow couldn't honor LD_LIBRARY_PATH

    2. needs me to change NIC name to "eth0" because license module can't find my MAC otherwise

  19. I got a #nandland #goboard because it looked like a good way to learn #fpga. Nice simple tutorials, built-in peripherals, etc. And the guy says the dev env is one of the simplest.

    #lattice #icecube2 is some of the *worst* software it's been my misfortune to install. Among other problems:

    1. required me to make a symlink in /lib32 because it somehow couldn't honor LD_LIBRARY_PATH

    2. needs me to change NIC name to "eth0" because license module can't find my MAC otherwise

    #linux

  20. I got a #nandland #goboard because it looked like a good way to learn #fpga. Nice simple tutorials, built-in peripherals, etc. And the guy says the dev env is one of the simplest.

    #lattice #icecube2 is some of the *worst* software it's been my misfortune to install. Among other problems:

    1. required me to make a symlink in /lib32 because it somehow couldn't honor LD_LIBRARY_PATH

    2. needs me to change NIC name to "eth0" because license module can't find my MAC otherwise

    #linux