Topic for #milkymist is now Milkymist One, Milkymist SoC & Flickernoise development channel (LLHDL/Antares are welcome too) :: Logs: http://en.qi-hardware.com/mmlogs :: JFDI
mumptai joined #milkymist
Gurty joined #milkymist
<sh4rm4> <wpwrak> hmm, "masala" must mean something naughty in india
<sh4rm4> it means "mix"
<sh4rm4> i.e. gharam masala = hot mix (spice mix)
<wpwrak> maybe with some second meaning ? like in english, a baffling number of words can be used synonymously to "having sex"
<sh4rm4> dunno, but maybe the porn site owners had something "interracial" in mind
<wpwrak> e.g., do, have, take, jump, ...
<wpwrak> ah yes, that could be too. "mix" would work well then.
wolfspraul joined #milkymist
wolfspraul joined #milkymist
Technicus joined #milkymist
aw joined #milkymist
aw_ joined #milkymist
wolfspraul joined #milkymist
xiangfu joined #milkymist
<wolfspraul> aw_: good morning!
<aw_> wolfspraul, hi good morning
wolfspra1l joined #milkymist
wolfspraul joined #milkymist
elldekaa joined #milkymist
elldekaa joined #milkymist
elldekaa joined #milkymist
elldekaa joined #milkymist
elldekaa joined #milkymist
<aw_> xiangfu, do we have a quick and easy way to re-build/make if I changed following those two files?
<aw_> and in the end I want a image of test bin?
<aw_> since i can't build them now. :)
<xiangfu> aw_, all you need do is type make under 'autotest-m1/' folder.
<xiangfu> aw_, do you have 'lm32-rtems4.11-gcc' ?
<xiangfu> let's do this now. :)
<aw_> but if i modify some content in vin.c file, so will i still need just make under 'autotest-m1/'?
<xiangfu> aw_, if you only modify the vin.c file. you needs 'make clean all' under 'autotest-m1/'
<xiangfu> aw_, like: MMDIR=../../milkymist.git/ make clean all
<xiangfu> MMDIR is the path of milkymist.git
<xiangfu> but first you need the compiler (lm-rtems4.11-gcc) in your system.
<aw_> second...i'm checking my 'milkymist' folder...
<aw_> xiangfu, alright. now how to check if my system has (lm-rtems4.11-gcc) ?
<xiangfu> there should be no lm-rtems4.11-gcc in your system. let's check. just type lm-rtems4.11-gcc. see what it output.
<aw_> command not found
<roh> kristianpaul: they use an spi usb controller
<roh> max3421
<kristianpaul> ahh
<roh> 'cheaters' ;)
<kristianpaul> indeed
<aw_> xiangfu, wow...big
<aw_> xiangfu, extracted done.
<xiangfu> you have to move the folder (rtems-4.11) to /opt/
<xiangfu> aw_, then add those lines to the end of ~/.bashrc : http://dpaste.com/664664/
<xiangfu> http://dpaste.com/664664/ line:5 change to your own milkymist.git patch.
<xiangfu> s/patch/path/
<aw_> xiangfu, where's ~/.bashrc ? under /opt ? or /opt/rtems-4.11 ?
<xiangfu> aw_, just 'gedit ~/.bashrc'
<xiangfu> ~ means your HOME folder.
<aw_> like this? adam@adam-laptop:/home$
<xiangfu> like /home/adam
<xiangfu> ~ == /home/adam
<aw_> ha
<wolfspraul> ok, so i understand the rc4 reset_ic and usb power switch design verification looks good so far
<wolfspraul> and the adv7181c is being tested right now
<aw_> wolfspraul, oah~yes. but I have to learn make on my site firstly then to check registers's setting on how difference between 7181C and 7181B. phew~ long way for me. ha~ :-)
<wolfspraul> if you believe the soldering is ok, maybe we should just send out one board to Werner?
<wolfspraul> to speed up...
<wolfspraul> let's see how it goes today first
<wolfspraul> Xiangfu is going to a milkymist event for the rest of the day, so his availability may be spotty
<aw_> xiangfu, like this? http://dpaste.com/664683/
<wolfspraul> maybe lekernel comes back later and can give you some binaries to speed up, don't know...
<xiangfu> aw_, yes. correct.
<wolfspraul> or we just send out the board to werner and take the risk that it has hardware flaws?
<wolfspraul> so we have multiple options, let's see how it goes today first
<wolfspraul> thanks for the good work!
<xiangfu> aw_, add one more line to the end of that file: 'export MMDIR=/home/adam/milkymist/milkymist.git'
<aw_> wolfspraul, don't know. maybe register settings needs to be changed a lot or few. I don't think that I can quickly digging into this.
<aw_> but good is that phew~ learn something new for me (always stupid in s/w)... :(
<xiangfu> aw_, after add that line. open a new terminal.
<aw_> wolfspraul, seems my first pre-rc4 board is almost soldering well.
<wolfspraul> aw_: just work on it step by step, concentrated and it will be fine
<wolfspraul> I'm just preparing you that xiangfu will be mostly offline or reply delayed for the rest of the day
<wolfspraul> after 12.30 or so
<wolfspraul> maybe lekernel can quickly make some test binaries for you and accelerate the verification
<aw_> except there's some pins of video decoder we still don't know if it works.
<wolfspraul> or we send out boards without verification
<aw_> wolfspraul, oah..yes
<wolfspraul> lots of options
<wolfspraul> bbiab
<aw_> xiangfu, done ... then ?
<xiangfu> yes. I will go to a event. there is a big device call 'Media Wall' , when it closed. it's just a big box. when it's open. there are screen. speakers. DMX LED light, DMX laser, etc.
<xiangfu> aw_, yes. open a new terminal. and goto the autotest-m1.git/ folder. run 'git pull' first. since I just fix the libs DEPENDS.
<aw_> aha...okay...you go first.
<xiangfu> aw_, I will leave at ~12:30. so we can finish the compile at lease. :)
<xiangfu> aw_, after run 'git pull' , goto the autotest-m1.git/src/ folder. just run 'make' you will get a new test bin that include the vin.c's modify. :)
<xiangfu> 'make' ==> will compile boot.bin for you. include all libs modify. like vin.c
<xiangfu> 'make load' ==> will run 'flterm --port /dev/ttyUSB0 --kernel boot.bin' for you. :)
<aw_> phew~ check where my autotest-m1.git/ folder, it seems that i git cloned before. damn it. :)
<aw_> does the autotest-m1.git under /milkymist folder?
<xiangfu> aw_, depends on you. :)
<xiangfu> aw_, I just put them under milkymist folder.
<aw_> xiangfu, okay..git cloned it under milkymist folder
<xiangfu> yes. goto autotest-m1.git/src. type 'make' then there will be 'boot.bin'
<aw_> adam@adam-laptop:~/milkymist/autotest-m1/src$ make
<aw_> Makefile:1: /software/include.mak: No such file or directory
<aw_> make: *** No rule to make target `/software/include.mak'. Stop.
<xiangfu> aw_, add another line : export MMDIR=/home/adam/milkymist/milkymist.git to your ~/.bashrc
<xiangfu> aw_, then open a new terminal. try again.
<aw_> xiangfu, i added: http://dpaste.com/664695/
<aw_> did I miss another sub-folder /milkymist.git/ ?
<aw_> my cd is 'adam@adam-laptop:~/milkymist/autotest-m1/src$'
<xiangfu> aw_, can you close the terminal and open a new one. try adain.
<xiangfu> again
<kristianpaul> xiangfu: you may have already downloaded ISE 13.3 in fidelio?
<xiangfu> kristianpaul, no.
<kristianpaul> morning btw !! :-)
<xiangfu> still 13.2
<xiangfu> kristianpaul, good morning.
<aw_> yes. i reopened:
<aw_> adam@adam-laptop:~/milkymist/autotest-m1/src$ make
<aw_> Makefile:1: /home/adam/milkymist/milkymist.git/software/include.mak: No such file or directory
<aw_> make: *** No rule to make target `/home/adam/milkymist/milkymist.git/software/include.mak'. Stop.
<aw_> adam@adam-laptop:~/milkymist/autotest-m1/src$
<aw_> kristianpaul, good morning. :)
<xiangfu> aw_, ok. what is '/home/adam/milkymist/milkymist.git/' is that the correct path.
<xiangfu> aw_, what is the output of 'ls /home/adam/milkymist/' and 'ls /home/adam/milkymist/milkymist.git'?
<kristianpaul> arghhh, 5GB!!! :-|
<kristianpaul> okay good night !
<aw_> xiangfu, 'ls /home/adam/milkymist/' : http://dpaste.com/664698/
<xiangfu> aw_, ok.
<xiangfu> aw_, try to do this:
<aw_> xiangfu, 'ls /home/adam/milkymist/milkymist.git' : http://dpaste.com/664699/
<xiangfu> 1. mv /home/adam/milkymist/autotest-m1 /home/adam
<xiangfu> 2. mv /home/adam/milkymist/ /home/adam/milkymist.git
<xiangfu> 2. mkdir /home/adam/milkymist/
<xiangfu> 4. mv /home/adam/milkymist.git /home/adam/autotest-m1 /home/adam/milkymist/
<xiangfu> and cd /home/adam/milkymist/autotest-m1/src. try again. :D
<aw_> adam@adam-laptop:~/milkymist/autotest-m1/src$ make
<aw_> lm32-rtems4.11-gcc -I/home/adam/milkymist/milkymist.git/software/include -I/home/adam/milkymist/milkymist.git/software/include/base -I/home/adam/milkymist/milkymist.git/tools -nostdinc -c -o crt0.o crt0.S
<aw_> /opt/rtems-4.11/bin/lm32-rtems4.11-gcc: 2: Syntax error: ")" unexpected
<aw_> make: *** [crt0.o] Error 2
<aw_> xiangfu, i just git pull: adam@adam-laptop:~/milkymist/milkymist.git$ git pull
<xiangfu> aw_, yes.
<aw_> else i missed?
<aw_> if you need go 'Media Wall' just go, we check this later. ;-)
DJTachyon joined #milkymist
<wpwrak> aw_: seems that you have a 32 bit machine while the pre-compiled SDK is for 64 bit. uname -m is reporting something like "i686", right ? (and not "x86_64")
<aw_> hi, yes xiangfu also found my system is "i686'. :(
<aw_> he just helped me 'remotely' to compile new one. phew~
<wpwrak> hm,, and i can't see any 32 bit SDK in his directories. i thought he once had made one
<wpwrak> oh, wow :)
<aw_> he could help me after he's back... well... meanwhile I could do a check on datasheet though. :)
<wpwrak> apt-get install texinfo ?
<wpwrak> there may be a number of things you'll have to install if you're doing this kind of build for the first time. but let's see.
<aw_> downloading ...
<aw_> done.... so keep 'make' under 'adam@adam-laptop:~/milkymist/scripts.git/compile-lm32-rtems$ ' folder ?
<aw_> he told me this will need 1 hr. :)
<wpwrak> (make) yeah, just retry the last command
<aw_> make ... again now.
<aw_> :)
<wpwrak> (1 hour) depends a lot on your system ;-) what does cat /proc/cpuinfo say ?
<wpwrak> dual-core, good. if you're using "make" without options now, you could try make -j2 to use both cores instead
<aw_> wow... do you next time i can always use 'make -j2' ?
<aw_> do you mean ... :)
<wpwrak> yes :)
<aw_> wowho...
<aw_> great info.
<wpwrak> note that, if a build fails, parallel make (make -j2, ...) may produce more confusing error messages, because the command that fails may not be the last command
<aw_> okay
<wpwrak> so if this happens, you can just do a make (without -j), and you'll get the regular error. that "make" may either come back quickly or take a while. depends on how the thing is structured.
<wpwrak> of course, if you just re-make things that are known to work or that have only small changes, there's no problem
<aw_> alright... my goal today is try to learn this firstly then see how difference between 7181B & C video decoder, if i see there's obvious/clear register settings then i modify files myself and make under 'autotest-m1.git' folder. phew~
<aw_> at least hope to see capture from video-in source. :-) don't know ...
<aw_> hmm...thinking(idea) and doing(s/w) are super different thing to me. :)
<wpwrak> takes a bit of time to become a master. but you're on a good path :)
<aw_> thank you sir. :)
DJTachyon joined #milkymist
<wpwrak> hmm, you're upgrading from 7181B to 7181C or from 7125 to 7181C ?
<aw_> from 7181B to 7181C
<aw_> make is done: "touch .install.gcc.ok" ...
<wpwrak> hmm, my m1rc3 has a 7125
<aw_> no...the 7125 is a encoder from digital r,g,b into analog r/g/b :)
<wpwrak> aah, wrong end. i see :-)
<aw_> 7125 is U18, i replaced 7181C instead on U21 footprint for video con (g/b/r)
<aw_> :-)
<wpwrak> they seems to have changed the multiplexer
<aw_> i got err 2: http://dpaste.com/664764/ when typed 'make' under '~/milkymist/autotest-m1.git/src$'
<aw_> how do think that err 2 ?
<wpwrak> *hmm* :)
<aw_> 'avr-gcc: Command not found' ?
<aw_> what's that 'avr-gcc' ?
<wpwrak> let's see how demanding that build process is ...
<aw_> you mean you check your site ?
<wpwrak> you could try apt-get install gcc-avr
<aw_> do you mean that to see "Makefile" always to see its build process ?
<aw_> okay
<wpwrak> if that doesn't help (you may get now, weird errors indead), then you'd have to build avr-gcc from sources
<wpwrak> the instructions for building a somewhat recent version of avr-gcc would be here: http://projects.qi-hardware.com/index.php/p/ben-wpan/source/tree/master/atusb/fw/README
<aw_> installed .. gcc-avr
<wpwrak> maybe doa avr-gcc --version ? (just the first line)
<aw_> solved ... then another:
<wpwrak> victory ! :)
<aw_> lm32-rtems4.11-ld: cannot find -lmath
<aw_> make: *** [boot.elf] Error 1
<wpwrak> wow. that's weird
<aw_> :)
kristianpaul joined #milkymist
<wpwrak> i dont't even know that that library is. i can see a libmath for C++, one for Perl, ... and then libmathlib2-dev - CERNLIB data analysis suite
<wpwrak> but none of this sound quite right
<wpwrak> what were you trying to build when you got the -lmath error ?
<aw_> phew ~ just googled ... don't know hehe ...
<aw_> after installed gcc-avr then go to '~/milkymist/autotest-m1.git/src$' folder and 'make'
<wpwrak> works here ;-)
wolfspraul joined #milkymist
<wpwrak> aha. libmath is a milkymist.git-ishm
<wpwrak> make, in milkymist.git, make -C software/libmath
<wpwrak> then try finishing the autotest build again
<wpwrak> while you're at it, also
<wpwrak> make -C software/libhal
<wpwrak> and
<wpwrak> make -C software/libfpvm
<wpwrak> (i hope the last one is right. there are two ways of building libfpvm and i'm not sure if they conflict or not)
<aw_> followed them above. second ...
<aw_> chmod -x boot.elf
<aw_> lm32-rtems4.11-objcopy -j .text -j .data -j .rodata -O binary boot.elf boot.bin
<aw_> chmod -x boot.bin
<aw_> make -C /home/adam/milkymist/milkymist.git/tools
<aw_> make[1]: Entering directory `/home/adam/milkymist/milkymist.git/tools'
<aw_> make[1]: Nothing to be done for `all'.
<aw_> make[1]: Leaving directory `/home/adam/milkymist/milkymist.git/tools'
<aw_> /home/adam/milkymist/milkymist.git/tools/mkmmimg boot.bin
<aw_> CRC32 (boot.bin): 8f262684
<aw_> does this mean it's done on making (boot.bin) ?
<wpwrak> i have no clue what yuo just did ;-)
<wpwrak> did you run make -C software/libmath ?
<wpwrak> or just "make" ?
<aw_> oah..yes i did your instructions.
<aw_> make -C software/libmath under milkymist.git
<aw_> then finished 'make' under '~/milkymist/autotest-m1.git/src$' then shows up 'CRC32 (boot.bin): ....
<wpwrak> very strange. that should just build libmath. there's nothing for it to do in tools/
<wpwrak> aah !!!
<wpwrak> now i get it :)
<aw_> you get what?
<wpwrak> i understood what you're doing. i was missing the last step
<wpwrak> it's kinda weird that autotest-m1 would go over to milkymist.git and build things there. that confused me
<aw_> so can i say that a 'newer' (boot.bin) is built already and now every time that after I modify files under '/autotest-m1.git/src/' folder then i just type 'make' ?
<wpwrak> okay, seems that you're good now. now you try to run the critter :)
<wpwrak> yes, i think that should work
<aw_> hehe...critter... okay..thanks.. now go back to see this file : https://github.com/milkymist/milkymist/blob/master/software/libhal/vin.c#L128
<aw_> phew ~ i need to see each of them, but seems lekernel told me those three:
<aw_> static const char vreg_addr[] = {
<aw_> 0x1d, 0xc3, 0xc4
<aw_> <lekernel> };
<aw_> hehe :)
<wpwrak> that would be crystal and multiplexer
<wpwrak> lovely. there's no complete data sheet
<wpwrak> the 7181B still had one
<aw_> second... in another place. :)
<wpwrak> bah. why simple if it can be awkward ? ;-)
<wpwrak> thanks ! that looks better. actually there's too much information now ;-))
<aw_> :)
<wpwrak> i think you want to change the 0x05 in vin.c to 0x06 (variable vreg_dat)
<wpwrak> then rebuild libhal, then rebuild the autotest
<wpwrak> i think i should teach dsv a few more tricks ... :)
<aw_> will back to see 0x06 ...
<aw_> firstly i need to run that new boot.bin to see if it can detect 0x19 ID(7181C) :-)
<wpwrak> oh, instead of changing vin.c you may also be able to get the video signal simply by plugging the camera into the middle connector
<aw_> the new boot.bin can't show menu items that i can pick. strange ! http://dpaste.com/664775/
<aw_> ha...okay
<aw_> let's see if xiangfu did something in this repository ?
<wpwrak> maybe you now have a SOC incompatibility
<aw_> i have to compile MMDIR/tools before run flterm. phew ~
<aw_> what does this commit mean ?
<wpwrak> (commit) perhaps some minor dependency. nothing really important
<aw_> aha ... you did them for me. ?
<wpwrak> yuo need the new soc, the new bios, and then load boot.bin via flterm
<wpwrak> yes. these are the files i currently use
<aw_> just copy your files into my current folder.
<aw_> so your boot.bin is for adv7181c and should detect id: 0x19 ?
<wpwrak> m1nor soc.fpg && m1nor bios.bin && flterm --port /dev/ttyUSB0 --kernel boot.bin
<wpwrak> it should accept the 0x19
<aw_> wow..wow...super script shows up now ...
<wpwrak> it doesn't set the mux right, though. but let's try my middle connector hypothesis first
<wpwrak> m1nor is all about keeping things simple ;-)
<aw_> let's see where your m1nor is .
<aw_> good i found it
<wpwrak> you're quicker than me :)
<wpwrak> yup, that's the one
<wpwrak> since yuo're getting the latest version, you can abbreviate the above command sequence to
<wpwrak> m1nor soc.fpg bios.bin && flterm --port /dev/ttyUSB0 --kernel boot.bin
<wpwrak> when things are running, connect the camera to the middle connector, then do the VGA test (d), then the video input test (h)
<wpwrak> and with a little luck, you'll see an image :)
<aw_> block 67 unlocked
<aw_> erasing block 67: 0
<aw_> addr: 0x00872462
<aw_> verify skipped
<aw_> Flashed soc.fpg at offset 0x6e0000 using /home/adam/.qi/milkymist/latest/fjmem.bit
<aw_> Flashed bios.bin at offset 0x860000
<aw_> [FLTERM] Starting...
<aw_> after above msg, i pressed middle btn but there's no items I can choose. :(
<wpwrak> you mean the bios doesn't start ?
<aw_> yes... it must show somethings log out ...
<aw_> or maybe I use the old method to load your boot.bin
<wpwrak> what's "the old method" ?
<aw_> just ' flterm --port /dev/ttyUSB0 --kernel boot.bin' but after power-cycle
<wpwrak> let's go step by step. after you press the middle button, does the BIOS print anything on the serial console ? "libHPDMC SDRAM initialization runtime" or such ?
<wpwrak> power cycle is always a good idea :)
<wpwrak> and yes, flterm ... is still how you'd load
<wpwrak> the m1nor was just for updating the NOR. you don't need to do this each time
<aw_> no show up "libHP....." just blank ...
<wpwrak> *hmm*
<wpwrak> oh wait .. there's somethign wrong with soc.fpg
<aw_> :)
<wpwrak> updating ...
<wpwrak> now it should he okay. sorry about that. md5sum soc.fpg: 04a486a928d4f737763521ddd64203f3 soc.fpg
kristianpaul joined #milkymist
mumptai joined #milkymist
<aw_> GREAT !!! we DID.
<aw_> I2C pass. and video captured !!!
<wpwrak> congratulatinos ! :)
<aw_> in middle connector (BLUE)
<wpwrak> how's the image quality ?
<wolfspraul> phew, great
<aw_> hehe.... so far i think it's good. you know the image is enlarged. :-)
<wolfspraul> I need to email rafa about the ben for miri, but I think it's still on
<wpwrak> using the current code, composite will simply be on the middle connector
<wpwrak> (can be changed, of course)
<wolfspraul> aw_: wpwrak : what should we send to Werner?
<wolfspraul> aw_: please include one retail new Ben NanoNote
<aw_> yeah...just change register of multiplexer
<wolfspraul> then one of the two reworked boards
<wolfspraul> then what?
<wolfspraul> camera? power supply? any accessories?
<wolfspraul> case?
<wpwrak> NO POWER SUPPLY !!
<wolfspraul> ah :-)
<aw_> he... wpwrak you're saying you don't have POWER supply or don't want it. ;-)
<wolfspraul> he doesn't want it
<wpwrak> if you really really want me to have one, you may send it in separate mail. just the power supply, nothing else. using air mail, not a courier
<wolfspraul> let's find out what you want
<wolfspraul> camera?
<wolfspraul> accessories?
<wolfspraul> parts?
<aw_> wolfspraul, i just rework one board only. surely we ship this one first then I back to rework another. :-)
<wpwrak> aw_: in argentina, they often don't let things into the country that connect to mains and dno't have the argentine certification
<wpwrak> aw_: and when they find such a thing, they block the entire shipment. so you can't just remove the power supply and get the rest. very messy.
<wpwrak> aw_: of course, with a sufficient bribe, also this can be solved ...
<wpwrak> aw_: may be better to rework #2 first. if you run into problems, you'll have one to compare to
<wolfspraul> wpwrak: let's make a quick list
<wolfspraul> nothing else?
<wolfspraul> spare parts?
<wolfspraul> camera?
<wolfspraul> anything?
<wpwrak> wolfspraul: i have a camera. case parts would be nice. IR remote, too (i don't have that one yet)
<aw_> parts: AP2142ASG * 2pcs, APX803-40SAG * 2pcs, few 100uF capacitors, 7181C * 1 or 2pcs ?
<wolfspraul> cool
<wolfspraul> 2 IR remote
<wolfspraul> case parts, we still had some old violet color
<wolfspraul> and the new light-blue (with logo)
<wpwrak> if you don't mind parting with a light-blue one, that would be better. that way, i can see how the colors look (e.g., when trying leds)
<wpwrak> if you're short on them, purple will do
<wolfspraul> oh no
<wolfspraul> alright, so 1 light-blue case
<wolfspraul> what else?
<wolfspraul> parts?
<wpwrak> aw_: (parts) 2 APX803-40SAG isthe most important. AP2142ASG can't hurt. i have 100 uF caps. and i'm too chicken to try to replace the 7181C anyway, so i'm not sure this one will be useful ;-)
<wpwrak> maybe a rubber keyboard, for completeness
<aw_> wpwrak, for 7181C, it's okay for 1pcs. maybe later you'd like your previous one built with C version. :-)
<wolfspraul> I doubt Werner will risk that
<aw_> he
<wolfspraul> I'm not against including one at all, of course
Martoni joined #milkymist
<wolfspraul> even if the chance is only 10%
<wolfspraul> but maybe it's more like 0% :-)
<wolfspraul> it's also good to be able to compare the two
<wpwrak> yeah, i'd only think of making such a change if we have an emergency with the C and my pre-rc4 board suffers some fatal accident
<aw_> the AP2142ASG, since I saw some emails about 4 usb channels. not sure if we will use. so ship 2 pcs to you, then I still have two.
<wolfspraul> I think no need now for the adv7181c
<aw_> i bought 5 sets of parts though.
<wpwrak> thinking of it .. if you have space power/ether/video-on sidewalls, 2-3 of them would be nice to have
<wpwrak> that way, i could cut holes for JTAG ... and close the box :)
<wolfspraul> aw_: how many spares did roh send you?
<wpwrak> or maybe i should just hack off a bit of cardboard. thinking of it, that may actually be substantially more efficient :)
<wolfspraul> no wait, roh sent us spares
<wolfspraul> I just don't know how many exactly, so this may be a very good opportunity to get some actually used
<aw_> i have three full sets of cases(matched) available. and now two rc3 boards available to assemble. So a light-blue case is okay.
<aw_> there's two cases with wrong 'M' log. if you don't mind I ship that one to you. so I can still reserve those three full sets of cases.
<wpwrak> sure, no problem
<roh> wolfspraul: :) holler if you need more cases
<wpwrak> aw_: btw, here's a flickernoise to go with the rest: http://downloads.qi-hardware.com/people/werner/tmp/adv7181c/flickernoise.fbi
<aw_> wpwrak, aha..tks.
<wpwrak> you;ll need that for the new soc. the older ones will have incompatibilities with uart and/or usb
<wpwrak> when the smoke settles a bit, we should have a great upgrade day. so that everyone gets synchronized again :)
<wolfspraul> aw_: how about *spare* parts?
<wolfspraul> I think roh included some extra parts
<wolfspraul> do you have any?
<wolfspraul> roh: do you remember how many spares you sent?
<roh> not sure if there were acryllic spares
lekernel_ joined #milkymist
<roh> i know i had spare buttons/shields
<wolfspraul> ah ok
<aw_> wolfspraul, second... needs to count them again from my site.
<wolfspraul> aw_: we mean individual parts, for example the sides
<wolfspraul> but it seems no such thing exists...
<aw_> since most of them are assembled already.
<wolfspraul> yes, so either you have *extra* parts somewhere, or not
<wolfspraul> but it seems no
<aw_> moments...i have to clean files firstly
<roh> i could laser some sidewalls for the video/eth side with another hole for the jtag
<aw_> no. i guess with reverse/wrong side cases, i can match hopefully if Werner needs 2pcs.
<roh> wpwrak: which color is your case?
<wpwrak> roh: the one i have now is purple
<wpwrak> but i guess the easiest approach is to use a bit of cardboard and a sharp knife. don't have to be pretty anyway
<aw_> wpwrak, type 'm1nor soc.fpg bios.bin flickernoise.fbi && flterm --port /dev/ttyUSB0 --kernel boot.bin' or 'm1nor soc.fpg && m1nor bios.bin && m1nor flickernoise.fbi && flterm --port /dev/ttyUSB0 --kernel boot.bin' ?
<wpwrak> now, you just need m1nor flickernoise.fbi
<wpwrak> you already have all the rest
<wpwrak> for a new machine, m1nor soc.fpg bios.bin flickernoise.fbi
<wpwrak> and then flterm
<aw_> i see. i mean I need to use '&&' to link them. right ?
<aw_> aha...tks.
<wpwrak> you don't need the &&. i only used that in the first example because i didn't know if you already had an older version of m1nor, which would accept only one file at a time. the current version accepts multiple files, so it's all in one command
<aw_> okay
<aw_> good the rendering run well with video source (middle connector) :-) but with your new flickernoise.fbi my usb mouser doesn't work.
<aw_> I count 'extra' cases part now ...
<wpwrak> (mouse) urk :-(
<wpwrak> if you go to the BIOS, does it report anything about the mouse ?
<wpwrak> maybe stop booting with Esc, then connect the mouse and watch the serial console for USB debug output
Martoni joined #milkymist
azonenberg joined #milkymist
<lekernel_> morning
<scrts> hi
<wolfspraul> good morning!
<wpwrak> lekernel_: good news: the new codec seems to work. just needs different multiplexer settings
<wpwrak> aw_: mouser, n.: a cat proficient at mousing :-)
<roh> wpwrak: i could laser you a new sidewall in purple. i still have some sheets of that color
<roh> wpwrak: just no clue how to get it to you afterwards
<wpwrak> yeah, shipping overhead (also including customs processing on my end) probably vastly exceeds the actual work
<roh> wpwrak: know some laser shops around? ;) i could also send you a file *g*
<wpwrak> duh. find shop. send and explain file. go there to pick things up. that's as much overhead as global shipping :)
<lekernel_> cool :)
<lekernel_> btw, it seems that codec might support a "raw ADC" mode :)
<wpwrak> naw, i'll try the cardboard plus knife approach :)
<wpwrak> oh, and i could make it cardboard plus mill :) that sounds like even more fun
<roh> wpwrak: you could just mill it
<roh> some fr4 also should look geeky
<wpwrak> yeah. just checked the size and it would fit. most M1 case parts are too large for my mill, but the short sidewalls are okay
<roh> oh. its that small?
<wpwrak> pretty small, yes: only 10 x 15 cm work area
<aw_> (acrylic cases) there's five full sets just after matched rest of them. One with reverse 'M' log, the other I think the surface of acrylic is not good. so I keep remaining 3 sets.
<aw_> how do you think? two sets or just one set?
<wpwrak> lekernel_: (raw adc) so we can use M1 to control the sensors in our secret nuclear research facilities ?
<wpwrak> aw_: one set will be okay. i'll just do the cardboard approach. that's easier ;)
<wpwrak> roh: hmm, my uncoated FR4 boards are a little bit too short
<wpwrak> roh: i have a ton of aluminium sheets, though. but then, that may be risky :)
<roh> why?
<roh> mill too weak?
<Fallenou> 16:07 < lekernel> I'm setting up http://milkymist.org/blog/ - who wants an account? < I want one :)
nightlybuild joined #milkymist
<lekernel_> hmm, what is the SOY pin?
<lekernel_> see fig. 30 p. 85 of the 7181C manual
<wpwrak> roh: the mill is weak, yes. but it can do aluminium, very slowly. but it's be worried to have so much bare metal around. not sure if there isn't anything on the sides of the M1 pcb that's not supposed to make contact
<wpwrak> lekernel_: i think the technical term may be "a surprise" ? :)
<aw_> wpwrak, with yours, my usb mouse. http://dpaste.com/664826/
<aw_> but well at least it works well these 2 days without your flickernoise.fbi :-)
<roh> wpwrak: well.. if you have any advice on shipping services from germany... i think simply for finding out how well it works we could send a small letter sized acryllic part *g*
<lekernel_> seems to be useful only in power save mode
<wpwrak> hmm, that's an unhappy mouse indeed. darn. what kind of mouse is it ?
<wpwrak> (2 days) so you bought it recently ?
<roh> wpwrak: hm. dhl says 'brief international' should work
<wpwrak> roh: the thing is that mail shipments often get held up at customs. and that's basically half a day wasted.
<roh> ah. so you need to go there in person for every letter?
<wpwrak> roh: fedex and such pass as long as you avoid the traps, and you just pay customs fees and such on delivery
<aw_> wpwrak, no. the mouse I used to test all rc3 boards. i have run this mouse well two days after I added usb switch AP2142ASG. It's FUJITSU Model : MP117-P
<aw_> wpwrak, but after your flickernoise.fbi then doesn't work. :)
<wpwrak> not for letters. but parcels have a high probability. and they x-ray things, so they see if the content of a letter is really paper or something more interesting.
<wpwrak> (mouse) ah, i see. does unplugging and re-plugging help ? some mice need a few tries before they come to life
<wpwrak> lekernel_: (soy) not sure if it's just for power-saving. seems that this is a new feature in the C and the B didn't even support sync-on-green (never heard of sync-on-luma)
<lekernel_> sync on luma is what S-Video and YPbPr do
<wpwrak> ah, i see
<lekernel_> shall we connect this SOY pin? it's just one capacitor ...
<lekernel_> we can just DNP it if we have problems ...
<wpwrak> i know the old component video cables, before vga. they had a BNC for red, green, blue, and at least one sync if not two
<wpwrak> yes, i think it's a good idea to connect it
<lekernel_> from my understanding it is not needed though
<lekernel_> as aw_'s test has shown, the chip is able to acquire sync without it
<lekernel_> CVBS sync is the same sync as s-video and ypbpr
<wpwrak> maybe only with somewhat peculiar equipment
<wpwrak> aw_: if that mouse doesn't work, do you have another mouse that does ?
<aw_> wpwrak, I'll test other three models on hands ... second ...
<wpwrak> ah, you have a ton of them :) very good. some ought to work
wolfspraul joined #milkymist
r33p joined #milkymist
<aw_> wpwrak, four mouses are tested. :-)
<aw_> 1. Fujitsu MP117-P, never work.
<aw_> 2. ASUS M-U005, can plug/replug and work well
<aw_> 3. msi SM02, work only power-cycle but cant be detected when replug
<aw_> 4. Logitech M-UAS144, can plug /replug and work well.
<aw_> hehe
<aw_> i think i won't cross my hands on them now until next pre-rc4 rework is done. :)
<wolfspraul> lekernel_: what do you think about 4 USB connectors?
<lekernel_> I don't really know where they would fit
<wolfspraul> and putting that aside?
<lekernel_> well, if you want. but 3 are enough imo...
<wolfspraul> I don't feel strongly about it
<wolfspraul> meaning that we don't even fully use the 2 yet, our usb support can still improve a lot it sounds
<wolfspraul> it's just that werner brought it up so I try to investigate a little
<wolfspraul> for example you could have said "oh no, horrible idea, will cause lots of trouble in the soc"
<wolfspraul> but you didn't :-)
<lekernel_> the 3 port scenario I have is keyboard + mouse + LV3
<lekernel_> no, adding more ports should be relatively painless with the current design
<lekernel_> unless more unexpected bugs show up
<wolfspraul> well there are still logs of potential fixes/improvements I'm sure, throughout the stack
<lekernel_> there's just one multiplexer, and the USB core services the ports one by one
<wolfspraul> just look at Adam's mouse list above :-)
<wolfspraul> will 3 fit?
<lekernel_> maybe, if we cramp them a little
wolfspraul joined #milkymist
Gurty joined #milkymist
wolfspraul joined #milkymist
errordeveloper joined #milkymist
wolfspraul joined #milkymist
<lekernel_> can we say "version" instead of "rc"?
wolfspraul joined #milkymist
wolfspraul joined #milkymist
<GitHub111> [milkymist] sbourdeauducq pushed 1 new commit to master: http://git.io/OFTuJA
<GitHub111> [milkymist/master] bios: make the LIBS as .PHONY - Xiangfu Liu
<wpwrak> i think the main question about adding USB ports would be whether the power supply can keep up. at least the path through M1 shuold be able to handle N x 500 mA plus a bit of tolerance
<wpwrak> regarding uses, i'm sure they will be found. you can never have too many USB ports ;-)
<wolfspraul> oh good point, the current power supply we include is only rated 2A, but we can source a bigger one. then would need to check the circuit on the board.
elldekaa joined #milkymist
<lekernel_> http://sourceforge.net/projects/opendf/develop (...and for the 1st time, svn didn't crash on a > 1GB checkout)
<wolfspraul> seems we are in class
<wolfspraul> can you summarize what these links are about?
<lekernel_> building hardware accelerators more efficiently
<wpwrak> for 4 ports, you may want to consider one of those stacked USB connectors. like this: http://search.digikey.com/us/en/products/AU-Y1008-R/AE9926-ND/821680
<wpwrak> or aybe this one. looks tidier and it's "USB 2.0", so more future-proof: http://search.digikey.com/us/en/products/690-008-621-013/151-1085-ND/806184
<wpwrak> s/aybe/maybe/
<wpwrak> naw, the bot here doesn't do it yet :)
<wolfspraul> ok those are pairs of 2, so we can only do 2 or 4
<wolfspraul> with the current vertical ones we could do 3
<wpwrak> you can also find monsters with 2 x USB + RJ45 if you want :)
<wpwrak> but i don't trust those. tall = big lever
<wolfspraul> lekernel_: ok so it's about the "CAL Actor Language"? http://en.wikipedia.org/wiki/CAL_Actor_Language
<wolfspraul> how does this relate to Milkymist?
<lekernel_> yes
<lekernel_> well, dataflow languages like CAL (there are others, and I can also brew my own) can be used to design things like graphics pipelines more efficiently
<lekernel_> the problem I see with CAL is there is no support for things like automatic generation of DMA masters and their SoC interconnect
<wolfspraul> ok. do you plan on using CAL for the Milkymist SoC? do you want to encourage others to study/use CAL? for what features in Milkymist specifically do you think it could be suited well?
<lekernel> for the design of a more powerful and flexible graphics pipeline
<lekernel> like, right now, switching to 5:6:5 to 10:10:10 means a lot of manual coding
<lekernel> from 5:6:5
<lekernel> ideally, with a high level synthesis language, we could easily parametrize such things
<lekernel> automatic memory interfaces also look interesting
<lekernel> right now there's a lot of copy and paste and "manual compilation"
<lekernel> this is daunting, inefficient, and not very flexible... with high level synthesis, it'd be much easier to explore the design space (e.g. enable/disable prefetching, caches, etc.)
<lekernel> so... yes, I plan to rewrite the TMU using dataflow (not necessarily CAL)
<lekernel> I'm just looking at what's already existing
<wolfspraul> ah ok, nice
<wolfspraul> that's very clear now - thanks!
elldekaa joined #milkymist
<wpwrak> (manual coding) no macros in verilog ?
<lekernel> they're not very powerful
<wpwrak> mmh, pity
<wpwrak> such layered languages are often more trouble that they're worth. they have to be really really good, or you'll just end up having to work on/debug your actual code, plus the gobbledygook the precompiler has generated
<wpwrak> hmm. thinking of it, we have no word on the camera image quality yet. what exactly is the ADV7181C supposed to improve with respect to the B ? anything specific that should be observable ?
<lekernel> better colors
aeris- joined #milkymist
aeris- left #milkymist
<mwalle> mh, the ft2232 samples with 120mhz and 10 bit oversampling giving us a max baudtick of 12mhz
<mwalle> unfortunately the error above 4mbps is rather high with our 20mhz (4bit oversampling) and that 12mhz
<wpwrak> lekernel: "better" in what sense ? dynamic range ? pixel-to-pixel crosstalk ? linearity ? ...
<lekernel> what can be expected from the effects of a better antialiasing filter on a CVBS signal
<wpwrak> hmm. so that would mean that signals with HF contamination will be better but those what stay within the design bandwidth will be unaffected ?
mumptai joined #milkymist
<wpwrak> very nice. without MIDI traffic, the "tunnel" patch renders at 24 +/- 0.03 FPS. if i hammer traditional MIDI at 1000 control changes per second, the frame rate drops to 15.44 +/- 0.12 FPS.
<wpwrak> now, let's make this faster ...
<wpwrak> nice. 23.99 +/- 0.1 FPS
<wpwrak> performance is good. now let's see about correctness ...
<wpwrak> hmm. something ain't quite right ... "optimized" midi seems to trigger false mouse action. not the improvement i was looking for. so where did i go astray ....
<wpwrak> seems this was just my rf mouse acting up at the point of losing battery power. ah well.
<kristianpaul> roh: send me the file :-)
<roh> kristianpaul: will do after i made one
<kristianpaul> lol i tought you alredy did it :)
<roh> nah. wasted the afternoon making new screw-locks for the fusebox
<roh> the box is as big as 2 wardrobes and has plastic thingies which keep the frontpanels in.. 4 per panel, i think 10 panels in total
<roh> there were only 2 on average per panel left in working order, the rest broke since 1984
<roh> and i couldnt find the manuf. so i used calipers and openscad and printed new ones. replicator(tm) for real
<roh> wpwrak: check if the messages contain a 'empty bat' packet
<roh> most devices send such prewarns... maybe your stack just misinterpreted that
juliusb joined #milkymist
<wpwrak> oh. that would be an interesting possibility. i'll have a look the next time this happens. thanks !
<wpwrak> lekernel: btw, did you get a reaction yet from xilinx regarding that xdl comma bug ?
errordeveloper joined #milkymist
<wpwrak> just machined a few more buttons. now i'm ready to receive the pre-rc4 :)
nightlybuild joined #milkymist
<kristianpaul> dynamical code loading in rtems GREAT !!
<kristianpaul> hum but suppoty got lm32..
<kristianpaul> s/suppoty/support
<kristianpaul> s/got/for
<wpwrak> dynamic code loading ?
<kristianpaul> yup
<wpwrak> ah :) that should be as easy as if (read(fd, buffer, sizeof(buffer)) > 0) ((void (*)(void)) buffer)(); no ? needs -fPIC, of course