Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    kost
    @kost
    you can basically say
    brew tap kost/homebrew-ulx3s
    brew install --HEAD  fujprog openfpgaloader
    currently, there is issue with nextpnr-trellis, need to fix that, but all other packages should work
    (like project-trellis and yosys)
    Erik Piehl
    @Speccery
    Did that, still problem:
    Eriks-MacBook-Pro:icy99 perik$ sudo openfpgaloader ti994a_ulx3s.bit
    unable to open ftdi device: -3 (device not found)
    Error: Failed to claim cable
    this was after installing openfpgaloader with your instructions.
    thank you @kost for the support. I will see if I can find out why fujprog does not work but the old ujprog does.
    kost
    @kost
    old ujprog is using old libusb0 as far as I can remember
    fujprog and openfpgaloader are ported to newer libftdi and libusb1
    Erik Piehl
    @Speccery
    old code uses LDFLAGS += pkg-config --libs libusb libftdi to find out libraries to link and on my machine that resolves to -L/usr/local/Cellar/libusb-compat/0.1.5_1/lib -L/usr/local/Cellar/libftdi0/0.20/lib -lusb -lftdi -lusb
    I need to come back to this issue later, now running out of time.
    kost
    @kost
    btw I think I fixed nextpnr-trellis, so every package in homebrew tap should work now.
    Erik Piehl
    @Speccery
    👍
    Paul Ruiz
    @pnru_gitlab
    @Speccery @kost Retraced my steps. I built fujprog from source on 24/8 on Catalina 10.15.3, using the provided CMake build script(s). This binary works for me on Catalina without sudo. The same binary also works for me on Mojave and High Sierra. I do not have a 3.0.8 board to test with. Over the last month this build of fujprog has worked for me without issues.
    Erik Piehl
    @Speccery
    Thanks @pnru_gitlab for the tests. Glad to hear you have it working. I got your binaries, but still same results. I sent you an e-mail. I will try to find some time to debug this - it's great to have the source code. It has already been almost a year that I worked on ujprog , before I got the ULX3S I added support for the FleaFPGAOhm. https://github.com/Speccery/tools
    e2kgh
    @e2kgh
    @Dolu1990 : how did you test the FrameBuffer? (/dev/fbdev)? Are there any simple test programs, which simply set a pixel in the frambuffer? ClearScreen or similar?
    mara
    @vmedea
    piping /dev/random or /dev/zero to it will do the trick
    😌
    kost
    @kost
    @Speccery i have managed to reproduce it on the 3.0.8 board on Mac.
    both openfpgaloader and fujprog fail to find JTAG cable connected
    Next step is to test with 3.0.3 version of the board
    could be something is changed with ftx
    Dolu1990
    @Dolu1990
    @e2kgh Normaly, there is a console running in it : cat miaou > /dev/tty0
    Dolu1990
    @Dolu1990
    @vmedea Hoooo funny, i never thinked about it XD
    Just tried, cat /dev/random > /dev/fb0 freeze, but cat /dev/urandom > /dev/fb0 works perfectly ^^
    emard
    @emard
    @Dolu1990 random desn't really freeze but its slow because it needs to accumulate some "entropy"
    Dolu1990
    @Dolu1990
    hooo right
    emard
    @emard
    BTW on FB textmode and colors, do vt100 color numbers 100-108 work, they are "bright" versions of normal text bg colors 40-49. Visually it colors appear identical as non-bright... Well it's just for tetris, and generally completely unimportant :)
    Dolu1990
    @Dolu1990
    hmm, i have no idea about it, maybe it is some packages to enable in linux / buildroot ?
    emard
    @emard
    ok, if you or lawrie can for some of next rebuilds enable 256-color mode, original tetris "needs" yellow and orange blocks which currently both look orange so I changed yellow to white, thus departing from official "standard" :) eheheheee
    Erik Piehl
    @Speccery
    @kost ok good to know you have the same issue, even if this is bad news. For me 3.0.3 fails too.
    kost
    @kost
    @Speccery Identified problem. caused by this pull request: https://github.com/kost/fujprog/pull/1/files
    if you open the device with NULL: hmp->cable_path, NULL, port_index);
    it works.
    if passed serial to the same function call, it does not recognize the device.
    currently it is only manifested on Mac
    kost
    @kost
    Right fix is to actually initialize value early in main() with serial=NULL;
    and it looks like it works
    mara
    @vmedea

    @emard

    BTW on FB textmode and colors, do vt100 color numbers 100-108 work, they are "bright" versions of normal text bg colors 40-49. Visually it colors appear identical as non-bright... Well it's just for tetris, and generally completely unimportant :)

    that's correct, due to IBM PC legacy, linux console doesn't support the bright background colors as separate color, the trick was always to use blink (SGR parameter 5), this sets the attribute bit in question

    mara
    @vmedea
    that said, for tetris with full-sized blocks, one could use a block character with the foreground color yellow instead maybe? or, fwiw, linux fb also allows changing the palette
    kost
    @kost
    @Speccery fixed in kost/fujprog@720e92b , that means you can pull latest version, compile it and it should work. I'll check for openfpgaloader, probably he have similar problem ;)
    Erik Piehl
    @Speccery
    Thanks @kost that was very fast!
    kost
    @kost
    As suspected, sudo openFPGALoader --board ulx3s blink/blink_85f.bit works
    directly calling does not work: sudo openFPGALoader blink/blink_85f.bit
    @Speccery does it work for you now?
    emard
    @emard
    @vmedea thanx for blink bit trick I will try!! :)
    emard
    @emard
    @vmedea Yes blink bit makes linux FB show orange as yellow, and it actually blinks in linux terminal, incrasing colorfulness of the board, thenx :)
    pushed new tetris :)
    Erik Piehl
    @Speccery
    @kost no change for me with the new version. I wonder if my FTDI drivers are somehow broken
    kost
    @kost
    stupid question. have you connected it to the USB (US1)? USB (US2) will not work. Also, do you get the micropython terminal screen when run screen /dev/tty.usbserial-XXXX
    ?