| *** tpb has joined #tomu | 00:00 | |
| futarisIRCcloud | https://gitlab.com/theseus-cores/theseus-cores | 00:23 |
|---|---|---|
| tpb | Title: Theseus Cores / Theseus Cores · GitLab (at gitlab.com) | 00:23 |
| synaption[m] | I have poked at my problem some more. so far I have loaded the latest fomu-pi-gen raspian image on my pi and cloned the foboot repo onto the pi. when trying to run python3 foboot-bitstream.py --revision hacker I get OSError: Subprocess failed. After which I do not see build/gateware/top-multiboot.bin. I was wondering if anybody knows what I should do to make the build work or if there is an existing working .bin that | 01:10 |
| synaption[m] | I could use. Please and thankyou. | 01:10 |
| futarisIRCcloud | synaption[m]: xobs is on a plane I think. I compiled the latest commit 6caffc and put it here: https://drive.google.com/drive/folders/1V3EQxeNVsksBWtABJn9A59nCkAPtA3Nc?usp=sharing | 01:22 |
| tpb | Title: im-tomu - Google Drive (at drive.google.com) | 01:22 |
| *** pollo has quit IRC | 03:07 | |
| *** stv0g has joined #tomu | 03:08 | |
| *** pollo has joined #tomu | 03:10 | |
| *** stv0g has quit IRC | 03:13 | |
| *** rohitksingh_work has joined #tomu | 04:55 | |
| *** stv0g has joined #tomu | 05:20 | |
| *** stv0g has quit IRC | 05:24 | |
| futarisIRCcloud | https://media.ccc.de/v/osmodevcon2019-98-the-ice40-fpga | 05:30 |
| tpb | Title: media.ccc.de - The iCE40 FPGA (at media.ccc.de) | 05:30 |
| futarisIRCcloud | https://www.youtube.com/watch?v=ADJs89Np9A8 | 05:31 |
| *** stv0g has joined #tomu | 05:38 | |
| *** stv0g has quit IRC | 05:42 | |
| *** stv0g has joined #tomu | 05:56 | |
| *** stv0g has quit IRC | 06:01 | |
| *** AmosSam has left #tomu | 06:13 | |
| *** AmosSam has joined #tomu | 06:15 | |
| *** Summertime has quit IRC | 06:20 | |
| *** Summertime has joined #tomu | 06:21 | |
| *** stv0g has joined #tomu | 06:24 | |
| *** _stew_ has joined #tomu | 06:48 | |
| *** kuldeep_ has joined #tomu | 06:48 | |
| *** kuldeep has quit IRC | 06:48 | |
| AmosSam | This ice40up5k looks nice... 😎 | 07:28 |
| *** stv0g has left #tomu | 07:34 | |
| *** stv0g has joined #tomu | 07:54 | |
| *** stv0g has left #tomu | 08:05 | |
| *** jas4711 has quit IRC | 08:41 | |
| *** futarisIRCcloud has quit IRC | 08:48 | |
| *** futarisIRCcloud has joined #tomu | 10:03 | |
| *** rohitksingh_work has quit IRC | 13:01 | |
| *** AmosSam has left #tomu | 13:43 | |
| *** AmosSam has joined #tomu | 13:45 | |
| *** rohitksingh has joined #tomu | 13:54 | |
| *** buZz has joined #tomu | 14:18 | |
| *** buZz is now known as Guest80742 | 14:18 | |
| *** Guest80742 has joined #tomu | 14:19 | |
| *** Guest80742 is now known as buZz | 14:21 | |
| *** futarisIRCcloud has quit IRC | 15:32 | |
| *** rohitksingh has quit IRC | 15:36 | |
| *** rohitksingh has joined #tomu | 17:02 | |
| synaption[m] | I think I almost have the bootloader working. thanks for the help so far. I did "fomu-flash -w top-multiboot.bin" and that seemed to do the right thing, but when I put the fomu in my usb port and run dfu-util it doesn't seem to see anything. As a sanity check I was able to fomu-flash -w the prebuilt blink binary from the fomu-tests repo via spi. So im not sure the binary is right or more likely it's user error. | 17:31 |
| *** emeb has joined #tomu | 17:33 | |
| *** stv0g has joined #tomu | 18:02 | |
| *** rohitksingh has quit IRC | 18:16 | |
| xobs | synaption: what kind of machine are you using for USB? Is it windows? | 18:27 |
| *** rohitksingh has joined #tomu | 18:41 | |
| *** stv0g has quit IRC | 19:07 | |
| *** stv0g has joined #tomu | 19:07 | |
| *** stv0g1 has joined #tomu | 19:14 | |
| *** stv0g has quit IRC | 19:18 | |
| *** rohitksingh has quit IRC | 19:39 | |
| *** rohitksingh has joined #tomu | 19:41 | |
| synaption[m] | laptop | 20:20 |
| synaption[m] | with ubuntu 18.04 | 20:21 |
| xobs | Does the led start to blink? | 20:21 |
| synaption[m] | it does not | 20:21 |
| xobs | The led is started by the cpu fairly early on in the boot sequence. It should turn on immediately. | 20:22 |
| xobs | Maybe the power pins aren't making good contact? | 20:22 |
| xobs | Also, often the default user doesn't have permission to use USB directly, so you'll need to use sudo. But the first order of business is to get the led blinking. | 20:23 |
| synaption[m] | should it work if I just give it 5v? | 20:24 |
| xobs | synaption: it should. | 20:29 |
| synaption[m] | ya, I have nice bright lights with the blink binary, but nothing with top-multiboot | 20:39 |
| *** stv0g1 has left #tomu | 20:57 | |
| tnt | xobs: btw, did you try to run the USB compliance test suite against foboot ? | 20:57 |
| xobs | tnt: I didn't. What's that? | 20:58 |
| tnt | xobs: https://www.usb.org/usb2tools | 20:58 |
| xobs | Thanks, that looks outrageously useful. | 21:00 |
| *** futarisIRCcloud has joined #tomu | 22:12 | |
| *** stv0g has joined #tomu | 23:37 | |
| *** stv0g has quit IRC | 23:45 | |
| *** stv0g has joined #tomu | 23:46 | |
| *** stv0g has quit IRC | 23:50 | |
| xobs | mithro: the answer to "what's wrong with FreePDK45" is that it's fake. | 23:55 |
| xobs | FreePDK45 is a PDK that was created to be able to write papers about, because every other PDK was available under an NDA. From what I gather, most PDKs have upwards of one thousand design rules, but FreePDK45 has somewhere between 100-500. It's a thought experiment, and is a decent one at that. | 23:58 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!