[Libre-soc-dev] daily kan-ban update 25sep2020
Luke Kenneth Casson Leighton
lkcl at lkcl.net
Sat Sep 26 13:34:10 BST 2020
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Sat, Sep 26, 2020 at 10:53 AM Luke Kenneth Casson Leighton
<lkcl at lkcl.net> wrote:
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
> On Sat, Sep 26, 2020 at 12:48 AM Jacob Lifshay <programmerjake at gmail.com> wrote:
> > On Fri, Sep 25, 2020, 06:30 Luke Kenneth Casson Leighton <lkcl at lkcl.net>
> > wrote:
> > > rest of day will write some tests (somehow) to check that the
> > > IOconnections through JTAG work. running this through JTAG will
> > > involve writing a mini jtagremote client/server to be able to talk to
> > > openocd.
> > >
> > Sorry, I wasn't able to figure out what you wanted me to do
> take the code from the searches i sent "python socket example" (20
> lines each) and put them in a file.
> take the code from the jtagremote link i sent for litex and convert it
> to a python client and a python server (25 lines each)
done - client-side was 2 functions, around 20 lines, server-side was 18.
very simple, no error checking, no abstraction, just "getting on with
it". about an hour's work, including the unit tests.
that was what was needed.
this is the kind of "no distractions, no thinking, just do it, right
here, right now" kind of mode we need right now.
go through the list of tasks, focus on *nothing* but what gets us to
the goal of being ready for the tapeout.
that involves making absolutely sure that the JTAG interface is
stable, does what it says, and making sure that at each phase of
conversion (nmigen, verilog, FPGA, GDSII) we can test that WITHOUT
FAIL the functionality is exactly the same.
anything that gets in the way of that, we *have* to clamp down on it
and leave it aside.
More information about the Libre-soc-dev