<aw_>
lekernel, what's the mark on your WM9707SCFT/V chip? is it "WM9707S"?
<kristianpaul>
Vj meeting was canceled and i lost 2 hrs finding the place today .. :(
<aw_>
kristianpaul, could you scope your 24.576MHz (Y1) easily? It should be easily use your scope via 'auto set' button. :-)
<wolfspraul>
aw_: why should he scope Y1? any bug we are hunting?
<wolfspraul>
kristianpaul: too bad :-) that happens, keep your spirits high
<aw_>
wolfspraul kristianpaul , no big bugs found/hunt, just want someone can help me know what's amplitude it should? since i replaced mine to wm9707, and no xtal pulse though.
<aw_>
no problems on must help me. I'd just want to someone's condition though.
<wolfspraul>
aw_: kristianpaul is traveling and does not have access to his scope for at least another day or two.
<aw_>
wolfspraul, um..okay.
<aw_>
lekernel, hi
<aw_>
lekernel, i followed your wm9707 replacement h/w patches, keep external capacitors except added 10uF on pin32, dnp 1M on crystal. this should work but mine is not.
<aw_>
lekernel, just want to confirm/compare your board now. :-)
<aw_>
my crystal doesn't oscillate. and check all pins with good powers and grounds.
<terpstra_>
does anyone know of a free gigabit etheret MAC that supports a streaming mode on wishbone?
<terpstra_>
(by streaming i mean !DMA)
<lekernel>
aw_: did you boot the board?
<lekernel>
when the board is unbooted the ac97 chip is in reset. not sure the oscillator stays enabled then.
<xiangfu>
<xiangfu> a patch for change the video-in size. but I guess the line:58, 68, 73 in this patch is not good. please give me some tips on MTKLIBÂ Â :)
<xiangfu>
ping
<aw_>
lekernel, i didn't boot board. I am pretty sure that Y1 doesn't need to stay under booted stage, I compared my other boards with unbooted. it oscillates.
<xiangfu_>
<xiangfu> <xiangfu> a patch for change the video-in size. but I guess the line:58, 68, 73 in this patch is not good. please give me some tips on MTKLIBÂ Â :)
<xiangfu_>
(seems something wrong with my network)
<aw_>
lekernel, did i maybe miss somethings or parts wrong? a hint would be good though.
<aw_>
lekernel, lm4550b can still oscillate under AC97_RESET is low while unbooted. not sure if i still missed what.
<aw_>
good, now i can see my ac97 signals but oscillating waveform is quite not stable so that my right line out randomly audio on randomly off, but left line out always on.
<lekernel>
aw_: it is not specified whether the oscillator should be on while the chip is on reset. national semiconductor and wolfson can do whatever they want there and possibly different things.
<aw_>
interesting..
<aw_>
lekernel, yup, i think so.
<aw_>
lekernel,  probably i need replace other value for C28/C29.
<lekernel>
yeah, maybe
<lekernel>
also, maybe it is your probing which makes the oscillator unstable? is it still unstable with the probe disconnected?
<lekernel>
you're using a x10 probe, right?
<aw_>
yes, i am using x10 probe, now it's very stable no matter I touch Y1's pad or not.
<aw_>
i did nothing though. now it's stable, but my LINE_R is good, LINE_L is sometime ON /OFF. i can see signals on C19's pad differently.
<aw_>
also randomly have noise appeared on both channel. not stable though.
<aw_>
keep monitoring.
<aw_>
but there's an fact that 'white noise' is less than lm4550b. this is definitely i confirmed here. this is good. :-)
<aw_>
the white noise stays roughly 500mV on lm4450b.
<aw_>
wm9707 is lower than 200mV. thus SNR ratio actually works better than lm4550b. :-)
<lekernel>
200mV is still a lot
<lekernel>
I measured a lot less than that
<aw_>
actually lower than 100mV here. my work now is not good on soldering  i think. now it comes with Intermittencely noise.
<aw_>
does your wm9707 have 'pop' sound between 'muted' and 'unmuted'?
<lekernel>
no
<lekernel>
it doesn't make any noise or pop except one pop when you turn the power off
<aw_>
i see, so my work was just still have somewhere's wrong. or parts by my heated.
<aw_>
so you used 10uF on pin32, right?
<lekernel>
yes
<lekernel>
10uF ceramic
<aw_>
good, okay
<aw_>
me too.
<lekernel>
btw how is the rest going?
<lekernel>
this audio codec is the last thing you're testing?
<lekernel>
before rc3?
<aw_>
no, still have zener/fuse & video littlefuse waiting for final test.
<aw_>
once they are all done, we can go for rc3.
<wolfspraul>
roh: I'm a bit worried about the buttons and tolerances on the inside
<wolfspraul>
I've had several cases where the pressure onto the electrical switches is so high that they are stuck (always pressed down)
<wolfspraul>
this happens particularly after putting the top cover on and tightening the screws
<wolfspraul>
not sure what to do...
<wolfspraul>
maybe we should move the switches into the pcb a few mil?
<wolfspraul>
or we change the design of the 3 button pieces?
<wolfspraul>
it's really only the thickness of that one slightly larger circle that is in between the switch and the acrylic side element
<wolfspraul>
I'm worried that the design is too unforgiving on the inside, so some percentage of cases (let's say 10-20%) will exhibit the 'buttons stuck' problem
<aw_>
wolfspraul, although i didn't know how these buttons's problem/situations. do you think that we can just use another 'long' tag push button then from the case surface we can easily push the long 'tag'?
<aw_>
wolfspraul, can you imagine my 'long tag' push button to solve this, suffer from 'button stuck'?
<aw_>
the tact switch with long length tag which goes though the thickness of case?
<wolfspraul>
hmm
<wolfspraul>
aw_: any change is risky, because what we have now is not bad, and tested well
<wolfspraul>
also the current solution is nice because there is no glue between the electrical switch and the button
<aw_>
if M1 is i use only, i'll change all 3 tact switches to be like SIE's tact switch, it have long tag. although it's ugly from outside outlook view.
<aw_>
well.. forget about my idea. :-)
<lekernel>
roh: just wondering, how can we cut the current case design out of metal and how expensive would that be?
<kristianpaul>
aw_: hi, i'm traveling home today at night, so i hope tomorrow help you with you measurements
<aw_>
kristianpaul, hi thanks, no needs now, i can check my others though.
<kristianpaul>
sure?
<kristianpaul>
ok
<roh>
lekernel: how? much more expensive laser or plasma-torch. also waterjet is an option
<roh>
but it would be quite heavy
<roh>
and crazy expensive
<lekernel>
plasma torch is expensive?
<lekernel>
they have plasma torches at tacheles... just not mounted on CNCs ;-)
<roh>
lekernel: well.. doesnt help
<roh>
its very imprecise
<roh>
for stuff <1cm width you usually use a waterjet
<lekernel>
I know... but my point is it's not such an unattainable/expensive technology, is it?
<roh>
also.... none of the methods works without a lot of work after (remove brill etc)
<roh>
lekernel: i dont know exact prices, but afaik material price as well as manufacturing cost AND working time would atleast double. so we end up with >150E a case minimum
<lekernel>
how does apple cut their cases?
<roh>
which ones?
<lekernel>
macbook pro for example
<lekernel>
injection?
<roh>
some the cnc-mill.. in china. in a process which only is feasible if you recyle ALL the ground up aluminium
<roh>
also it only works if you have whole halls of cnc machines and do masses.
<roh>
its still expensive tho.
<roh>
i find that impressive.. dont get me wrong... apple are the first consumer-electronics-company who does such manufacturing methods. yet it doesnt work for smaller scales
<roh>
if you'd ask me what machine i want to get access to next: a machine to form plastic over molds. vacuum-deep-molding
<roh>
EDM sounds fancy.. but afaik only works on metal
<roh>
btw.. its the only machine which can do 'real rectangular corners'
<lekernel>
except for the x ray hazard it looks very nice
<roh>
inside-corners
<lekernel>
shouldn't even be super hard to DIY... probably easier than a laser cutter for metal
<roh>
EDM/EBM is also huge, expensive and does not work with all material
<lekernel>
and cheaper too
<lekernel>
yeah, but for cutting metal
<roh>
on the other side... metal corrodes.. so plastic gives a better finish for less money anyhow
<lekernel>
imo the price is only because certified vacuum components are expensive like hell
<roh>
for cutting: use waterjet on metal.
<lekernel>
but there are ways around that
<roh>
or depending on the thickness: NG-YAG or so.
<roh>
co2 laser is not good for metal at all
<lekernel>
imo the major problem I see with building such a machine is getting your ass x-rayed
<roh>
so.. there is no single manufacturing technique which is anywhere in the range of owning machines besides co2-lasers
<roh>
guess why we have one ;)
<lekernel>
if we can have a small one that can work with x-ray safe voltages (< 12kV or so), perfect
<roh>
edm isnt that mulipurpose how you think
<lekernel>
seem to me it's like your laser cutter but for metal :)
<lekernel>
which would already be very nice
<roh>
also one needs a vaccuum chamber
<lekernel>
yeah sure
<roh>
lekernel: the cheapest way to cnc metal is either laser, waterjet or plasmajet
<roh>
in that order.
<lekernel>
in the hackspace in paris we have some turbopumps laying around already. such a project would put them to good use.
<roh>
waterjet gives the nicest results, but laser and waterjet have a thickness-limit
<roh>
plasmajet can go through thicker stuff, but is less precise
<roh>
also all three machines need 'space'
<roh>
much more space
<lekernel>
we even got our hands on a ion pump (which works by trapping ionized gas molecules and spinning them in circles using magnetic+electric field... quite crazy stuff for ultra low vacuum)
<lekernel>
also, what about photoresist+chemical attack?
<roh>
on metal?
<lekernel>
yes
<roh>
guess how pcbs are made
<lekernel>
yeah. but what about a thick piece of metal?
<roh>
but you wont get great z-precision by 'continuing ecthing'
<lekernel>
yeah... they have this problems with semiconductors too. which they solved using special formulations of the etchants.
<roh>
i dont see any gain in there
<roh>
waterjet is fine and comparedably easy to handle. just a bit expensive in room and money (but less than the other methods)
<carlobar>
hi, im trying to compile the kernel for milkymist SoC, and i get this eror:Â Â Â Â arch/lm32/kernel/early_printk.c:43: error: implicit declaration of function out_be32, someone can help me?
<carlobar>
hi, i got the kernel on https://github.com/milkymist/linux-milkymist, but compiling i got the same error: arch/lm32/kernel/early_printk.c:43: error: implicit declaration of function out_be32. Maybe is something wrong with my linux configuration?
<mwalle>
lekernel: should i remove minimac1 from qemu?
<mwalle>
carlobar: i guess there is a missing include (which declares out_be32)
<mwalle>
carlobar: mh out_be32 isnt provided anymore for lm32 arch
<carlobar>
hi mwalle, and what can i do?
<mwalle>
try writew() instead
<mwalle>
erm writel
<carlobar>
ok, thank you
<larsc>
carlobar: #include <linux/io.h>
<mwalle>
lekernel: and could you change the microudp timeout loop to use the timer, too? this way it'll work in qemu too
<mwalle>
larsc: out_be32 is ppc specific
<larsc>
oh out_be32
<mwalle>
dunno the exact equivalent
<larsc>
iowrite32be
<larsc>
writel is litte-endian
<lekernel>
uhm, why did it work for me?
<mwalle>
lekernel:Â Â in qemu?
<lekernel>
mwalle: (remove minimac1 from qemu) yes, I think so
<larsc>
lekernel: CONFIG_EARLY_PRINTK=n
<lekernel>
no, compiling the linux kernel
<lekernel>
ah, maybe
<lekernel>
mwalle: (using timer) yes
<lekernel>
should do that
<lekernel>
counting cycles is just a quick hack
<lekernel>
minimac2 works neatly now... been using ftp quite intensively for the past 3 hours or so without bug
<lekernel>
there is still a reset problem of the PHY, but if you've not run into it at boot time ethernet is fairly stable
<lekernel>
btw it's clearly the PHY, pulsing its reset line when the problem occurs resolves it
<lekernel>
(without rebooting)
<lekernel>
and the symptom of it is just dysfunctional ethernet, no driver crash as before :-)
<mwalle>
lekernel: btw the ac97 'problem' only affects lineout?
<lekernel>
seems so, but tbh I have not measured
<mwalle>
i desoldered three ac97 codecs today.. maybe one of them is drop in compatible, ad1980, alc650, and stac9220
<mwalle>
mh the latter is a hd one
<carlobar>
with CONFIG_EARLY_PRINTK=n the error was solved, but now i got other: kernel/posix-cpu-timers.c:287: internal compiler error: in lm32_block_move_inline, at config/lm32/lm32.c:785... this is because of wrong configuration in timers?
<mwalle>
carlobar: whats your compiler version?
<lekernel>
mwalle: I can send you a wm9707 if you want
<carlobar>
mwalle: gcc version 4.4.1 (GCC)
<mwalle>
carlobar lekernel: i think the latest working version was some 4.5.x right?
<larsc>
4.5.x workes find (somthimes)
<larsc>
sometimes
<lekernel>
for c yes
<lekernel>
4.5.1 works
<lekernel>
c++ seems broken in all 4.5.* and works in the 4.4 lattice release
<mwalle>
lekernel: btw on the qemu ml there was some consens on first disable opengl by default, then make configure more intelligent in the way it links to the needed libs
<mwalle>
the disable by default patch wasnt merged, instead they are trying to figure out the real problem, but it seems everyone got stuck somewhere
<mwalle>
wasnt merged yet..
<carlobar>
i'll try to compile the kernel with the lattice toolchain.. i'll write about the results latter
<lekernel>
carlobar: fwiw i'm using the 4.5.1 rtems toolchain