<wolfspraul>
I guess we still have to update the schematics?
<wolfspraul>
since I need to fix my board somehow, do we have a placement drawing somewhere?
<aw_>
rc2 L19 we mounted with wrong bead with its DC resistor has 0.1 ohm resistor not as rc1 0.01 ohm resistor.
<aw_>
so current rc3 incoming parts already with correct type of bead with 0.01 ohm
<wolfspraul>
0.01 ohm same as 0 ohm? are we sure this is enough for the fix?
<aw_>
a resistor's value defined as 0hm, need to consider its tolerance, so for example, a 1% tolerance define as  0.01 ohm.
<aw_>
wolfspraul, no the answer is that i am not sure!
<aw_>
since sebasiten's rc2 board he had have that problem, but i don't, you may be no, i don't know. so what i want to say is a soldering as "short" is better than using a 1% resistor.
<wolfspraul>
why don't we just solder it short in rc3?
<aw_>
thus as i suggested we relayout it as "short" in rc4.
<aw_>
right
<aw_>
so i susggested to manually soldered all is as "short". :-)
<wolfspraul>
what's better? manually solder short 80 units, or 0 ohm resistor?
<aw_>
since it was a nice catch, but nnot just using 0 ohm. short 80 units. :-)
<wolfspraul>
ok fine by me
<wolfspraul>
aw_: do we have a placement drawing? where is L19?
<aw_>
becuase currently no on  knew rc1 has this problem potentially existing, so as a better idea that we directly manully solder it as short in rc3.
<aw_>
L19 is located under MIDI RX connector and at the left side of U6 silk screen.
<wolfspraul>
how did Werner upload this?
<wolfspraul>
and in his tmp folder?
<wolfspraul>
looks like a fairly useful thing to me, maybe we should upload into the wiki and link to it in appropriate places? unfortunately with Altium our process on these things is not so smooth... all needs to be done manually :-)
<aw_>
that one is genereated by his smart "prettygerbv" script under EDA tools project
<wolfspraul>
oh I see. it's created from gerber files?
<wolfspraul>
yes, I found L19, thanks!
<aw_>
no problem I'll have a rc3's pcb wiki page later, so i can link his images. :-)
<wolfspraul>
yes definitely
<aw_>
yes, created from gerber files.
<wolfspraul>
this one is very nice. only not searchable.
<aw_>
sure sure i'll create a rc3 pcb wiki page. :-)
<wolfspraul>
good idea to create this kind of thing from gerber files. I like it.
<wolfspraul>
at least that's a standard, so if things can be created out of that - good
<aw_>
then it's easily to find them with real pcb image the I scan them.
<wolfspraul>
aw_: so it should be fairly easy to remove L19 and short it, right?
<wolfspraul>
I will try one day :-)
<aw_>
yes, it's easy for me also I can let smt vendor to short it not me. :-)
<aw_>
btw, i'll still order a 1206 package with ohm +/- 1% resistor today.
<wolfspraul>
why? not sure it's needed...
<aw_>
no no, for me just samples only. :-)
<wolfspraul>
ok
<aw_>
so xiangfu's rc2 also have this problem?
<aw_>
wolfspraul, the black one of remoter, you'd order them if they have 100pcs?
<wolfspraul>
aw_: not yet
<wolfspraul>
aw_: yes, xiangfu also has the L19 problem
<wolfspraul>
xiangfu: so you can reproduce the camera-signal-loss bug on your rc2 board, right?
<xiangfu>
wolfspraul: yes. plug, then unplug the camera, the video-in gone.
<xiangfu>
I mean. re-plug the camera, the video-in will not working.
<wolfspraul>
ok great
<wolfspraul>
let's try the L19 medicine
<xiangfu>
ok
<wolfspraul>
you know where L19 is?
<wolfspraul>
remove and short it :-)
<xiangfu>
yes.
<kristianpaul>
aw: can i guess L19 is easy to remove with a solder iron?
<kristianpaul>
i think yes, but was not the same asumption when i was trying to do the same witn a  capacitor in a cell phone board..
<aw>
yes,
<wolfspraul>
kristianpaul: should be easy, yes
<aw>
but you probably need to soldering a big blob on L19's two terminal pads at the same time, then you can soldering(remove) out.
<wolfspraul>
but maybe you wait until xiangfu tells us what happened to him :-)
<wolfspraul>
have you seen the actual bug? loosing camera signal, need to reboot m1 to get it back?
<kristianpaul>
i realize i need twizzers..
<wolfspraul>
I'm pretty sure it's related to the power supply of the camera. I had this problem for months, but now I cannot reproduce it anymore. And I just switched to a new camera power supply and discarded the old one...
<kristianpaul>
yes that bug is nasty
<wolfspraul>
ah ok, so you've seen it
<kristianpaul>
i just used to it after a while..
<wolfspraul>
yes, for someone who really wants to use the camera, especially at a real party/event, that's the kidn of thing that can drive you crazy
<kristianpaul>
i tought was software really, never hw..
<wolfspraul>
it could be fixed in software, by implementing a watchdog and hard-resetting just the chip
<wolfspraul>
but that's why we have small runs, slowly ramping up the product, etc. right now it's easy to remove/short L19
<kristianpaul>
oh, interesting
<wolfspraul>
and on future boards of course it will be fixed right away
<wolfspraul>
so I don't think there is a need for a software watchdog
<kristianpaul>
indeed
<wolfspraul>
if we had thousands of boards and hard to reach users, of course we would do the software watchdog as well
<wolfspraul>
well, do you want to try in parallel with xiangfu ?
<wolfspraul>
actually we have very few confirmations of the fix so far, so it's a good thing if people who can reproduce the bug report that the fix indeed fixes their problem
<kristianpaul>
not know, may be tommorrow, reading some datasheets right now
<kristianpaul>
but sure i confirm the bug is there in my side too
<wolfspraul>
so far we only have analysis of the root cause, and Werner and Sebastien agree on the agnd/dgnd issue
<wolfspraul>
and Sebastien was able to reproduce the bug consistently, and shorting L19 fixed it
<wolfspraul>
if xiangfu and you can add two more confirmations of the fix - awesome
<wolfspraul>
me or Adam cannot currently reproduce the bug, so we also cannot verify a fix :-)
<kristianpaul>
i wish i could fix my ac97 chip as well ;)
<wolfspraul>
you mean the noise?
<kristianpaul>
ah, you mean neither you or adam have a mm1?
<kristianpaul>
yes
<wolfspraul>
is it hard to rework the chip to wolfson?
<wolfspraul>
no we have mm1, of course
<wolfspraul>
but I just wrote it above :-)
<kristianpaul>
:)
<wolfspraul>
I think the bug first of all needs a leaking power supply to show up.
<wolfspraul>
and as it happens, I just replaced my camera power supply a few days ago, and, of course, discarded the old one
<wolfspraul>
now I cannot reproduce the problem
<wolfspraul>
Adam is probably using a lab power supply, and he also cannot reproduce it
<kristianpaul>
(rework) well i need a solder statio and some exprimentation in other boards before try do it on my mm1 ;)
<wolfspraul>
but there is no need for many people to reproduce it, we are quite confident of the analysis and fix, and if xiangfu or you (who both can reproduce the bug), can verify the fix, then perfect, done.
<kristianpaul>
oh, i see (power supply)
<wolfspraul>
I forgot which modifications exactly we believe lead to less noice on rc3
<wolfspraul>
noise
<wolfspraul>
was it the wolfson codec?
<wolfspraul>
or some other changes?
<kristianpaul>
i think the new codec itself imply other changes..
<kristianpaul>
in any case i dont noticed noise when was at labsurlab, or more people complain about it..
<kristianpaul>
well i was using an iphone in the line-in
<kristianpaul>
but now i dont have an iphone to try,
<kristianpaul>
also in labsurlab the audio out was ampliflied for all the place, surelly that explain why noise was gone..
<wolfspraul>
ok
<wolfspraul>
I think you should try to fix L19 first, if xiangfu confirms it
<kristianpaul>
sure :0
<kristianpaul>
s/:0/:)
<wolfspraul>
that's easy and a small nasty bug, especially when you try to use m1+camera at a real event
<xiangfu>
wolfspraul: hi
<xiangfu>
after short the L19, I tried 30 times. everytime I re-plug the camera, the video-in works just fine.
<wolfspraul>
aha, perfect!
<wolfspraul>
xiangfu: thanks a lot for trying, and also we have another rc2 fixed ;-)
<xiangfu>
I also tried re-plug camera very fast, works fine.
<wolfspraul>
sure of course. it should be rock solid. we are making a professional product...
<wpwrak>
wolfspraul: needed a few tweaks and hard-coding of an offset between the drill file (excellon) and the real gerbers, though.
<wolfspraul>
I saw something, but it didn't register with me how cool it actually was :-)
<wolfspraul>
I like the idea of first trying to extract new perspectives into the design from standard file formats.
<wolfspraul>
wpwrak: you saw that xiangfu made another positive confirmation of the L19 fix? very good.
<wpwrak>
yeah. looks pretty much solved
<wolfspraul>
that makes it two people who went from being able to repro the bug to not having it anymore.
<wolfspraul>
and kristianpaul will probably/hopefully be the third, at some point
<wpwrak>
according to ADI's design guidelines, shorting L19 isn't ideal (the bridge between the ground planes should be underneath the video chip), but it's close enough
<wolfspraul>
we should start the rc3 errata already
<wolfspraul>
as long as it's just one thing I can remember it :-)
<wpwrak>
hehe :)
<lekernel>
aw, aren't you able to source 0 ohm "resistors" that are just bits of metal?
<lekernel>
that datasheet you pointed looks more like resistors to make current probes and such
<aw>
lekernel, yes, I've not found out a metal one. won't you want to use soldering "short" L19?
<lekernel>
that looks more work-intensive than just throwing a reel of 0 ohm resistors into the pick and place machine
<aw>
yeah
<lekernel>
but well... up to you
<aw>
smt factory can do this for me while producing brds.
<lekernel>
i'm planning to do quite a bit of publicity after this run is out, so hopefully they will sell fast
<lekernel>
which means, it's better if we can produce them fast (by just re-doing the run 3 design) as well
<aw>
with soldering.
<aw>
yeah...we all hope that
<lekernel>
aw, do you happen to know how to use a chip wire bonding machine?
<aw>
lekernel, i saw bonding machines with Wolfgang before, but how to use? I don't exactly know too much.
<aw>
my last time to see it with golden bonding machine while producing avt2 run1 with 0.7 mil diameter golden wire.
<lekernel>
people at a hackerspace in Paris scavenged one, but need help with using it
<aw>
seems that have two catogories on golden and aluminum wires, golden wire it uses an electric arc to heat a platform to heat golden wire.
<aw>
the aluminum i didn't see it carefully. but too bad that here bonding vendors din't allow us to take video on machines though.
<aw>
well...can't help you anything. :-)
<lekernel>
interesting, they have an ADV7181C as well
<carlobar>
hi, i have modified the HPDMC controller to support 16 bit memories. Now memory tests pass and bios is executed, but when i try to read the memory (executing mr), just the the 16 most significant bits are ok. The least significant bits printed are wrong and do not change after rewriting data. Can someone help me to solve that problem? thanks
<kristianpaul>
how are you rewriting data
<kristianpaul>
?
<carlobar>
with mw
<kristianpaul>
and from wich addres are you readin at first?
<kristianpaul>
sure, but, the exact command you used
<carlobar>
sdram is at 0x400000000, so i execute something like: mw 0x40000000 0xabadface
<carlobar>
yes, i got 0x53334558, that is S3EX in ascii..
<kristianpaul>
good
<kristianpaul>
so if you implement the bram core for example (is ti on the avnet milkymist port)
<kristianpaul>
can you repeathat mr and mw commands on it
<kristianpaul>
to be sure you issue is not related witht the HPDMC
<kristianpaul>
sorry, i'm not very related to this core yet to help you more
<kristianpaul>
ah, well for easy you could implement a general porpuse register in sysctl, you can confirm readin and writing is OK
<kristianpaul>
but nice you ported mm1 to this board !
<carlobar>
yes, but now i have to port linux :-D
<carlobar>
writings, readings on bram are ok
<kristianpaul>
good !
<carlobar>
that problem is only on hpdmc.. but memory test on sdram pass..
<kristianpaul>
lekernel: (pico) cute board, but indeed a bit pricy
<kristianpaul>
arghh, again that nasty cypress controller..
<kristianpaul>
a basic device mode support for the mm1 will be nice
<kristianpaul>
JFDI :-D
<wpwrak>
in iDiot mode: lekernel: (picocomputing) but it's cheaper than the M1 ! it has an FPGA, so it's the same ! ;-)
<kristianpaul>
lol
<lekernel>
wpwrak, the picocomputing thing is $399
<lekernel>
it's more expensive than the m1 :)
<wpwrak>
lekernel: isn't M1 USD 500 ?
<lekernel>
that'll be the package, the board alone (which we have now) is cheaper
<kristianpaul>
try to remenber how much paid for his m1 board
<wpwrak>
aah, i see :) bah, such a big board without a nice case. that's so /technical/. and where's the app store ? ;-)
<kristianpaul>
you mean patch library?
<kristianpaul>
so you dont need bother for apps, all work out of the boxes, and you can get cool patches from free ;-)
<kristianpaul>
also there are special edition patches, that you can easilly buy
<wpwrak>
kristianpaul: an app store ! where i can buy apps blessed by Steve Holy Jobs :)
<kristianpaul>
Sr, the only app you run in milkymist is the VJing stuff called FLickernoise,
<wpwrak>
kristianpaul: you techies talk funny. "patches". that's why this stuff sucks !
<kristianpaul>
how i should call it then?
<wpwrak>
kristianpaul: 1 app ?!? we have a hundred millions in the app store !! aah, go away, geeks !
<kristianpaul>
wpwrak: what if i tell you dont need to be a VJ to use MM1, you can just turn in on, press a button and your friends will get amazed with the coolest effects
<kristianpaul>
if you want further, you can be social and use twitter to display messages on the go
<kristianpaul>
and thats not all, from you iphone you can control the performance too, is as easy as always :-)
<wpwrak>
hah. the iPhone is in control ! so you morlocks did at least something right. keep on trying. maybe in 10-20 years, you'll have something that is worth our money. until then, we shall shower you with disdain and nonsensical feature sugg... no, demands !
<wpwrak>
heh, a bit more exercise and i could become a slashdot troll ;-)
<kristianpaul>
jeje ;-)
<lekernel>
wpwrak, the sad thing is they probably buy iphones
<wpwrak>
lekernel: it probably feels like a basic necessity to them. like wearing clothes. they would feel naked and shunned by their peers if they didn't have an iSomething too.
<kristianpaul>
wear is very correct, and iphone an apple product have nice design, so many people surelly just like wear/show it :-)
<kristianpaul>
like all those geeks wearing t-shirts with fork bombs written in the back, or that funny penguino :-)
<GitHub104>
[milkymist] sbourdeauducq pushed 1 new commit to master: http://bit.ly/jTvmCe
<GitHub104>
[milkymist/master] rc5: adapt timing to the t003 remote - Sebastien Bourdeauducq
<carlobar>
hi, problem with HPDMC was solved.. it was an error in memory addressing
<lekernel>
well, given the ZPU core I tried last year was some 10-20x slower than that, Alvie seems to have done a good job
<wpwrak>
fractional cycles ? interesting ;) addsp must do some interesting magic
<wpwrak>
and "store" is marginally slower than 2 cycles
<mwalle>
lekernel: instead of patching the lm32 interrupt controller, we could add our own interrupt core and hook it up in the cpu interrupt line, thats imho the cleanest solution
<lekernel>
what cpu interrupt line? the lm32 has 32
<mwalle>
all 32 are ored to one, iirc
<kristianpaul>
+1 to the own interrupt core
<mwalle>
so we basically patch out the lm32 interrupt controller
<lekernel>
so 1) remove most of the LM32 interrupt logic and turn it into a single line IRQ input 2) implement an off-core interrupt controller?
<mwalle>
just keep IE
<mwalle>
yes
<lekernel>
sounds ok, as long as the extra bus cycles involved do not impact performance
<mwalle>
we could add some vector logic, so we wont have to walk over the IP register
<mwalle>
how many cycles does a csr access need?
<lekernel>
at least 3
<lekernel>
what is the advantage of an external interrupt controller over making the LM32 interrupt lines level-sensitive and IP read-only?
<kristianpaul>
run linux? :-)
<kristianpaul>
ah sorry, miss read
<mwalle>
easier to modify, eg xilinx has some nice set/clear bit pseudo registers for IE, so you wont have to RMW
<mwalle>
and i hoped that it would be easier to patch, but i think this isnt the case, just looking at the lm32_interrupt.v
<mwalle>
s/easier/cleaner/
<lekernel>
you can make the register that assert the IRQ in each core clear the IRQ bit on write, so you won't have to RMW either
<mwalle>
youre right, still thinking in the 'old' per interrupt IE bits terms
<mwalle>
cool devices trees are basically working
<GitHub0>
[llvm-lm32] jpbonn pushed 70 new commits to master: http://bit.ly/lDpsa7
<GitHub0>
[llvm-lm32/master] SI, DI, BP, and SP don't have 8-bit sub-registers in x86 mode. - Jakob Stoklund Olesen
<GitHub0>
[llvm-lm32/master] Zap the last reference to allocation_order_begin(). - Jakob Stoklund Olesen
<GitHub0>
[llvm-lm32/master] Only call TRI::getRawAllocationOrder to resolve a target-dependent hint. - Jakob Stoklund Olesen