lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs :: Something to do? https://github.com/milkymist/bugs/issues
xiangfu has joined #milkymist
<wpwrak> kyak: (utf8) rejoice in the unblemished purity of plain 7 bit ASCII ! :)
<kristianpaul> xiangfu: hi !
<kristianpaul> sorry i remenber a log from you about a milkyminer taking too long to miner?
<kristianpaul> or just calculated hash once..
<wpwrak> dvdk: that sounds like the yaffs rootfs bug
<dvdk> wpwrak: already reformatted.
<dvdk> yes, remembered youm mail on devel@m
<xiangfu> kristianpaul, yes. I use the payload.py. it need ~5m give a result.
<kristianpaul> damn
<wpwrak> dvdk: i'm a bit surprised you ran into that one, though. what build did you install ?
<dvdk> 1.2 was 1.1 before
<wolfspra1l> good morning everybody
<wolfspra1l> new week, new luck
<wolfspra1l> kicad, boom! where are thou
<wpwrak> being hacked on, all of them i suppose :)
<wpwrak> dvdk: hmm. makes me wonder what's inside 1.2 then. that problem should have popped up only recently, yet might be gone in the daily builds already.
<dvdk> wpwrak: if even you don't know that... :)
<wpwrak> dvdk: i know very little about the actual builds, only about the things that may go into them ;-)
<xiangfu> dvdk, try reflash_m1.sh --qi --data
* dvdk tries to not think about what may be in there :)
<wpwrak> at daytime make saussages. at night, we hack code ...
<dvdk> xiangfu: just trying. but i though --qi should reflash everything, including --data!?
<xiangfu> dvdk, --qi will reflash everything except data partition.
<wpwrak> s/ss/s/
<dvdk> well, then help output from reflash_ben.sh is broken.
<dvdk> s/ben/m1
<xiangfu> dvdk, --data will reflash data partition.
<xiangfu> dvdk, ? you mean this one: CAUTION: if '--data' enable, it will REFLASH DATA PARTITION ?
<wpwrak> hmm, 1.2 ought to be first of march. very odd
<dvdk> xiangfu: ah, this line. skipped over it I guess :)
<dvdk> after seeing '--qi [VERSION] [--data] ' i gave up understanting command line :)
<wpwrak> they changes the permissions on march 2, though. maybe that just crept in at the last moment
<wpwrak> that would also mean that all the people who have upgraded to 1.2 have chosen to suffer in silence
<xiangfu> dvdk, there is a workaround method to exit rendering without keyboard.
<xiangfu> dvdk, Hold left button. it will exit the rendering mode. and goes to webupdate.
<dvdk> ah cool.
<xiangfu> the next release will automatic save all configuration.
cladamw has joined #milkymist
<wpwrak> xiangfu: you may want to check if 1.2 works with a yaffs created with an earlier release (and not auto-upgraded by my chmod commit from 4 days ago)
<xiangfu> wpwrak, yes.
<wpwrak> xiangfu: it seems that 1.2 may have picked up the new permission check in rtems, but nobody noticed. at least that would explain the problem dvdk has encountered
<xiangfu> wpwrak, yes.
<xiangfu> wpwrak, since I always reflash with --data. I must miss this problem.
<wpwrak> ah. maybe that explains it
<xiangfu> wpwrak, working on that in next hour. :)
cladamw_ has joined #milkymist
* xiangfu reflash back to 1.1 with data partition.
<wpwrak> ls -l /ssd shows 666 ?
<xiangfu> wpwrak, yes.: drw-rw-rw- 1 root root 512 Jan 1 00:00 ssd
<xiangfu> drwxr-xr-x 1 root root 7504 Jan 1 00:00 dev
<xiangfu> drwxr-xr-x 1 root root 536 Jan 1 00:00 etc
<xiangfu> drw-rw-rw- 1 root root 512 Jan 1 00:00 ssd
<xiangfu> ^^^ ls -l /
<xiangfu> now reflashing to latest qi image.
<xiangfu> without touch data partition
<wpwrak> 666, the number of the beast. so far so good :)
<xiangfu> cannot reproduce the bug. :( after reflash latest qi image. it still works fine.
<wpwrak> after reflashing 1.2 ? or the latest daily build ?
<xiangfu> after reflashing 1.2, it still works fine.
<wpwrak> and /ssd is still 666 ?
<xiangfu> let me do this again.
<xiangfu> 1. I run reflash_m1.sh --rc3 00 3a: it will download image from : http://milkymist.org/updates/2011-11-29/ include the data partition.
<wpwrak> perfect. that's certainly old enough
<GitHub61> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/4a2b950a6fefed364f2035794ed1cbc375237aae
<GitHub61> [board-m1/master] corrected J21 pin assignments - Adam Wang
<xiangfu> ls -l shows: drw-rw-rw- 1 root root 512 Jan 1 00:00 ssd, I can open file under patch editor.
<xiangfu> 2. now running reflash_m1.sh --release. which will donwload image from http://milkymist.org/updates/2012-03-01/ reflash without touch data partition.
<wpwrak> wait ...
<xiangfu> :(
<xiangfu> pressed 'Enter'
<wpwrak> that's odd. if you installed all the 2011-11-29 stuff, you should still be able to open files
<wpwrak> since RTEMS and data partition will both agree on using 666
<xiangfu> yes. I can open file under patch editor.
<wpwrak> oh, alright
<wpwrak> somehow, i read "can't" :)
<wpwrak> let's see how 2. goes then :)
<xiangfu> after [reflash_m1.sh --release], ls -l shows: drw-rw-rw- 1 root root 512 Jan 1 00:00 ssd
<wpwrak> very good
<xiangfu> patch editor open file just fine.
<wpwrak> excellent. that's how it should be
<wpwrak> so dvdk ran into something else
<wpwrak> thanks for checking !
<xiangfu> maybe after step_1. I should edit some file. and save etc..
<wpwrak> naw, the results look quite conclusive to me. with the permission problem, nothing worked
<xiangfu> ok. now I am reflashing the qi image.
<xiangfu> build under "2012-04-02/" it include the rtems-yaffs2 change.
<wolfspra1l> why did the frog pad and alpha grip keyboards not work for david?
<xiangfu> ls -l shows: drwxr-xr-x 1 root root 512 Jan 1 00:00 ssd.
<xiangfu> ( dvdk ran into something else) yes.
<wolfspra1l> looks like 2 interesting little keyboards
<xiangfu> have to dump the hid description for check more detail.
<kristianpaul> "new firmware doesn't allow me to exit patch via mouse click." arghhh that explain why on the demo i had i tough mouse support was broken !
<kristianpaul> but indeed is a good safe measure
rejon has joined #milkymist
<wolfspra1l> xiangfu: can you explain to david how to easily dump the hid descriptor?
<xiangfu> I have replied his email. and kyak's email.
<wolfspra1l> ah :-)
<kristianpaul> btw rii kbd also supports touchpad?
<wolfspra1l> you have one, no?
<kristianpaul> ergh,
<kristianpaul> yes
<kristianpaul> but havent tried touchpad..
<wolfspra1l> that should only take 1 second
<kristianpaul> will do .)
<wolfspra1l> you mean the touch area on it?
<wolfspra1l> just try :-)
<kristianpaul> yes
* kristianpaul brings a extra monitor from the closet
* kristianpaul turns on m1
<kristianpaul> ewww :)
<kristianpaul> I love yopu guys ! :)
<kristianpaul> what was the short cut to get a rtems shell.. Fallenou ?
<wolfspra1l> he's sleeping I'm sure
<kristianpaul> :)
<xiangfu> flterm --port /dev/ttyUSB0
<xiangfu> kristianpaul, ^
<xiangfu> kristianpaul, oh. you mean the rmmod?
<kristianpaul> nope, in FN
<xiangfu> kristianpaul, you cannot do that under FN. no such GUI for rtems shell.
<kristianpaul> hmm, sure?
<kristianpaul> ok
<xiangfu> from my understanding. have to connect through /dev/ttyUSB0
<kristianpaul> where is the no need for PC ;)
<kristianpaul> (kidding)
<kristianpaul> lol the ezcap IR control seems work ;)
<kristianpaul> ah, partially
<kristianpaul> well :)
<xiangfu> it not RC5.
proppy_ has joined #milkymist
xiangfu has joined #milkymist
<GitHub102> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/745baa077b33162046dfdebd4ccbad4030335870
<GitHub102> [board-m1/master] added VIDEOIN_A3V3, VIDEOIN_A1V8 components to fix ErrType(3): Pin connected to some others pins but no pin to drive it. (i.e. a local lable can't drive to a type of Power input). - Adam Wang
<GitHub76> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/64c29af1f0f4c1fdb9e4007f2fd69d45a5e721cc
<GitHub76> [board-m1/master] added ETH_A3V3, ETH_A1V8, ETH_PLL1V8 components to fix ErrType(3): Pin connected to some others pins but no pin to drive it. (i.e. a local lable can't drive to a type of Power input). - Adam Wang
cxadams has joined #milkymist
fpgaminer has joined #milkymist
Ladislas1 has joined #milkymist
proppy has joined #milkymist
whitequark has joined #milkymist
Thihi has joined #milkymist
ximian has joined #milkymist
mwk has joined #milkymist
kristianpaul has joined #milkymist
scrts has joined #milkymist
azonenberg has joined #milkymist
cladamw has joined #milkymist
cladamw has joined #milkymist
Jia has joined #milkymist
<wpwrak> ah, --qi also means "snapshot". that could explain dvdk's trouble. and indeed, the latest version is from 2012-04-02, just when that bug was around.
<wpwrak> --qi vs. --release does indeed seem a bit redundant. --qi is only a small superset of --release, and far from having the granularity of http://fidelio.qi-hardware.com/~xiangfu/build-milkymist/
<xiangfu> wpwrak, --qi have latest standby.bit splash.raw etc. for factory reflash in future. before the --release.
<xiangfu> if we already have those standby.bit etc. it's a bit redundant. :-)
<wpwrak> maybe just add the missing files to milkymist.org/updates/current/ ?
<wpwrak> they do exist under http://milkymist.org/updates/, just scattered over various directories
<wolfspra1l> if --qi means snapshot it should be called --snapshot, no?
<wpwrak> i'd rather call the things under build-milkymist a "snapshot"
<wpwrak> --qi is sort of a release, just sometimes slightly time-shifted. and sometimes with what looks like multiple tries
<wpwrak> compare: --release, http://milkymist.org/updates/
Martoni has joined #milkymist
<wpwrak> --snapshot is undocumented in the online help of reflash_m1.sh
<wpwrak> (to paraphrase some old text adventure games) you're in a maze of twisty little releases, all different ;-)
<wpwrak> i guess the things it takes are roughly what you can find via that page ...
<wpwrak> but i don't know that web interface. so maybe there are files you can't easily access.
Jia has joined #milkymist
elldekaa has joined #milkymist
<GitHub169> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/7e99faf754dc7d8ef5ca48c6a5bd97d3024064fa
<GitHub169> [board-m1/master] latest updated files - Adam Wang
voidcoder has joined #milkymist
<kyak> kristianpaul: sorry, i didn
<kyak> 't understand your reference to CSR bus
<kyak> what did you try to say? :)
<kyak> xiangfu: for the HID description - i will do that. But from what wpwrak said, there is only basic HID support and he was looking forward to Linux
<kyak> so.. not so clear - do you still need the HID description?
<xiangfu> I think so. I would like to checkout what is different on your keyboard.
<kyak> ok, then i'll send it as soon as i can
<kyak> when Linux hits M1, perhaps atusb would be upstream already
<kyak> this would have been awesome
<wpwrak> kyak: it's always good to know what weird descriptors people use :)
<kyak> wpwrak: so it is just for your amusement, i see :)
<wpwrak> kyak: amusement is what we can be sure of. all the rest is more difficult ;-)
<xiangfu> :-)
<kyak> xiangfu: what is the version of oscsend you are using? I'm using the one provided by liblo (if i remember correctly) package in arch linux.. It displays OSD fine (though no UTF-8), but the /patch command doesn't owkr
<kyak> *work
<xiangfu> for /patch. you have to configure under Flickernoise.
<kyak> ok, so it's not enabled by default
<xiangfu> no.
<kyak> is it a 'yes' no? :)
<xiangfu> for simple mode. there are no keyboard/IR/osc/midi configured.
<xiangfu> I have plan to try to automatic hook keyboard/IR/osc/midi configure under simple mode.
<kyak> what is the simple mode?
<kyak> is it the simple mode in Flickernoise interface when you start performance?
<xiangfu> yes. by default it using simple mode.
<xiangfu> and there is a configure mode.
<kyak> right.. i wondered what the configure mode means and what i can configure
<kyak> should i provide some configuration file?
<GitHub179> [board-m1] wpwrak pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/32e1f7479cedaea12dd9975444f0482557f06d3b
<GitHub179> [board-m1/master] r4/Power.sch: replaced PWR_FLAG with new POWERED - Werner Almesberger
<xiangfu> kyak, I would advice you update to recently daily build. that support automatic save all configure
<xiangfu> kyak, without this feature. it's a little bit hard to play with configure mode. :-)
<xiangfu> basically, it edit the 'Keyboard' 'MIDI' 'OSC' etc. and click the 'Save' under Control Panel.
<kyak> ok, that i can do.. though it's hard to upgrade without jtag properly working.. have to upload firmware to FTP and update from files
<xiangfu> then when start the performance. chose the 'Configure' not 'Simple mode'
<xiangfu> s/ it edit the 'Keyboard' 'MIDI' 'OSC' etc./you edit the 'Keyboard' 'MIDI' 'OSC' etc.
<kyak> i hope i don't need a keyboard to perform these configuration :)
<xiangfu> mouse is enough :-) but exit render mode have to use 'Ctrl + ESC' or HOLD left button. (this will exit render mode and goto webupdate)
<kyak> ok...
<kyak> xiangfu: do you know why holding middle button turns off M1 if it runs (as expected), but then it immediately turns on again (unexpected)?
<wpwrak> kyak: for the jtag, can you try with a different usb power ? also, which version of libusb do you have ? 1.0 or 0.1 ?
<xiangfu> kyak, hold middle button is for reboot.
<kyak> xiangfu: hm.. i thought pressign all three buttons is for reboot. How can i power off?
<xiangfu> kyak, there is no 'PowerOFF' any more.
<wpwrak> kyak: (middle) we used to have an "off" mode (standby) but that's gone now. so if you find any references to that behaviour, they're obsolete :)
<xiangfu> PowerOFF == unplug the power cable.
<kyak> wpwrak: my libusb is 1.0; what do you mean "different usb power"?
<wpwrak> err, different usb PORT
<wpwrak> sorry, multitasking confusion :)
<kyak> hm, ok.. it's just convenient to leave it plugged in and just power off.. but whatevrr :)
<kyak> wpwrak: i tried various ports of course, and different cable. But as i said, the same setup works fine for flashing Ben \
<wpwrak> (leave it) if you turn off the screen, you'll never notice :) power consumption in "standby" wasn't all that much below normal power consumption anyway
<xiangfu> ( if you turn off the screen) :-D
<kyak> ok, that's fine :)
<wpwrak> (jtag) that would suggest a software problem. hmm. i'm on ubuntu, also libusb 1.0, and it works just fine.
Alarm____ has joined #milkymist
Zorro has joined #milkymist
<kyak> wpwrak: if i install ubuntu in a virtual machine and jtag works there, will it prove that the problem is a software?
<kristianpaul> kyak: are you interested adding custom cores to milkymist SoC?
<kyak> kristianpaul: ahh, ok, i got you now :)
<Fallenou> kyak: I think yes
<Fallenou> it will prove it's just libusb/urjtag/linux related problem
<wpwrak> kyak: it would be a strong hint towards the problem being software, yes. or very wickedly buggy hardware :)
<kyak> ok, then i'll try ubuntu :)
<kristianpaul> kyak: i noticed you are interested on hdl coding, dont you?
<wolfspra1l> kyak: maybe you can just boot from a live ubuntu usb stick, or try ubuntu in a virtual machine
<wolfspra1l> as I explained, that fixed the same problem for me, and now I have a debian virtual machine just for m1 reflashing over jtag
<kyak> kristianpaul: "coding" - no :) hdl autocode generation - perhaps :)
<kyak> wolfspra1l: yep, booting from a stick - good idea
cladamw has joined #milkymist
<GitHub164> [board-m1] adamwang pushed 1 new commit to master: https://github.com/milkymist/board-m1/commit/de852f58dca2bf23ab14feac63db607132b30975
<GitHub164> [board-m1/master] added bigger text within each hierarchical rectangle by functional naming. - Adam Wang
<Fallenou> 5/win 36