Wednesday, 2019-01-09

*** tpb has joined #timvideos00:00
mithroewen: interesting....00:01
ewenmithro: However so far I've not figured out where it's getting that path from... :-)00:01
ewenNOSTDINC_FLAGS += -nostdinc -isystem $(call shell-cached,$(CC) -print-file-name=include)00:09
ewen(Linux Makefile)00:09
ewenWhich suggests it's being cached somewhere...00:09
ewen$ or1k-elf-newlib-gcc -print-file-name=include00:10
ewen/src/fpga/litex-buildenv/build/conda/bin/../lib/gcc/or1k-elf/8.2.0/include00:10
ewen$ grep Usage.*shell-cached scripts/Kbuild.include00:12
ewen# Usage:   $(call shell-cached,shell_command)00:12
ewenmithro: Looks like it caches in .cache.mk stored in $(obj), which is build/arty_net_or1k.linux/software/linux/.cache.mk in this case00:17
ewen[email protected]:/src/fpga/litex-buildenv$ find . -name "*cache.mk*"00:17
ewen./build/arty_net_or1k.linux/software/linux/.cache.mk00:17
ewen./build/cache.mk00:17
ewen[email protected]:/src/fpga/litex-buildenv$ ls -l build/arty_net_or1k.linux/software/linux/.cache.mk00:17
ewen-rw-rw-r-- 1 ewen ewen 23901 Jan  9 12:12 build/arty_net_or1k.linux/software/linux/.cache.mk00:17
ewen[email protected]:/src/fpga/litex-buildenv$ grep 5.4.0 build/arty_net_or1k.linux/software/linux/.cache.mk00:17
ewen__cached_or1k-elf-newlib-gcc_-print-file-name_include := /src/fpga/litex-buildenv/build/conda/bin/../lib/gcc/or1k-elf/5.4.0/include00:17
ewen[email protected]:/src/fpga/litex-buildenv$00:17
ewenCarlFK[m]: mithro: FTR, "rm ./build/arty_net_or1k.linux/software/linux/.cache.mk" and then running scripts/build-linux.sh works properly.  I guess this is a side effect of starting with an older buildenv.00:18
ewenFTR, successfully built or1k linux and booted, via TFTP in QEMU (about to try on the Arty itself).00:22
ewenmithro: Success.  Can build/boot Linux on Arty as well.00:29
mithroewen: \o/00:40
*** andi-m has quit IRC00:45
*** andi-m has joined #timvideos00:45
CarlFK[m]Woot00:51
*** sc00bz1 has quit IRC01:09
*** sc00bz has joined #timvideos01:10
*** CarlFK has joined #timvideos01:22
*** ChanServ sets mode: +v CarlFK01:22
ewenWhile following https://github.com/timvideos/litex-buildenv/wiki/HowTo-FuPy-on-iCE40-Boards it appears that I've managed to (partially?) brick one of my TinyFPGA BX boards.  The "tinyprog --program-image" returned Failure (2-3 times), and after unplugging/plugging in BX board it's no longer finding the bootloader for programming :-(01:37
tpbTitle: HowTo FuPy on iCE40 Boards · timvideos/litex-buildenv Wiki · GitHub (at github.com)01:37
ewen    TinyProg CLI01:38
ewen    ------------01:38
ewen    Using device id 1d50:613001:38
ewen    Only one board with active bootloader, using it.01:38
ewen    Programming /dev/ttyACM0 with build/tinyfpga_bx_base_lm32.minimal//image-gateware+bios+none.bin01:38
ewen    Programming at addr 02800001:38
mithroewen: I think having the wrong version of tinyprog and overriding the warning might do that?01:38
ewenThere was no warning, AFAICT.01:39
mithrohrm....01:39
mithroewen: Are you using a VM?01:39
ewenNo, native on Ubuntu 16.04 VM01:39
ewen(16.04 laptop, I mean01:39
ewentinyprog                  1.0.22b1                  <pip>01:40
ewen(Installed via conda, via litex-buildenv)01:40
mithroewen: Hrm....01:41
ewenmithro: Not 100% bricked.  After leaving it plugged in for a while, *then* pressing reset, I did manage to re-upload the blink example.01:41
ewenI'll see if I can find another USB cable to try...01:41
ewenmithro: Looks like there's two things going on: 1. bootloader is only active for a wee while after reset, and 2. for some reason I'm having trouble programming BX from within litex-buildenv.01:44
ewen(Latter problem persists with a different USB cable.)01:44
mithroewen: If you are seeing (1) then it sounds like the bootloader is not detecting that your system has working USB01:45
mithrodo you have output in dmesg about xhci being all confused?01:45
ewenmithro: Not from xhci itself, now.  Seem to have usb-1.2 / cdc_acm messages only. Including failed to set dtr/rts01:47
ewenblink demo: 135100 bytes to program01:49
ewenlitex: 180192 bytes to program01:50
ewenOf note, my working "blink" example window is using tinyprog 1.0.18, and the litex-buildenv one is using tinyprog 1.0.22b101:55
*** mauz555 has joined #timvideos01:56
ewenPossibly relevant TinyFPGA thread: https://discourse.tinyfpga.com/t/issues-with-tinyprog-u-on-bx/628/801:57
tpbTitle: Issues with tinyprog -u on BX - TinyFPGA (at discourse.tinyfpga.com)01:57
ewenAnd possibly relevant bug (different file size): https://github.com/tinyfpga/TinyFPGA-Bootloader/issues/2301:58
tpbTitle: Programming TinyFPGA BX with userdata of size exactly 1244 bytes fails · Issue #23 · tinyfpga/TinyFPGA-Bootloader · GitHub (at github.com)01:58
*** mauz555 has quit IRC01:59
ewen1.0.22b1 is a beta pre-release; there's a 1.0.23 at https://pypi.org/project/tinyprog/#history, although there's still apparently no Python3 wheel (https://github.com/tinyfpga/TinyFPGA-Bootloader/issues/25)02:01
tpbTitle: tinyprog · PyPI (at pypi.org)02:01
ewenIn theory since https://github.com/timvideos/litex-buildenv/pull/119 we're installing tinyprog from github (not PyPI)02:02
tpbTitle: Install tinyprog from repo until new version is uploaded to PyPI. by cr1901 · Pull Request #119 · timvideos/litex-buildenv · GitHub (at github.com)02:02
ewenmithro: Looks like it might be file length related.  If I do "make image-flash" then it successfully programs.  If I do "make gateware-flash" then it fails on every attempt.02:06
ewenmithro: As best I can tell from TinyFPGA discourse thread that bug is supposed to be fixed in Oct 2018, possibly by 1.0.23. (But for some reason we're still installing 1.0.22b1 as best I can tell.)02:06
ewen$ make firmware-connect02:12
ewenflterm --port=/dev/ttyUSB0 --speed=11520002:12
ewen[FLTERM] Starting...02:12
ewenExecuting booted program at 0x2005800802:12
ewenMicroPython v1.9.4-534-gd2bd404 on 2019-01-09; litex with lm3202:12
ewen>>>02:12
ewenmithro: Seems like TinyProg has 1.0.22b1 version in the *git* version: https://github.com/tinyfpga/TinyFPGA-Bootloader/blob/0b70c51b8a3fa6b4b2ce4f8d31435ec80d0c8a3f/programmer/setup.py#L1402:56
tpbTitle: TinyFPGA-Bootloader/setup.py at 0b70c51b8a3fa6b4b2ce4f8d31435ec80d0c8a3f · tinyfpga/TinyFPGA-Bootloader · GitHub (at github.com)02:56
ewenYet https://pypi.org/project/tinyprog/#history has a 1.0.23 (but apparently only for Python 2).02:57
tpbTitle: tinyprog · PyPI (at pypi.org)02:57
ewenFTR, I've tried to encourage tinyfpga to release 1.0.23 in a way it can be installed on Python 3 (see, https://discourse.tinyfpga.com/t/issues-with-tinyprog-u-on-bx/628/16 and https://github.com/tinyfpga/TinyFPGA-Bootloader/issues/25#issuecomment-452556842)03:23
tpbTitle: Issues with tinyprog -u on BX - TinyFPGA (at discourse.tinyfpga.com)03:23
*** Kripton has quit IRC03:46
*** Kripton has joined #timvideos03:46
*** ewen has quit IRC04:26
*** tsglove2 has joined #timvideos04:59
*** rohitksingh_work has joined #timvideos05:00
*** springermac_ has joined #timvideos05:03
*** tsglove has quit IRC05:08
*** springermac has quit IRC05:08
*** futarisIRCcloud has joined #timvideos06:57
*** CarlFK has quit IRC07:32
*** cr1901_modern has quit IRC09:12
*** cr1901_modern has joined #timvideos10:43
*** futarisIRCcloud has quit IRC10:47
*** rohitksingh_work has quit IRC13:24
*** Kripton has quit IRC13:35
*** Kripton has joined #timvideos13:46
*** tsglove2 has quit IRC14:33
*** rohitksingh has joined #timvideos14:43
*** puck_ has quit IRC15:45
*** puck_ has joined #timvideos15:49
*** CarlFK has joined #timvideos17:23
*** ChanServ sets mode: +v CarlFK17:23
*** rohitksingh has quit IRC18:32
*** Kripton has quit IRC19:25
*** Kripton has joined #timvideos19:26
*** rohitksingh has joined #timvideos19:35
*** rohitksingh has quit IRC19:45
*** rohitksingh has joined #timvideos19:45
*** rohitksingh has quit IRC20:43
*** fischerm has joined #timvideos22:08
*** CarlFK has quit IRC23:54
*** Kripton has quit IRC23:57
*** Kripton has joined #timvideos23:58

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!