mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC v4 10/10] Documentation: add RISC-V docs
Date: Sat, 30 Sep 2017 15:34:30 +0300	[thread overview]
Message-ID: <20170930153430.531d45897831b9f1e08bc4c7@gmail.com> (raw)
In-Reply-To: <9b1d2334-72a1-7aee-a1d5-3df034c29fef@rempel-privat.de>

On Fri, 29 Sep 2017 14:35:37 +0200
Oleksij Rempel <linux@rempel-privat.de> wrote:

> Am 29.09.2017 um 01:12 schrieb Antony Pavlov:
> > Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> > ---
> >  Documentation/boards/riscv.rst | 110 +++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 110 insertions(+)
> > 
> > diff --git a/Documentation/boards/riscv.rst b/Documentation/boards/riscv.rst
> > new file mode 100644
> > index 000000000..912f16786
> > --- /dev/null
> > +++ b/Documentation/boards/riscv.rst
> > @@ -0,0 +1,110 @@
> > +RISC-V
> > +======
> > +
> > +At the moment only qemu emulator is supported (see https://github.com/riscv/riscv-isa-sim
> > +for details).
> > +
> > +Running RISC-V barebox on qemu
> > +------------------------------
> > +
> > +Obtain RISC-V GCC/Newlib Toolchain,
> > +see https://github.com/riscv/riscv-tools/blob/master/README.md
> > +for details. The ``build.sh`` script from ``riscv-tools`` should
> > +create toolchain.
> > +
> > +Next compile qemu emulator::
> > +
> > +  $ git clone -b 20170824.erizo https://github.com/miet-riscv-workgroup/riscv-qemu
> > +  $ cd riscv-qemu
> > +  $ cap="no" ./configure \
> > +    --extra-cflags="-Wno-maybe-uninitialized" \
> > +    --audio-drv-list="" \
> > +    --disable-attr \
> > +    --disable-blobs \
> > +    --disable-bluez \
> > +    --disable-brlapi \
> > +    --disable-curl \
> > +    --disable-curses \
> > +    --disable-docs \
> > +    --disable-kvm \
> > +    --disable-spice \
> > +    --disable-sdl \
> > +    --disable-vde \
> > +    --disable-vnc-sasl \
> > +    --disable-werror \
> > +    --enable-trace-backend=simple \
> > +    --disable-stack-protector \
> > +    --target-list=riscv32-softmmu,riscv64-softmmu
> > +  $ make
> > +
> > +
> > +Next compile barebox::
> > +
> > +  $ make erizo_generic_defconfig ARCH=riscv
> > +  ...
> > +  $ make ARCH=riscv CROSS_COMPILE=<path to your riscv toolchain>/riscv32-unknown-elf-
> > +
> > +Run barebox::
> > +
> > +  $ <path to riscv-qemu source>/riscv32-softmmu/qemu-system-riscv32 \
> > +      -nographic -M erizo -bios <path to barebox sources >/barebox.bin \
> > +      -serial stdio -monitor none -trace file=/dev/null
> > +
> > +  nmon> q
> > +  
> > +  copy loop done
> > +  restarting...
> > +  
> > +  nmon> q
> > +  Switch to console [cs0]
> > +  
> > +  
> > +  barebox 2017.08.0-00102-g212af75153 #1 Mon Sep 4 20:54:31 MSK 2017
> > +  
> > +  
> > +  Board: generic Erizo SoC board
> > +  m25p80 m25p128@00: unrecognized JEDEC id bytes: 00,  0,  0
> > +  m25p80 m25p128@00: probe failed: error 2
> > +  malloc space: 0x80100000 -> 0x801fffff (size 1 MiB)
> > +  running /env/bin/init...
> > +  /env/bin/init not found
> > +  barebox:/
> > +
> > +
> > +Running RISC-V barebox on DE0-Nano FPGA board
> > +---------------------------------------------
> > +
> > +See https://github.com/open-design/riscv-soc-cores/ for instructions
> > +on DE0-Nano bitstream generation and loading.
> > +
> > +Connect to board's UART with your favorite serial communication software
> > +(e.g. minicom) and check 'nmon> ' prompt (nmon runs from onchip ROM).
> > +
> > +Next close your communication software and use ./scripts/nmon-loader
> > +to load barebox image into board's DRAM, e.g.
> > +
> > +  # ./scripts/nmon-loader barebox.erizo.nmon /dev/ttyUSB1 115200
> > +
> > +Wait several munutes for 'nmon> ' prompt.
> > +
> > +Next, start barebox from DRAM:
> > +
> > +  nmon> g 80000000
> > +
> > +You should see one more 'nmon> ' prompt (this nmon runs from DRAM).
> > +Exit nmon with 'q' command:
> > +
> > +  nmon> q
> > +  Switch to console [cs0]
> > +  
> > +  
> > +  barebox 2017.08.0-00102-g212af75153 #1 Mon Sep 4 20:54:31 MSK 2017
> > +  
> > +  
> > +  Board: generic Erizo SoC board
> > +  m25p80 m25p128@00: unrecognized JEDEC id bytes: 00,  0,  0
> > +  m25p80 m25p128@00: probe failed: error 2
> 
> hmmm... not working example?


At the moment I run risc-v barebox on several FPGA boards.
SPI flash chip is absent on some boards.
This log was produced by SPI-flash-chip-less board.

Also SPI flash chip emulation is absent for Erizo qemu board.


> > +  malloc space: 0x80100000 -> 0x801fffff (size 1 MiB)
> > +  running /env/bin/init...
> > +  /env/bin/init not found
> > +  barebox:/ 
> 
> some parts are missing in defconfig. Barebox shell can display hostname
> and so on ;)
> -- 
> Regards,
> Oleksij
> 


-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-09-30 12:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 23:12 [RFC v4 00/10] add initial RISC-V architecture support Antony Pavlov
2017-09-28 23:12 ` [RFC v4 01/10] Add " Antony Pavlov
2017-09-29 12:07   ` Oleksij Rempel
2017-09-30 11:57     ` Antony Pavlov
2017-10-02  7:43       ` Oleksij Rempel
2017-10-02 14:08         ` Antony Pavlov
2017-10-02 10:04       ` Daniel Schultz
2017-10-02 22:15         ` Antony Pavlov
2017-10-02 10:08     ` Daniel Schultz
2017-10-02 22:21       ` Antony Pavlov
2017-10-05 10:55         ` Daniel Schultz
2017-10-06 15:39           ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 02/10] RISC-V: add Erizo SoC support Antony Pavlov
2017-09-29 12:18   ` Oleksij Rempel
2017-09-30 12:05     ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 03/10] RISC-V: add low-level debug macros for ns16550 Antony Pavlov
2017-09-28 23:12 ` [RFC v4 04/10] RISC-V: add nmon nano-monitor Antony Pavlov
2017-09-29 12:26   ` Oleksij Rempel
2017-09-30 12:22     ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 05/10] RISC-V: erizo: add DEBUG_LL support Antony Pavlov
2017-09-28 23:12 ` [RFC v4 06/10] RISC-V: erizo: enable NMON Antony Pavlov
2017-09-28 23:12 ` [RFC v4 07/10] RISC-V: erizo: add nmon image creation Antony Pavlov
2017-09-28 23:12 ` [RFC v4 08/10] RISC-V: add erizo_generic_defconfig Antony Pavlov
2017-09-29 12:29   ` Oleksij Rempel
2017-09-30 12:38     ` Antony Pavlov
2017-09-28 23:12 ` [RFC v4 09/10] scripts: add nmon-loader Antony Pavlov
2017-09-28 23:12 ` [RFC v4 10/10] Documentation: add RISC-V docs Antony Pavlov
2017-09-29 12:35   ` Oleksij Rempel
2017-09-30 12:34     ` Antony Pavlov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170930153430.531d45897831b9f1e08bc4c7@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=linux@rempel-privat.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox