Playing with RISC-V SiFive E300 on Arty A7 FPGA Development Board

Ғылым және технология

Sifive: www.sifive.com/
twitter: @sahajsarup
Instagram: @ric_96
My Vlog Channel:
/ @sahajvlogs665
blog: geektillithertz.com/wordpress

Пікірлер: 16

  • @esra_erimez
    @esra_erimez5 жыл бұрын

    Great video! Thank you.

  • @rajeshtechfreak
    @rajeshtechfreak5 жыл бұрын

    Thanks. This is a unique channel that is always hands-on centric approach. How do you fund the newer boards? Also, what do you do with your unused old boards?

  • @ashwin372

    @ashwin372

    2 жыл бұрын

    obviously youtube revenue

  • @kammounmanel5439
    @kammounmanel54394 жыл бұрын

    thank you so much sir. Your tutorial is very helpful. Would you please provide us with more tutorials about Risc V ?? and thanks

  • @saadullah2371
    @saadullah23713 жыл бұрын

    Hey, I am unable to download Vivado any other way to do the same thing?

  • @hoahuynh2734
    @hoahuynh27344 жыл бұрын

    Thank you, sir, very much. Your tutorial helps me to start successfully. :)

  • @hoahuynh2734

    @hoahuynh2734

    3 жыл бұрын

    With your tutorial and howto combination of application code to RISC-V boot code, I make some good progress in learning and playing with SiFive open-source RTL code for almost one year. Thank you. I post my progress in other social media; please visit and give some feedback. Please search for: "riscv study sifive approach autumn 2019 project"; the site forces the keywords into one long text string. Thank you.

  • @BruceHoult
    @BruceHoult5 жыл бұрын

    Whaaaat? We didn't get to see the final result of the Dhrystone :-( With that many iterations it takes 2m30s on a HiFve1 at 256 MHz, so should be about 10 min at 65 MHz, or 20 min if you're really running at 32 MHz now. btw the "core freq at xxx Hz" is *not* hard coded, it's calculated at program startup by counting actual CPU core cycles during one tick of the 32 kHz crystal.

  • @sahajsarup

    @sahajsarup

    5 жыл бұрын

    Hmm... We'll i guess I'll wait 20 minutues then. So, in some examples, like the demo_gpio it is hard coded. But it's defenately running at 32mhz, the 65mhz clock doesn't exist in the design anymore.

  • @BruceHoult

    @BruceHoult

    5 жыл бұрын

    @@sahajsarup no it's not. Show me where github.com/sifive/freedom-e-sdk/blob/master/software/demo_gpio/demo_gpio.c

  • @sahajsarup

    @sahajsarup

    5 жыл бұрын

    not directly in the example code. github.com/sifive/freedom-e-sdk/blob/master/bsp/freedom-e310-arty/design.dts#L50

  • @BruceHoult

    @BruceHoult

    5 жыл бұрын

    @@sahajsarup wrong place. github.com/sifive/freedom-e-sdk/blob/master/bsp/env/freedom-e300-arty/init.c OK, I'm shocked. I only use the HIFive1, and it calculates the clock speed. But I still don't see how you got 32 MHz in reality. If you did. I await the Dhrystone time.

Келесі