<shorne>
ecpix5 looks nice, maybe its time for an upgrade. I need more than 256mb ram for glibc development/testing
lkcl has quit [Ping timeout: 240 seconds]
lkcl has joined #litex
shorne has quit [Ping timeout: 264 seconds]
<somlo>
shorne: just be extra gentle with the micro-usb connector :)
Degi_ has joined #litex
Degi has quit [Ping timeout: 264 seconds]
Degi_ is now known as Degi
peeps[zen] has joined #litex
peepsalot has quit [Ping timeout: 246 seconds]
shorne has joined #litex
Bertl_oO is now known as Bertl_zZ
tucanae47 has quit [Ping timeout: 260 seconds]
tucanae47 has joined #litex
levi has quit [Ping timeout: 260 seconds]
levi has joined #litex
_whitelogger has joined #litex
hansfbaier has quit [Quit: WeeChat 2.8]
hansfbaier has joined #litex
hansfbaier has quit [Read error: Connection reset by peer]
hansfbaier has joined #litex
hansfbaier has left #litex [#litex]
hansfbaier1 has joined #litex
hansfbaier1 has quit [Read error: Connection reset by peer]
hansfbaier has joined #litex
hansfbaier has quit [Read error: Connection reset by peer]
hansfbaier has joined #litex
hansfbaier has quit [Read error: Connection reset by peer]
hansfbaier has joined #litex
hansfbaier has quit [Read error: Connection reset by peer]
hansfbaier has joined #litex
hansfbaier has quit [Read error: No route to host]
hansfbaier has joined #litex
hansfbaier has left #litex [#litex]
ambro718 has joined #litex
ambro718 has quit [Read error: Connection reset by peer]
ambro718 has joined #litex
x56 has quit [Quit: Ծ-Ծ]
x56 has joined #litex
Bertl_zZ is now known as Bertl
peeps[zen] is now known as peepsalot
<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
Zguig has joined #litex
<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...
<Zguig>
I will load and check your code on my board
<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
<zyp>
I'd expect a warranty replacement in your case
<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)
<tpb>
Title: Imgur: The magic of the Internet (at imgur.com)
<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 :(
<zyp>
yeah
<zyp>
I'd say that's a defect
<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 :)
<geertu>
somlo: just needs a little bit of hot air? ;-)
<zyp>
should be reasonably easy to hotair it back
<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 :)
<somlo>
it's really a very nice idea, hopefully it can be sorted out
<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
<zyp>
I'm really not a fan of the sockets without mechanical tabs going into holes in the board
<zyp>
and I don't get why they didn't go with usb-c for the debug port too
<geertu>
zyp: yeah, it has more pins to hold the connector (in case you forget to solder the tabs ;)
<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
<Zguig>
but then no way to have usb 3 speed, isn't it?
<Zguig>
Maybe just wanted to keep the logic usb micro => usb2 et usb c => usb3?
<Zguig>
or maybe it is not related at all and it is only the manufacturers that did this association?
<zyp>
it's not related at all, usb-c can do anything
<mithro>
nickoe: Sounds like there might be a gateware / firmware mismatch or some other issue
<nickoe>
Is it correct that it should use stub fw?
<mithro>
nickoe: I don't know if anyone has been using the basys3 much
<mithro>
Generally the stub firmware is used on boards which don't have external DDR memory
<nickoe>
ok, and I guess that is true in this case with the basys3.
<mithro>
Generally the basys3 isn't a great fit for the type of things that LiteX-BuildEnv tends to target...
<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.
<mithro>
nickoe: That is what the stub firmware does
<nickoe>
but how can I figure out why it does not run?
<nickoe>
I am using vivado 2020.2 btw
pdp7 has quit [*.net *.split]
flammit has quit [*.net *.split]
flammit_ is now known as flammit
pdp7_ is now known as pdp7
kgugala has joined #litex
<nickoe>
mithro: Should I be able to run the micropython interpreter fw on the basys3?
<nickoe>
it does not seem to create build/basys3_base_vexriscv/software/micropython when building with make firmware and I have export FIRMWARE=micropython
<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...
<nickoe>
(LX P=basys3 C=vexriscv F=micropython) [nickoe@x280-arch litex-buildenv]$ ./scripts/build-micropython.sh .... that is
<mithro>
nickoe: I can't see enough of the output to confirm that you are running what I expect
<nickoe>
but at least there is that micropython build folder and a subsequent make firmware-load and serialboot seems to do something
<nickoe>
mithro: Output of what?
<mithro>
In that above pastebin
<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
<nickoe>
[FLTERM] v2.4-29-g47d3b15 Starting...
<nickoe>
Command not found
<nickoe>
s
<nickoe>
litex>
<nickoe>
litex> serialboot
<nickoe>
Booting from serial...
<nickoe>
Press Q or ESC to abort boot completely.
<nickoe>
sL5DdSMmkekro
<nickoe>
[FLTERM] Received firmware download request from the device.
<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
<nickoe>
*reffering
<nickoe>
oh, referring :D
<nickoe>
if just I could spell
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<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
<nickoe>
Why is it that different?
<nickoe>
Or rather, what makes it that different?
<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... <------
<nickoe>
Maybe I could do more in simulation for that somehow?
<mithro>
nickoe: The Arty A7 is the best / most well tested platform for a beginner who wants to use Xilinx Artix-7
<nickoe>
yeah, well, but unfortunately I don't have one of those :(
<nickoe>
same issue with that as you predicted.
<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
<nickoe>
mithro: the AX3 appears to have a XC7A35T-1CSG324I
<nickoe>
somlo: Story?
<nickoe>
not sure what the -1 before the CSG means.
<zyp>
speed grade 1
<nickoe>
xc7a35tcsg324-1 ... but that is the same -1 as the notation used in prjxray-db?
<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
<nickoe>
mm, shite happens
<zyp>
somlo, looking at it, I won't be surprised if mine ends up suffering the same fate
<daveshah>
Yep tabs on mine look a bit ropey too
<nickoe>
is it surface mount only?
<daveshah>
yeah
<daveshah>
which can be OK if done properly (e.g. the icebreakers)
<nickoe>
are the pads too small on the ecpix5?
<daveshah>
looks like the solder just didn't attach well for some reason
<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
<nickoe>
ugh
<nickoe>
would have been nicer with usb c :D
<zyp>
absolutely
<nickoe>
even if just usb 2.0
<zyp>
that's why they make 14-pin usb-c sockets
<nickoe>
just remember to connect both "sides" of the d+ and d- lines on the board