Running programs at Linux Startup
by Imran Wali
Hi,
I am trying to automatically run a user program after Linux startup on LowRISC v0.3.
To do so, I have changed the make_root.sh script to incorporate my program in /usr/bin in the root file system. I have tried a few methods to launch the program for e.g. modifying the "inittab" file, and to use /etc/rc.local etc, but nothing seems to work.
Please share your experiences or ideas how to automatically launch programs at Linux startup.
Thanks and regards,
Imran Wali
Postdoctoral Researcher
ARIES Research Center
Nebrija University
4 years, 8 months
Re: [hw-dev] memory space mapping for lowRiscv
by Dr Jonathan Kimmitt
I do not see why you would need to use any software drivers from
previous releases for that set up. Some drivers might
not have changed however. Needless to say you have to use the correct
version of gcc that comes with that release.
It does not work if you set $RISCV to an old gcc install (this is to do
with control and status register numbers primarily).
If it still doesn't work it might be to do with clock management.
Verilog timing simulation should show you if this is the case.
On 12/07/18 15:31, Claire M. M. Wong wrote:
> Thanks for the heads-up.
>
> As for Jonathan queations:
>
> Yes I started the porting by copying the v0.5 nexys4ddr directory to
> kc705.
>
> I commented the ethernet part in release v0.5. I want to minimise the
> scope of troubleshooting. I will deal with this part later on.
>
> As for the drivers, yes I did mix and modify a little from other
> releases. But not for the memory maps.
>
> Yes the NexyDDR only peripheral has been removed, that also includes
> the ADD_HID
>
> I have run the fpga simulation. I directly try out the make hello and
> it didnt work. As in I didnt get the Hello Work printout on the terminal.
>
> Just to be sure, is the drivers are strictly specific for each release?
>
>
>
> On Thu, Jul 12, 2018 at 7:58 PM, Robert Mullins
> <Robert.Mullins(a)cl.cam.ac.uk <mailto:Robert.Mullins@cl.cam.ac.uk>> wrote:
>
> Hi Claire,
>
> Nice to hear you are experimenting with lowRISC. I hope Jonathan is
> able to help.
>
> The lowrisc-dev mailing list might be best for this sort of
> discussion:
> https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lowrisc-dev-li...
> <https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/lowrisc-dev-li...>
>
> Let us know how we can help by providing a few more details.
>
> v. best,
> - Rob.
>
>
> On 12 July 2018 at 12:48, Dr Jonathan Kimmitt <jrrk2(a)cam.ac.uk
> <mailto:jrrk2@cam.ac.uk>> wrote:
> > Dear Claire,
> >
> > From your description it is impossible to know what is wrong
> with your
> > 'several changes'.
> >
> > The main memory space by necessity will be larger on KC705.
> Other than that
> > the memory map will be specific to the release and not to the board.
> >
> > The only files which should definitely be taken for the KC705
> from previous
> > releases are the Xilinx pinout and the dynamic memory config.
> >
> > Did you begin your port by copying the v0.5 nexys4ddr directory
> to kc705?
> >
> > Did you adapt the Ethernet module design to use MII instead of
> RMII ?
> >
> > Did you avoid mixing drivers, memory maps or RISCV files from
> different
> > releases to prevent incompatible API changes from being propagated ?
> >
> > Did you remove the peripherals that are Nexys4DDR only
> (everything except
> > serial, Ethernet, and SD-Card)
> >
> > Did you simulate the reworked parts of the design in Verilog ?
> >
> > If you are still stuck you need to provide more details of the
> changes you
> > tried to make.
> >
> > Regards,
> > Jonathan
> >
> >
> > On 12/07/18 01:41, Claire M. M. Wong wrote:
> >
> > Hi all,
> >
> > I noticed there is a significant change in memory space mapping
> between
> > lowriscv project v0.2 (developed for KC705) and project v0.3 onwards
> > (developed for NexyDDR). Is the memory mapping has to be done in
> such way
> > subject to the hardware board?
> >
> > In other words, suppose that I am trying to port project v0.5 to
> KC705,
> > should I also change the memory space allocated for the IO and Mem?
> >
> > What about the drivers for the baremetal examples? are they
> subjected to the
> > project's version and independent of the board? again if I would
> like to run
> > the bare metal example Hello World for v0.5 implemented on
> KC705, should I
> > be using the drivers that come with v0.5 or I have to use the
> ones provided
> > in v0.2?
> >
> > Sorry if I sound very silly as I am still trying to figure out
> how to get
> > things work with lowriscv project :)
> > My main aim is to implement v0.5 on KC705. After several changes
> have been
> > done, the work is still not successful. Therefore, I am trying to
> > troubleshoot as much as I could to figure out what I might have
> missed.
> >
> > And I really need your advice and opinions. They will be very much
> > appreciated :D
> >
> > Regards
> > Claire
> > --
> > You received this message because you are subscribed to the
> Google Groups
> > "RISC-V HW Dev" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send an
> > email to hw-dev+unsubscribe(a)groups.riscv.org
> <mailto:hw-dev%2Bunsubscribe@groups.riscv.org>.
> > To post to this group, send email to hw-dev(a)groups.riscv.org
> <mailto:hw-dev@groups.riscv.org>.
> > Visit this group at
> > https://groups.google.com/a/groups.riscv.org/group/hw-dev/
> <https://groups.google.com/a/groups.riscv.org/group/hw-dev/>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/a/groups.riscv.org/d/msgid/hw-dev/84928d28-7c9e...
> <https://groups.google.com/a/groups.riscv.org/d/msgid/hw-dev/84928d28-7c9e...>.
> >
> >
> > --
> > You received this message because you are subscribed to the
> Google Groups
> > "RISC-V HW Dev" group.
> > To unsubscribe from this group and stop receiving emails from
> it, send an
> > email to hw-dev+unsubscribe(a)groups.riscv.org
> <mailto:hw-dev%2Bunsubscribe@groups.riscv.org>.
> > To post to this group, send email to hw-dev(a)groups.riscv.org
> <mailto:hw-dev@groups.riscv.org>.
> > Visit this group at
> > https://groups.google.com/a/groups.riscv.org/group/hw-dev/
> <https://groups.google.com/a/groups.riscv.org/group/hw-dev/>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/a/groups.riscv.org/d/msgid/hw-dev/d57bca23-dd81...
> <https://groups.google.com/a/groups.riscv.org/d/msgid/hw-dev/d57bca23-dd81...>.
>
>
>
>
> --
> Regards,
> Ming
4 years, 8 months
