[quote author="lura"]Its easy.... Just start jawis. Select external clock, but do not connect ols to external clock physically Start capture.... So result be will never showed since clock are not clocking..... Red - stop capture - button is not active, so what to do ? Just open capture setup dialog again , change to internal clock.... or whatever.... AND Start capture again. You will see mesage that capture is abotred and reason is, that com port is not avalaible... Its all. Just restarting of PC/win is solution since this is occured....[/quote]
Jawi Was reading above post by alexwhittemore and had a look at salae site http://www.saleae.com/logic/features/ I think the colour idea is a useful one if it could be implemented so that the colour for each channel is able to be changed for different probe wiring colours.
Thanks dogsbody for the quick reply just tried it and everything now works fine.I really do not know what happened originally but i should have realised that burning just the firmware with the pickit2 would erase the bootloader,my only excuse is it was a long hot day at work and the A/C had broken down so i think my brain was a bit cooked.Anyway thanks again for your help and contribution to the site. Nick
[quote author="dogsbody"][quote author="ian"]I'll add address evaluation to the bootloader.[/quote] Definitely a good idea.
btw, belated thanks for the posting in "OLS files and utilities"! Can you edit it have the 2.01 release? I'd like to avoid burning anyone who tries updating to 2.6 firmware... :-(
Thanks! -- IED[/quote]
Unfortunately i got burnt yesterday before i saw this (oh well that will teach me for jumping in to quickly) and i did see the warning in the winloader dialog box but went ahead anyway as i do have a pickit2 and thought it wouldn't be much of a problem to reflash the bootloader if i had to .
I had upgraded to meta4 core and then went to upgrade pic to v2.6 and it crashed and appeared to break the bootloader so i got out my pickit2 soldered a header on the board and flashed this bootloader OLSv1-DUMP-FW21BL2-16MHz and that appeared to work as now OLS is working again.
There is still a problem however, i now can no longer update the pic with any version of fw_update or either version of ols_winloader.With fw_update it tells me device not found and ols_winloader v2.01 states that the file i am trying to burn is 8 bytes too small and if i proceed anyway i get error reading file failed file to large for fpga flash rom.V2.0 just says error writing pic firmware. Windows is seeing it as a comm port with vid 04d8 & pid fc92 .It is also possible to flash any version of the firmware using pickit2 and they work.
Ian mentioned "Careful, those last 8 bytes are the config words, we need to protect that page because the firmware ships without them, and there are both 20mhz and 16mhz crystal OLSes." Could this be the problem , i really am not sure because i thought that the config bytes are set in the code i.e in the hex file i burnt.
If you setup a capture that never comes you can not abort it because the stop capture button is not highlighted.The only way you can abort, is to reopen the capture dialog box and cancel it, the stop capture button then becomes highlighted and can abort the capture. Have tried same setup with v0.9.2 and it works fine. Setup is Verilog v5 on win7 32bit if you need more info let me know.
[quote author="dogsbody"][quote author="kandos"]Getting much the same errors and have done much the same i.e delete all copies of felix-cache etc only difference i am using win7.My 0.9.2 also works fine with ver4.[/quote] I wonder if this has something to do with high COM port numbers. I installed OLS on a notebook, and after scratching my head over drivers, got 0.9.3-b4 capturing no problem. The port number was COM6. On my development machine, which crashes, the port number is COM11.
Kandos, what port number are you using?
I wonder if it's something like a string buffer that's too short? ie: COM1to COM9 work, but COM10 & higher overflow the buffer and fail. Might even be a bug that's been there forever, but a recent change is now manifesting it... -- IED[/quote] Your on to something there.I was using com 13 changed to com 3 and it now captures.As an added bonus the RLE appears to have been fixed,did a quick test with the same setup as referred to in this post viewtopic.php?f=23&t=1711&start=45#p16744
The results now look good.Must go and mow the lawn will do some further testing a little later. Nick
Excellent presentation Jack It has made my mind up on whether i should delve into FPGA"s.Decided Yes so have ordered a Papilo board and the first thing i will try will be recreating this example.Thanks for that and hope to see more. Nick
[quote author="dogsbody"]Yup, WinXP. Perhaps an updated library in 0.9.3 references an API only available in Vista & Win7? I dug into the error report. Here is a little more information:
The "#" character didn't bother 0.9.2. Also, I discovered that if in I replace binorg.apache.* with "org.osgi.compendium-4.2.0.jar" & "org.apache.felix.main-3.0.1.jar" from 0.9.2, it runs fine with the "#". Something broke there at least.
I know it's painful, but one debug method is reverting changes & reapplying them one-by-one. If you've an old copy of WinXP, try installing it as a virtual machine in under VMPlayer. It's free from VMWare. -- IED[/quote]
Bit more info. Getting much the same errors and have done much the same i.e delete all copies of felix-cache etc only difference i am using win7.My 0.9.2 also works fine with ver4.
Hi Jawi Thanks for your excellent software and the time that you put in to this project.I have what i hope is a simple request and if it is not then i really don't need it that much but would it be possible to have a remove all cursors option in the cursor menu .This would save having to disable them one at time.
I have upgraded my ols to the new ver4 and thought i would use it to debug a Playstation2 game controller to usb converter i built with a pic 18f4550.(I know i could buy one real cheap but i have some spare pic's and i learn more if i build things myself ).
Found the problem i was having and the controller is now functioning in windows,The Pic code (asm) i use for the controller is software spi with a 9 byte packet LSB.
it then just loops sending 0x01 0x42 0x00 0x00 0x00 0x00 0x00 0x00 0x00 to "read" the controller. If i do a capture without RLE and trigger on c/s low i can get the first 2 packets as seen here. [attachment=1] It is possible to see "read" packets if i just do a random capture with no trigger, but I was trying to see a few more packets from the start so i thought i could use the RLE and trigger on c/s low , but i can not seem to get a good outcome as seen here. [attachment=0] I have tried various settings to no avail and do not know if there is something wrong with the RLE ,or if i am missing some vital point as to its use.Can anyone give me some advice?
I am using the FPGA ver4 and OLS ver0.9.2 (Can not seem to get 0.9.3 working yet).
Nick
P.S To Dogsbody & Jack sorry i left the conversation abruptly the other night but my modem seems to have developed a heat related fault and only works for short periods.
