| *** tpb has joined #litex | 00:00 | |
| *** hansfbaier has quit IRC | 00:21 | |
| *** hansfbaier has joined #litex | 00:23 | |
| *** lf_ has joined #litex | 00:40 | |
| *** lf has quit IRC | 00:40 | |
| *** ambro718 has quit IRC | 01:25 | |
| shorne | ecpix5 looks nice, maybe its time for an upgrade. I need more than 256mb ram for glibc development/testing | 01:35 |
|---|---|---|
| *** lkcl has quit IRC | 02:11 | |
| *** lkcl has joined #litex | 02:58 | |
| *** shorne has quit IRC | 03:04 | |
| somlo | shorne: just be extra gentle with the micro-usb connector :) | 03:18 |
| *** Degi_ has joined #litex | 03:34 | |
| *** Degi has quit IRC | 03:35 | |
| *** Degi_ is now known as Degi | 03:35 | |
| *** peeps[zen] has joined #litex | 04:26 | |
| *** peepsalot has quit IRC | 04:27 | |
| *** shorne has joined #litex | 05:10 | |
| *** Bertl_oO is now known as Bertl_zZ | 05:22 | |
| *** tucanae47 has quit IRC | 06:44 | |
| *** tucanae47 has joined #litex | 06:44 | |
| *** levi has quit IRC | 06:45 | |
| *** levi has joined #litex | 06:46 | |
| *** _whitelogger has quit IRC | 07:54 | |
| *** _whitelogger has joined #litex | 07:56 | |
| *** hansfbaier has quit IRC | 07:57 | |
| *** hansfbaier has joined #litex | 08:00 | |
| *** hansfbaier has quit IRC | 08:06 | |
| *** hansfbaier has joined #litex | 08:08 | |
| *** hansfbaier has left #litex | 08:10 | |
| *** hansfbaier1 has joined #litex | 08:24 | |
| *** hansfbaier1 has quit IRC | 08:27 | |
| *** hansfbaier has joined #litex | 08:28 | |
| *** hansfbaier has quit IRC | 08:29 | |
| *** hansfbaier has joined #litex | 08:30 | |
| *** hansfbaier has joined #litex | 08:32 | |
| *** hansfbaier has quit IRC | 08:34 | |
| *** hansfbaier has joined #litex | 08:36 | |
| *** hansfbaier has quit IRC | 08:57 | |
| *** hansfbaier has joined #litex | 08:58 | |
| *** hansfbaier has left #litex | 09:01 | |
| *** ambro718 has joined #litex | 09:17 | |
| *** ambro718 has quit IRC | 09:56 | |
| *** ambro718 has joined #litex | 09:56 | |
| *** x56 has quit IRC | 11:07 | |
| *** x56 has joined #litex | 11:09 | |
| *** Bertl_zZ is now known as Bertl | 12:02 | |
| *** peeps[zen] is now known as peepsalot | 12:32 | |
| somlo | anyone with a working ecpix5 interested in trying the linux-on-litex-rocket bitstream and boot.bin (should load via either sdcard or tftp)? http://mirror.ini.cmu.edu/ecpix5.tar.xz | 13:12 |
| *** Zguig has joined #litex | 13:50 | |
| Zguig | Hi somlo, I saw your misadventures with the USB connectors... I'm sorry for this. There is no way to sold back the connector? Or maybe try to see with the suppliers if they can give another to you... | 13:52 |
| Zguig | I will load and check your code on my board | 13:52 |
| zyp | somlo, if the usb signals weren't getting through and then the connector fell off way too easily, it sounds like a manufacturing defect, not soldering the connectors properly | 13:58 |
| zyp | I'd expect a warranty replacement in your case | 13:59 |
| Zguig | Looks good somlo :) | 14:04 |
| Zguig | Executing booted program at 0x80000000 | 14:04 |
| Zguig | --============= Liftoff! ===============-- | 14:04 |
| Zguig | bbl loader | 14:04 |
| Zguig | vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | vvvvvvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| zyp | I'm speaking from experience, I've had similar problems on stuff I've made, e.g: https://bin.jvnv.net/file/Kg4JE.JPG (pins 1 and 4 are not making contact) | 14:04 |
| Zguig | rrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rrrrrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rrrrrrrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rrrrrrrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rrrrrrrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rrrrrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rrrrrrrrrrrrr vvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rr vvvvvvvvvvvvvvvvvvvvvv | 14:04 |
| Zguig | rr vvvvvvvvvvvvvvvvvvvvvvvv rr | 14:04 |
| Zguig | rrrr vvvvvvvvvvvvvvvvvvvvvvvvvv rrrr | 14:04 |
| Zguig | rrrrrr vvvvvvvvvvvvvvvvvvvvvv rrrrrr | 14:04 |
| Zguig | rrrrrrrr vvvvvvvvvvvvvvvvvv rrrrrrrr | 14:04 |
| Zguig | rrrrrrrrrr vvvvvvvvvvvvvv rrrrrrrrrr | 14:04 |
| Zguig | rrrrrrrrrrrr vvvvvvvvvv rrrrrrrrrrrr | 14:04 |
| zyp | nice | 14:04 |
| Zguig | [ 0.000000] SBI specification v0.1 detected | 14:04 |
| Zguig | [ 0.000000] software IO TLB: mapped [mem 0x000000009f7fa000-0x000000009f7fa800] (0MB) | 14:04 |
| Zguig | [ 0.000000] riscv: ISA extensions acdfim | 14:04 |
| Zguig | [ 0.000000] riscv: ELF capabilities acdfim | 14:04 |
| Zguig | [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 | 14:04 |
| Zguig | [ 0.000000] pcpu-alloc: [0] 0 | 14:04 |
| Zguig | [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 128520 | 14:04 |
| Zguig | [ 0.000000] Kernel command line: earlycon=sbi console=hvc0 swiotlb=noforce | 14:04 |
| Zguig | [ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear) | 14:04 |
| Zguig | [ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear) | 14:04 |
| Zguig | [ 0.000000] Sorting __ex_table... | 14:04 |
| Zguig | [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off | 14:04 |
| Zguig | [ 0.000000] Memory: 499924K/522240K available (3765K kernel code, 3988K rwdata, 2048K rodata, 2880K init, 269K bss, 22316K reserved, 0K cma-reserved) | 14:04 |
| Zguig | [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 | 14:04 |
| Zguig | [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 | 14:04 |
| Zguig | [ 0.000000] riscv-intc: 64 local interrupts mapped | 14:04 |
| Zguig | [ 0.000000] plic: interrupt-controller@c000000: mapped 4 interrupts with 1 handlers for 2 contexts. | 14:04 |
| Zguig | [ 0.000000] random: get_random_bytes called from start_kernel+0x39e/0x556 with crng_init=0 | 14:04 |
| somlo | Zguig: thanks! did it make it all the way to the busybox shell ? | 14:07 |
| Zguig | Yep | 14:08 |
| Zguig | # ifconfig | 14:08 |
| Zguig | # ls /etc | 14:08 |
| Zguig | inittab | 14:08 |
| Zguig | # ifconfig -a | 14:08 |
| Zguig | eth0 Link encap:Ethernet HWaddr E6:E7:4C:CC:20:70 | 14:08 |
| Zguig | BROADCAST MULTICAST MTU:1500 Metric:1 | 14:08 |
| Zguig | RX packets:0 errors:0 dropped:0 overruns:0 frame:0 | 14:08 |
| Zguig | TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 | 14:08 |
| Zguig | collisions:0 txqueuelen:1000 | 14:08 |
| Zguig | RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) | 14:08 |
| Zguig | Interrupt:2 | 14:08 |
| Zguig | lo Link encap:Local Loopback | 14:08 |
| Zguig | LOOPBACK MTU:65536 Metric:1 | 14:08 |
| Zguig | RX packets:0 errors:0 dropped:0 overruns:0 frame:0 | 14:08 |
| Zguig | TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 | 14:08 |
| Zguig | collisions:0 txqueuelen:1000 | 14:08 |
| Zguig | RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) | 14:08 |
| somlo | awesome, thanks! I'll update linux-on-litex-rocket to include this | 14:08 |
| Zguig | Congrats! | 14:09 |
| Zguig | I used OpenOCD to load the firmware and have copied the image on SDCard | 14:10 |
| Zguig | openocd -f Research/litex/litex-boards/litex_boards/prog/openocd_ecpix5.cfg -c 'transport select jtag; init; svf ./Téléchargements/ecpix5/ecpix5.svf; exit' | 14:10 |
| somlo | Zguig: which of the two USB ports (usb-c, micro-usb) are you using for the console and/or programming? | 14:10 |
| Zguig | micro USB... | 14:11 |
| Zguig | From what is written here: http://docs.lambdaconcept.com/ecpix-5/features/debug.html | 14:11 |
| tpb | Title: Debug ECPIX-5 Documentation documentation (at docs.lambdaconcept.com) | 14:11 |
| Zguig | Only micro usb is able to be used | 14:12 |
| Zguig | Or the external JTAG | 14:12 |
| Zguig | Haven't tested the external JTAG yet, but I took the JTAG serial board from Lambda concept with the board in case of | 14:12 |
| Zguig | Do you have an equivalent? | 14:13 |
| Zguig | If you wantI can try with this also | 14:13 |
| zyp | somlo, micro-usb goes to the onboard ftdi for debug, usb-c is connected directly to the fpga | 14:15 |
| somlo | Zguig, zyp: https://imgur.com/a/DGuIvSL | 14:18 |
| tpb | Title: Imgur: The magic of the Internet (at imgur.com) | 14:18 |
| somlo | the pads pointed to by the arrow should have been "melted" against the connector better than they were, to keep it in place, which was apparently not the case :( | 14:19 |
| zyp | yeah | 14:19 |
| zyp | I'd say that's a defect | 14:19 |
| somlo | I should follow-up my email to lambdaconcepts to send them this image, in support of my "I didn't abuse the board" claim :) | 14:20 |
| geertu | somlo: just needs a little bit of hot air? ;-) | 14:20 |
| zyp | should be reasonably easy to hotair it back | 14:20 |
| somlo | geertu: I'm not set up to fix this on my end, unfortunately. But it'd be great if the vendor could fix it and restock it, or send it back to me, or whatever :) | 14:21 |
| somlo | it's really a very nice idea, hopefully it can be sorted out | 14:21 |
| Zguig | I would also say that this is a defect in the board, seems on your picture that the only soldering point were the two small pins | 14:22 |
| zyp | I'm really not a fan of the sockets without mechanical tabs going into holes in the board | 14:22 |
| zyp | and I don't get why they didn't go with usb-c for the debug port too | 14:23 |
| geertu | zyp: yeah, it has more pins to hold the connector (in case you forget to solder the tabs ;) | 14:24 |
| zyp | ha | 14:24 |
| Zguig | It seems related to the chipset used which is USB2 https://ftdichip.com/products/ft2232hq/ | 14:25 |
| tpb | Title: FT2232HQ - FTDI (at ftdichip.com) | 14:25 |
| zyp | there's no reason to not use usb-c for usb2, there's even a bunch of simplified usb-c sockets on the market that only implements the pins used by usb-2 | 14:27 |
| Zguig | but then no way to have usb 3 speed, isn't it? | 14:35 |
| Zguig | Maybe just wanted to keep the logic usb micro => usb2 et usb c => usb3? | 14:36 |
| Zguig | or maybe it is not related at all and it is only the manufacturers that did this association? | 14:37 |
| zyp | it's not related at all, usb-c can do anything | 14:39 |
| somlo | updated https://github.com/litex-hub/linux-on-litex-rocket (and the pinned issue with pre-built blobs) for ecpix5; Zguig, thanks again for running the tests! | 14:56 |
| *** Bertl is now known as Bertl_oO | 16:03 | |
| *** Bertl_oO is now known as Bertl | 17:03 | |
| *** Zguig has quit IRC | 17:43 | |
| zyp | somlo, this actually looks like a design mistake: https://bin.jvnv.net/file/Rohhx.jpg | 17:58 |
| zyp | socket is pulled a bit too far back, the flange is designed to protrude past the board edge | 17:58 |
| *** david-sawatzke[m has quit IRC | 18:10 | |
| *** david-sawatzke[m has joined #litex | 18:24 | |
| *** kgugala has quit IRC | 19:11 | |
| *** nickoe has joined #litex | 19:15 | |
| nickoe | hello | 19:15 |
| nickoe | I am looking at https://github.com/timvideos/litex-buildenv/wiki/Using | 19:16 |
| nickoe | Seeing https://github.com/timvideos/litex-buildenv/blob/master/platforms/basys3.py it looks like there is a migen platform def for the basys3 | 19:16 |
| nickoe | and some kind of soc definition in https://github.com/timvideos/litex-buildenv/blob/master/targets/basys3/base.py | 19:17 |
| nickoe | But how do I build that, just sourcing the env and doing make gateware does not work. | 19:17 |
| nickoe | I used, export PLATFORM=basys3; source litex-buildenv/scripts/enter-env.sh and get a console: (LX P=basys3 C=vexriscv) | 19:18 |
| nickoe | from what path should I be able to do "make gateware"? | 19:20 |
| mithro | nickoe: In the litex-buildenv directory | 19:28 |
| nickoe | mm, ok | 19:30 |
| nickoe | I think it did synth something | 19:30 |
| nickoe | but make gateware-load (not make load as on the wiki) fails | 19:31 |
| nickoe | embedded:startup.tcl:26: Error: Can't find board/digilent_basys3.cfg | 19:31 |
| nickoe | from openocd | 19:31 |
| nickoe | I guess | 19:31 |
| nickoe | mithro: Do I need to set the CPU for he basys3 board, or is the default of vexriscv ok? | 19:35 |
| mithro | default should be fine | 19:35 |
| mithro | nickoe: Log a bug about the openocd error | 19:35 |
| nickoe | mithro: and this is the correct repo? https://github.com/timvideos/litex-buildenv | 19:36 |
| nickoe | mithro: I used the one specifed on https://symbiflow-examples.readthedocs.io/en/latest/building-examples.html for flash ing before | 19:38 |
| tpb | Title: Building example designs SymbiFlow examples documentation (at symbiflow-examples.readthedocs.io) | 19:38 |
| nickoe | share/openocd/scripts/board/digilent_arty.cfg | 19:38 |
| nickoe | and that is available in the ocd checked out | 19:38 |
| nickoe | ok, usin that cfg it did flash and I see the litex | 19:42 |
| nickoe | bios | 19:42 |
| nickoe | mithro: v | 19:52 |
| nickoe | mithro: https://github.com/timvideos/litex-buildenv/issues/637 | 19:52 |
| nickoe | how does that flterm work? I did make firmware-load and it is stuck at "[FLTERM] v2.4-29-g47d3b15 Starting..." | 19:56 |
| mithro | nickoe: Hit enter? | 19:56 |
| nickoe | then what? | 19:57 |
| mithro | nickoe: Did a prompt appear? | 19:57 |
| nickoe | yes | 19:57 |
| nickoe | is there supposed to be some other firmware running than in the "bios? | 19:57 |
| mithro | Did you load some other firmware? | 19:57 |
| nickoe | I just did make firmware-load | 19:58 |
| mithro | nickoe: Type "serialload" possible then? | 19:58 |
| nickoe | https://dpaste.com/5DE66S2UZ | 19:59 |
| tpb | Title: dpaste: 5DE66S2UZ (at dpaste.com) | 19:59 |
| mithro | nickoe: This is documented at https://github.com/timvideos/litex-buildenv/wiki/HowTo-FuPy-on-a-Digilent-Arty-A7 for example | 19:59 |
| mithro | nickoe: That log shows you as having typed `make firmware-connect-basys3`not `make firmware-load` ? | 19:59 |
| nickoe | oh, well, I don't see any difference anyway | 20:00 |
| mithro | `make firmware-load` will load firmware when it sees the serialboot prompt | 20:00 |
| nickoe | mm | 20:01 |
| nickoe | here you go https://dpaste.com/C8EEKSR4Q | 20:01 |
| tpb | Title: dpaste: C8EEKSR4Q (at dpaste.com) | 20:01 |
| nickoe | It still sort of errors. | 20:01 |
| nickoe | mithro: I am not really sure what to expect, but that looks like something is not quite right to me | 20:03 |
| mithro | nickoe: Can you log an bug about the `[FLTERM] Unable to open kernel image (request ignored).: No such file or directory` line? | 20:03 |
| mithro | nickoe: Can you check to see if `build/basys3_base_vexriscv/software/firmware/firmware.bin`exists? | 20:05 |
| mithro | Looks like there is some confusing about if the firmware you are using is the stub firmware or not | 20:07 |
| nickoe | file ./build/basys3_base_vexriscv/software/stub/firmware.bin | 20:07 |
| nickoe | ./build/basys3_base_vexriscv/software/stub/firmware.bin: data | 20:07 |
| mithro | nickoe: stub != firmware (yes there is firmware called stub and firmware called firmware) | 20:07 |
| nickoe | ?? | 20:07 |
| nickoe | What do do to make it run some firmwarE? | 20:08 |
| mithro | Try "export FIRMWARE=stub" and then `make firmware-load` again | 20:09 |
| nickoe | if I dod that and type serialboot then it looks like it is doing stuff, at lesat it is showing some progress in the form of a percentage. | 20:10 |
| nickoe | [FLTERM] Received firmware download request from the device. | 20:10 |
| nickoe | [FLTERM] Uploading kernel (7848 bytes)... | 20:10 |
| nickoe | 44% | 20:10 |
| nickoe | mithro: is that "stub" fw supposed to do anything? | 20:11 |
| mithro | It's only a little more advanced than the bios -- I think you can toggle LEDs and stuff | 20:12 |
| nickoe | I don't get a console | 20:12 |
| nickoe | it is just like this, even if I hit enter a couple of times, https://dpaste.com/66QCEYGNN | 20:13 |
| tpb | Title: dpaste: 66QCEYGNN (at dpaste.com) | 20:13 |
| *** flammit_ has joined #litex | 20:18 | |
| *** pdp7_ has joined #litex | 20:18 | |
| nickoe | mithro: So what to do now? | 20:18 |
| mithro | nickoe: Sounds like there might be a gateware / firmware mismatch or some other issue | 20:18 |
| nickoe | Is it correct that it should use stub fw? | 20:19 |
| mithro | nickoe: I don't know if anyone has been using the basys3 much | 20:19 |
| mithro | Generally the stub firmware is used on boards which don't have external DDR memory | 20:20 |
| nickoe | ok, and I guess that is true in this case with the basys3. | 20:20 |
| mithro | Generally the basys3 isn't a great fit for the type of things that LiteX-BuildEnv tends to target... | 20:21 |
| nickoe | I don't need a big softcpu, just a small one to run a bit of code on to be able to interface with serial for example and write to a few regs. | 20:23 |
| mithro | nickoe: That is what the stub firmware does | 20:23 |
| nickoe | but how can I figure out why it does not run? | 20:23 |
| nickoe | I am using vivado 2020.2 btw | 20:24 |
| *** pdp7 has quit IRC | 20:26 | |
| *** flammit has quit IRC | 20:26 | |
| *** pdp7_ is now known as pdp7 | 20:26 | |
| *** flammit_ is now known as flammit | 20:26 | |
| *** kgugala has joined #litex | 20:32 | |
| nickoe | mithro: Should I be able to run the micropython interpreter fw on the basys3? | 20:35 |
| nickoe | it does not seem to create build/basys3_base_vexriscv/software/micropython when building with make firmware and I have export FIRMWARE=micropython | 20:36 |
| mithro | nickoe: I'm unclear what is being used as the "main memory" on the basys3 -- as it doesn't have external DDR or the big SP RAM blocks that the ice40up5k has... | 20:36 |
| mithro | nickoe: https://github.com/timvideos/litex-buildenv/wiki/HowTo-FuPy-on-a-Digilent-Arty-A7 | 20:37 |
| nickoe | the only diffrence on that seems to be that it sets TARGET, is that required? | 20:38 |
| mithro | nickoe: You have to use the `./scripts/build-micropython.sh` | 20:38 |
| mithro | nickoe: As the micropython build system is outside the normal litex-buildenv system | 20:39 |
| nickoe | mm, ok, I would have dhough that the download-env-sh script would take care of that when sourced | 20:39 |
| nickoe | into an env with the FIRMWARE=micropython | 20:39 |
| nickoe | mithro: it errors with https://dpaste.com/5895SX24T | 20:41 |
| tpb | Title: dpaste: 5895SX24T (at dpaste.com) | 20:41 |
| nickoe | (LX P=basys3 C=vexriscv F=micropython) [nickoe@x280-arch litex-buildenv]$ ./scripts/build-micropython.sh .... that is | 20:41 |
| mithro | nickoe: I can't see enough of the output to confirm that you are running what I expect | 20:42 |
| nickoe | but at least there is that micropython build folder and a subsequent make firmware-load and serialboot seems to do something | 20:42 |
| nickoe | mithro: Output of what? | 20:43 |
| mithro | In that above pastebin | 20:43 |
| nickoe | right now it appears to flash a min from the micropython folder flterm --port=/dev/ttyUSB1 --kernel=build/basys3_base_vexriscv/software/micropython/firmware.bin --speed=115200 | 20:43 |
| nickoe | [FLTERM] v2.4-29-g47d3b15 Starting... | 20:43 |
| nickoe | s | 20:43 |
| nickoe | Command not found | 20:43 |
| nickoe | litex> | 20:43 |
| nickoe | litex> serialboot | 20:43 |
| nickoe | Booting from serial... | 20:43 |
| nickoe | Press Q or ESC to abort boot completely. | 20:43 |
| nickoe | sL5DdSMmkekro | 20:43 |
| nickoe | [FLTERM] Received firmware download request from the device. | 20:43 |
| nickoe | [FLTERM] Uploading kernel (218752 bytes)... | 20:43 |
| nickoe | 2% | 20:43 |
| nickoe | wopps | 20:43 |
| nickoe | I meant to paste https://dpaste.com/CM532M73Y | 20:43 |
| tpb | Title: dpaste: CM532M73Y (at dpaste.com) | 20:43 |
| mithro | I expect it'll fail | 20:44 |
| nickoe | mithro: Sorry, but I am not sure what output you are refferint to for the tail of the output of ./scripts/build-micropython.s | 20:45 |
| nickoe | *reffering | 20:45 |
| nickoe | oh, referring :D | 20:45 |
| nickoe | if just I could spell | 20:45 |
| *** futarisIRCcloud has quit IRC | 20:46 | |
| mithro | Given the current state of things the basys is just *not* a good platform to be used here -- There are just too many things on the basys board that do not work like every other platform | 20:46 |
| nickoe | Why is it that different? | 20:47 |
| nickoe | Or rather, what makes it that different? | 20:47 |
| mithro | nickoe: I'm unclear what is being used as the "main memory" on the basys3 -- as it doesn't have external DDR or the big SP RAM blocks that the ice40up5k has... <------ | 20:48 |
| nickoe | mithro: it appers to use flash, https://github.com/timvideos/litex-buildenv/blob/master/targets/basys3/base.py#L84-L91 | 20:49 |
| nickoe | As far as I understand it. | 20:49 |
| nickoe | I have this board as well, https://www.enclustra.com/en/products/fpga-modules/mars-ax3/ , but I am waiting for a JTAG for it | 20:50 |
| tpb | Title: Enclustra FPGA Solutions | Mars AX3 | Xilinx Artix-7 28nm FPGA Module | 7A35T | 7A50T | 7A100T (at www.enclustra.com) | 20:50 |
| nickoe | Maybe I could do more in simulation for that somehow? | 20:51 |
| mithro | nickoe: The Arty A7 is the best / most well tested platform for a beginner who wants to use Xilinx Artix-7 | 20:51 |
| nickoe | yeah, well, but unfortunately I don't have one of those :( | 20:52 |
| nickoe | same issue with that as you predicted. | 21:20 |
| somlo | zyp: thanks, that makes sense... either way, I emailed my picture and story to the folks at lambdaconcepts, we'll see if/when they get back to me | 21:23 |
| nickoe | mithro: the AX3 appears to have a XC7A35T-1CSG324I | 21:24 |
| nickoe | somlo: Story? | 21:24 |
| nickoe | not sure what the -1 before the CSG means. | 21:31 |
| zyp | speed grade 1 | 21:31 |
| nickoe | xc7a35tcsg324-1 ... but that is the same -1 as the notation used in prjxray-db? | 21:32 |
| nickoe | https://github.com/SymbiFlow/prjxray-db/tree/master/artix7/xc7a35tcsg324-1 ? | 21:32 |
| zyp | that sounds likely | 21:32 |
| nickoe | ok | 21:32 |
| somlo | nickoe: not a very exciting story -- I ended up damaging the micro-usb port on my ecpix5 due to some weak soldering done by the PCB shop that ended up fabricating the board | 22:07 |
| nickoe | mm, shite happens | 22:08 |
| zyp | somlo, looking at it, I won't be surprised if mine ends up suffering the same fate | 22:14 |
| daveshah | Yep tabs on mine look a bit ropey too | 22:15 |
| nickoe | is it surface mount only? | 22:15 |
| daveshah | yeah | 22:21 |
| daveshah | which can be OK if done properly (e.g. the icebreakers) | 22:21 |
| nickoe | are the pads too small on the ecpix5? | 22:22 |
| daveshah | looks like the solder just didn't attach well for some reason | 22:23 |
| zyp | daveshah, because the socket is not located properly, the flange should have been past the board edge: https://bin.jvnv.net/file/Rohhx.jpg | 22:23 |
| nickoe | ugh | 22:24 |
| nickoe | would have been nicer with usb c :D | 22:24 |
| zyp | absolutely | 22:24 |
| nickoe | even if just usb 2.0 | 22:24 |
| zyp | that's why they make 14-pin usb-c sockets | 22:25 |
| nickoe | just remember to connect both "sides" of the d+ and d- lines on the board | 22:25 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
