<wpwrak> wolfspraul: hmm, a bit tricky then. not very expensive but still.
<wpwrak> one consideration would also be how many of those already made would actually be sellable. e.g., if you're thinking of making a new revision, some of the boards in stock may actually have zero commercial value.
<wpwrak> (and could be used to sweeten the current M1 offer, my declaring them as a free extra for early adopters)
<wpwrak> if you can lower the price of the whole system in the future, dropping the jtag would also justify that change to existing customers.
<wolfspraul> jtag-serial is included with every m1 for the time being
<wolfspraul> we need to learn much more about who buys it, where, etc. before optimizing this
<wpwrak> good. so we're on the same page :)
<wpwrak> btw, did you try to plant M1 at any other news outlet than The Reg ?
<wolfspraul> no
<wolfspraul> overloaded
<wolfspraul> but I work on all this, and of course will continue
<wpwrak> (overload) hmm. so this also means ... november news then ? :)
<wolfspraul> ha ha
<wolfspraul> :-)
<wolfspraul> you do want to push me into the cemetery faster...
<kristianpaul> bien, igual .... -_-
<kristianpaul> oops
<wolfspraul> yes I am late on that too
<wolfspraul> I am sitting here explaining m1 to our new China sales person :-)
<wpwrak> heh, great ! :)
<wpwrak> (the sales person, not the cemetery :)
<wolfspraul> the plan is to get it into one reference club, then work with that club to polish the product, in parallel sell that club's success story to other clubs
<wolfspraul> the sale into the first club is 'almost' a done deal
<wolfspraul> but I want to see cold hard cash first...
<wpwrak> reference customers sound like a good idea
<wpwrak> ;-)
<wpwrak> they should consider the value of all the free support they're getting. priority access to the product's development team of a globally acting enterprise. where do you find that without putting a six-figure sum on the table ? ;-)
<wpwrak> no pictures ?
<wpwrak> description sounds good, though. avantgarde, just the right fit
<wolfspraul> just opened 2 weeks ago
<wpwrak> hmmm. i locked the usual suspect yet i see this  "Checking : flickernoise.fbi(rescue)(CRC)      CRC failed". looking forward to a deeper analysis of what happened to my lock bits ...
<wpwrak> s/suspect/suspects/
<wolfspraul> kristianpaul: very nice! (downloading, haven't read yet)
<wolfspraul> kristianpaul: oh my :-)
<wolfspraul> just look at the usage restrictions on page 2 :-)
<wolfspraul> opencores, ha ha
<wolfspraul> some people really always have it backwards
<wpwrak> and where are the remaining 200 pages of fine print ? there are LOTS of cases they don't cover :)
<stekern> that is the version before the restrictions were added...
<wolfspraul> seriously? they were *added* at some point?
<wolfspraul> my god
<wolfspraul> I mean we all learn, adapt, etc. we see what works and what doesn't work. but the motivation of someone adding this to an existing document must be the weirdest thing I can imagine.
<wolfspraul> I am 100% sure they did not have cases where those restrictions actually made a difference. So they must have added them just for the heck of it :-)
<wolfspraul> stekern: ok but that version has no copyright information at all, and with the very specific information on later version I'd hesitate to reuse the older one as a starting point
<wolfspraul> it seems they don't want to be built upon...
<stekern> well, "they" are different "theys" in the different versions
<sb0> do not read any opencores guidelines. they lead to the results we know too well.
<stekern> I think the opencores guidelines are fairly good, a bit outdated in parts perhaps though
<stekern> the ohwr ones are good too
<sb0> cheap fpga board with sdram and usb: http://www.xess.com/prods/prod048.php
<kristianpaul> wolfspraul: yeah license is a shame :-/
<kristianpaul> stekern: nice memory ;)
<kristianpaul> i agree with stekern
<kristianpaul> also opencores is the nearest thing we have to an upstream (for some glue stuff like wishbone, ethernet cores?) :) and yes there is ohwr :-)
<wpwrak> hmm, no hw development, no hw commercialization, no sw development ?
<wpwrak> hmm, a question about the bitstream format: our standby bitstream ends in ... 00 b0  04 00 ...  ff ff ...
<wpwrak> i understand the 00 b0 and the ff ff but not the 04 00. ff ff is simply uninitialized NOR.
<wpwrak> 00 b0 must be the DESYNC WORD from table 5-50 page 102 of ug380. i.e., 0x000d, bit-swapped
<wpwrak> but where does the 04 00 come from ? (or 0x2000, bit-swapped)
<xiangfu> wpwrak,  0400 bit-swapped is 2000 which is is NOOP, seems there are two many NOOP at the end of bitstream
<wpwrak> aah, they never introduce it in the document but they use the NOOP at a few places. thanks !
<wpwrak> i think the trailing NOOPs in standby.fpd that don't get flashed into the NOR are a mismatch between the file and what urtag expects
<wpwrak> urtag seems to expect file data to be a multiple of a certain size, maybe N*16 bytes. anything that's not such a multiple is ignored
<wpwrak> and the file doesn't have such padding
<wpwrak> i guess urtag should either do the padding itself or complain if it's given a file with an unaligned size
<xiangfu> wpwrak, yes.
<xiangfu> needs to read more document and the urjtag code :)
<wpwrak> hmm, http://www.milkymist.org seems to have troubles
<kristianpaul> ah still
<wpwrak> apparently some database backend not responding
<mwalle> wpwrak: the bitstream loading code?
<mwalle> (padding, multiple of N)
<wpwrak> yes
<wpwrak> well, the bitstream flashing code
<mwalle> mh?
<mwalle> fjmem ?
<wpwrak> file -> NOR. somewhere along the path, something seems to go wrong with unpadded files
<mwalle> mh, ok no code from me expect the fjmem core ;)
<wpwrak> hehe :)