EMC: 03jepler 07master * r7b03efb4247f 10/docs/src/drivers/pico_ppmc.lyx: looks like index-enable is in the ppmc driver nowadays
EMC: 03jepler 07master * ra211875cd93b 10/src/emc/rs274ngc/interp_read.cc: Allow unary negation of expressions
[03:48:45] <jepler> http://emergent.unpy.net/files/sandbox/0001-new-load-pin-immediately-copies-input-to-output.patch
I don't know exactly what jfingle is up to, but this is a bit of a glaring omission in retrospect
[Global Notice] Hi all, it appears one of our volunteers set a network ban which were way too wide last night in an attempt to deal with the current attacks; as a result a truckload of genuine users have been banned from the network, with a misleading and unhelpful message. For more information please enable +w in your client. Apologies for the inconvenience, we'll try tidy up after them now.
EMC: 03jthornton 07master * r708a1bc47b5b 10/docs/src/hal/ (basic_hal.lyx images/wsum01.png): add info about weighted sum
EMC: 03jthornton 07master * r5d7cc06ca8a8 10/docs/man/man9/ (6 files): parameters were converted to pins on 2008-10-26
* jthornton thinks he didn't miss any
parameters converted to pins, I think
micges: have you tried cooling the southbridge?
I didn't checked that
I'll do that
but one hang was 3 min after start
boot up pc, load emc some jog-> close emc -> start again -> mesa hang
today on my devel pc I'll loaded over and over my plasma config (with mesa) and once I've loaded joints_axes3 sim and after that my plasma mesa config didn't load
maybe this helps a little
maybe this is driver closing issue
do you mean it worked fine until you ran joints_axes3 sim, and after that the hostmot2 driver failed to load the 5i20 firmware?
yes that was today
strange... sim shouldnt touch the mesa hardware at all, as i understand it
but two days ago it was on real plasma cutter with only mesa config
is it repeatable, does sim always break firmware loading? does a reboot always bring it back?
and it doesn't touch
reboot bring it back in 60% of cases, rest is restored by either power off for 10min or mesa swap to other pci
I can't tell if sim always break firmware loading
this is only observed on that Asus P5KPL-CM motherboard, never on any other machines?
it never happened on any hp or my old asus mainboard with celeron (I'm on oit now)
well that's good to hear
hmm I've just recall that we had parport problems with that mainboard too, they burned off with no reason
now we're only using parprot pci card
i wonder how much of the sb got cooked when the parports burned
we have 16 those mb here, 12 were used for machines
3 first mb was parport damaged
but my parport at work (last hang) was never connected to sth
so still no scheme but it seems that tthose mb are sh*t
that's what it sounds like to me too
gladly only 4 machines are far away from here ;P
rest was simply replacement of old pc here at workshop
and parport that burned off was fully optoisolated and on it was simple slow spi transfer
anyway I will make some changes on monday, and many thanks for looking and testing this issue
looks like there's a windbond chip on there, so the parport drivers would not be in the same package as the south bridge
if you've got a bad batch of systems, the power supplies might also be to blame
micges: maybe a BIOS upgrade will help. The ASUS P5KPL-CM uses common chipset parts (G31, ICH7) , so if theres a problem
I'd like to get to the bottom of it. I'm ordering a P5KPL-CM from Newegg for testing here so I can try and duplicate your troubles
PCW: when you have a chance, can you send me the card and ucf files for building the 3x20 firmwares?
is there a different 'top' file for the PCIE bridge too?
ASUS at least used to be a good name... Though the P5KPL-CM is only $59.99 so its a prettty low end MB
jepler: did you change the logger software?
I see that they're now logger_1 and logger_2
SWPLinux: I haven't touched it in weeks
oh. I may have just not noticed :)
I don't recall intentionally changing the nicks they use
ok. I just happened to notice the topic for this channel, looked for logger_dev, and saw logger_2
jepler: Top file is the same: Top9054...
I think there are a bunch of source changes to accommodate 144 pins including a change in the IDROM version
so firmware built from the new source will not work with 2.3.4
PCW: I see
PCW: I don't even have one of the cards, but I want to get it added to my scripts that build "all" the firmwares
SWPLinux: that happened as they somehow reconnected today
I saw the new nicks (_1 & _2) connect, and the other ones die a bit later
may be connected to the new ircd server
PCW: I'll try bios update on one machine and I'll look for some scheme of that issue
so maybe the cron thing is working :)
wow. $439 for 16GB RAM
jepler: The problem is that the old (V2) IDROM had the pindescs terminated by a 0 sentinel
with 144 pins we used all the IDROM locations so theres no room for the sentinel. I changed the IDROM for all
cards to the new layout and changed the IDROM version (so the older driver will bail). I guess I could make the IDROM version
card dependent so only the 3X20 uses the new version for now. I wont be able to get to this for a week or so however.
(now the choice is all new source that will make firmware that will only work with 2.4 or old source that does not include the 3X20)
2.4 seems like a fine time to add support for new hardware
PCW: I don't see a lot of firmware updates for emc 2.3 in the future
hmph, what's wrong with my Makefile
(make is great, once you've convinced it to do what you want...)
hey PCW, got a website suggestion for you. Make the part numbers in the price list be links to the product pages
(I haven't found the 6I68 yet, going through the categories on the left)
I'm pretty sure the latest HM2 driver will work with either old or new firmware, but of course the old HM2 driver will bail on new bitfiles
or put the prices with the products
Sounds like work to me...
IMO it's quite an irritation to not see the feature list and price for a product together
right. the price list is a good place to jump to the descriptions
on some sites you can't find the price at all without signing up or calling - twice as bad - I never ever buy from them
since it lists all the products in one place
and also never buy from places that make you sign up to get the datasheets/specs
The 6I68 is not on the website yet, (it just looks like a 7I68 with a 1 lane PCIE slot connector)
hmmm. PCW, is it a typo that the 1MGate and 2MGate 3x20's are the same price?
if so, I'll take a 2M before the price goes up ;)
Is the 2Mgate one the one that can't be built with free xilinx ise?
I always remember there's one that can't be
We will have a much cheaper integrated PCIE card later this year
(1M and 2M FPGA prices are the same, note for 2M Webpack will not work)
and if I get my way that board will be a very second-class citizen, since my plan is to build all the firmwares we ship with the free ise
(X gets there money back from licenses I guess)
hmmm. what's the largest spartan3?
they usually add the non-flagship parts to ISE a year or two later
(and take them out a few years before, so you have to fork over the cash to support legacy applications)
Looks like all of the SP6 are supported
(New PCIE uses SP6)
WARNING:Xst:1336 - (*) More than 100% of Device resources are used
how is this only a warning!?
is that the last placement/optimization stage?
SWPLinux: it must not have been
so many messages scroll by
later on it does error
ok, so my assumption is that either they're dumb and that should be an error, or they may be able to remove some stuff with later optimizations
I wonder if my older ISE is dumber than pcw's or whether I'm missing some optimization flag; at the end it still doesn't fit, but this should be the same as a bitfile that he's provided us..
(this is some 7i43 firmware, SVST4_6S)
using the 400k or 200k part?
the suffix "S" indicates the 200k part
urp, I just discovered that (A) I had a bug in my build script that caused errors in the ise subprograms to be ignored
and (B) other firmwares don't fit either, such as 5i20 SVST8_4
what version are you using?
oh. that's at least 2 years old I think
I wonder in how many other programs I've assumed the return value of os.spawnvp(P_WAIT, ...) was the same as os.waitpid(...) i.e., suitable for WEXITSTATUS-type checks
- raise SystemExit, os.WEXITSTATUS(r)
+ raise SystemExit, r
looks like the "-r" (disable register ordering) option to map, which is suggested in the error messages, makes the 3 non-fitting designs fit again; now to do the long step of seeing whether everything builds with map -r
I use 9.2 normally (11.4 only for SP6)
hi again pcw
11.4 took something like 18G to install
any idea if you have set the equivalent of map -r in the project when you build (some of) these firmwares?
I got similar errors for 5i20 SVST8_4, 7i43 SVST4_6S, and 4i65 SVST8_4: http://pastebin.ca/1752851
and as I was saying, they went away when I specified -r
I can take a look at my build options, let me try building 5I20 SVST8_4...
5i20 SVST8_4 builds ok without -r
I assume there's a downside to -r, but the docs aren't really spelling it out for me
As usual, it may be my fault, you may have the source with the probe enabled counters always used regardless of whether there is a probe input
-r may limit the speed, but HM2 should meet timing easily
well, in hostmot2.vhd I have 'useprobe1: if UseProbe generate ...' and other stuff that looks like it is making choices based on whether there's a probe input
and in the toplevel files, lines like constant UseProbe: boolean := PinExists(ThePinDesc,QCountTag,QCountProbePin);
any settings from the project files I don't have, so it could also be something earlier in the build process
OK well its not that, let me look at the log file
if you wonder what's in any of the files I'm building from: http://git.unpy.net/view?p=hostmot2-firmware.git;a=tree;h=66b42bf5e6a762e576a24384cac24478b757b0e4;hb=66b42bf5e6a762e576a24384cac24478b757b0e4
bbl, it's beer-o-clock in Nebraska
EMC: 03micges 07defer-format * r2f33e257bebb 10/ (429 files in 145 dirs): Merge branch 'master' into defer-format
[22:21:11] <PCW> http://pastebin.ca/1752907
is the command log for building top9030
(should you scroll back...)
[22:26:22] <PCW> http://filebin.ca/qdbacb
is the latest source including the 3X20 support (but rev3 IDROM so not for 2.3)
PCW: thanks, will look later