whitequark changed the topic of #glasgow to: glasgow debug tool · code https://github.com/GlasgowEmbedded/Glasgow · logs https://freenode.irclog.whitequark.org/glasgow
<esden> whitequark: it gets further now, the new error is `E: g.cli: FPGA configuration failed` it did work with C0.
<whitequark> esden: hm, that seems bad
<whitequark> can you show what happens with -vv ?
<esden> Yeah I will look when I am back home in an hour or so
<esden> errm wait sorry .. .(long day I am starting to make stupid mistakes)
<esden> https://pastebin.com/FpEGTWXn <- that should be better
<esden> ok I reverted to C0 and that worked fine and the selftest passed.
<whitequark> esden: ohhhh I know
<whitequark> sorry
<esden> :)
<whitequark> esden: duh. fixed...
<_whitenotifier-3> [GlasgowEmbedded/Glasgow] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/fja4V
<_whitenotifier-3> [GlasgowEmbedded/Glasgow] whitequark bc6523d - firmware: add revC0 support.
<esden> not revC1?
<whitequark> argh
<esden> just amend it noone will notice :)
<whitequark> repushed
<whitequark> yep
<_whitenotifier-3> [GlasgowEmbedded/Glasgow] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/fja4w
<_whitenotifier-3> [GlasgowEmbedded/Glasgow] whitequark d0bc373 - firmware: add revC1 support.
<whitequark> exactly what i did
<esden> :D
<whitequark> my brain's fried too
<_whitenotifier-3> [Glasgow] Error. The Travis CI build could not complete due to an error - https://travis-ci.org/GlasgowEmbedded/Glasgow/builds/546540374?utm_source=github_status&utm_medium=notification
<esden> no worries ... no rush :)
<esden> ohh damn that means I have to fix my firmware building ...
<esden> I was using marcan binary till now :)
<esden> so that might have caused issues too.. sorry
<whitequark> lemme build a firmware
<whitequark> ha. good thing ihex is text
<esden> yeah so I am now using sdcc v3.9.0 and it is still broken :/
<esden> maybe I am not rebuilding everything ... I went into the firmware directory and made `make clean` and then `make`
<esden> anything else I should do?
<esden> besides copying the ihex to the glasgow subdirectory?
<esden> in software
<esden> ahh vendor library
<esden> there we go!
<esden> at least that new firmware flashes now... still getting the config error... I will try your firmware now
<esden> ok with your firmware it is now failing with
<esden> with my firmware it is still failing to configure the fpga
<whitequark> esden: hm. weird.
<whitequark> esden: after rebuilding the firmware you need to copy it to software/glasgow/glasgow.ihex
<whitequark> the difference could be due to that
<whitequark> or, are you flashing it directly
<esden> I think I did that ... I will try again
<esden> >_< ... I am a dumb fuck... I did not merge your changes...
<esden> ok different error now
<whitequark> oooh
<whitequark> i mean shit, i missed more of them
<whitequark> but also oh
<whitequark> wait. what
<whitequark> OH
<whitequark> ok that wasn't something stupid
<whitequark> fixed
<_whitenotifier-3> [GlasgowEmbedded/Glasgow] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/fja4H
<_whitenotifier-3> [GlasgowEmbedded/Glasgow] whitequark d2d87e5 - access.direct.demultiplexer: fix a crash with args=None.
<esden> hehe :)
<esden> all the code emotions at once ... ;)
<esden> Sweet it is passing now! :D
<bgamari_> marcan, I have a batch of C1 boards sitting next to me
<esden> marcan, whitequark ok all four boards pass the selftest now, using my locally built firmware and setting the hardware revision to C1
<esden> so I think the FPGA might be ok after all :D
<esden> bgamari_: make sure to swap the voltage regulators before testing them...
<esden> or are those unpopulated boards?
<esden> I can definitely send this prototype to you as is. At least it seems to be starting up. :D
<esden> wrong window sorry ... :)
<esden> this is bit strange... one of the glasgows lights up the ERR led when it is pluged in ... others dont... but the selftest returns PASS on all of them...
<esden> the err led disappears when I start doing something with the board
<esden> ok some additional cleaning solved that problem... can't wait to assemble the boards with little less subsequent reworking :)
<whitequark> :D
<esden> is there a good way to control the LED one by one?
<esden> so that I can test/match them?
<whitequark> mm, not really, you have to patch the firmware
<sorear> short them out?
<esden> not sure how accurate that would be when they are pulled down ... that is probably not representative of real use
<whitequark> oh, you mean user led?
<esden> user led too
<whitequark> selftest lights all user leds correctly
<esden> yeah but I would like to light them up individually too that would be helpful
<esden> or display a pattern or something but I guess I will have to write some code for that
_whitelogger has joined #glasgow
_whitelogger has joined #glasgow
thaytan has quit [Ping timeout: 248 seconds]
thaytan has joined #glasgow
m4ssi has joined #glasgow
Jasjar has quit [Ping timeout: 245 seconds]
setrofim has joined #glasgow
Jasjar has joined #glasgow
_whitelogger has joined #glasgow
rappet has quit [Remote host closed the connection]
rappet has joined #glasgow
englishm has quit [Excess Flood]
englishm has joined #glasgow
m4ssi has quit [Remote host closed the connection]
esden has quit [Ping timeout: 252 seconds]
esden has joined #glasgow
Javantea has quit [Quit: reboot]
Javantea has joined #glasgow