Hello, I am new to JAL and have bought the wisp628 programmer. When I want to dowload a program to the PIC16F877 with the program xwisp2w I get this error...
... Are you the guy that phoned me an hour ago? In that case you should mention that you use Vista and an usb-serial converter, and that the LED connected to...
... Hi Dennis, My guess would be that your power supply is not stable (enough). In any case we'll need more information. At what point does this error occur,...
Yes, I am that guy that phoned you an hour ago. I tried programming with a computer using windws 98 and that has a serial communication port. With this ...
... In that win98 case, do you use a straight cable? Still in win98, could you install python/win32ext/xwisp and try with "xwisp comX term 1200" and a short...
... want to ... this ... error ... you using ... I am using a 12 Volt adaptor where I have connected a 7805 voltage regulator that can profide 1A. The hardware...
... Hi Dennis, Looks ok to me. Just to make sure you could try: xwisp2w baud 19200 port 4 target 16f877 go c:\picdev\projecten\test\test Wouter has recommended...
... work? over the phone he confirmed that the LED blinked twice. [ Here are two Dutch guys discussing a problem of a third Dutch guy, all in English :) ] ...
... The fourth (me) didn't show up here so far, but suggested in a direct E-mail to the OP to check the 'Problem Determination' section of the Xwisp2 users...
Hi Bert ... Indeed, not exactly, therefore I said 'problems like his'. In most of the cases it is a wiring problem (I myself frequently connect clock and data...
... to which MCLR, target or chip in the Wisp628, and which problem did this solve? Wouter van Ooijen -- ------------------------------------------- Van Ooijen...
... So it wasn't connected correctly at all. The best way to test your equipment is to built a flashing led schematic from Wouters website and use the hex...
Couldn't figure out why this message didn't get to this list. I sent it to the wrong list %*&%^*&! Hi All I've run into a number of problems like this one not...
One "feature" that I have just come across for multibyte arrays (eg byte*2). If you have something like this: var volatile sbyte*2 res const sbyte*2 result[] =...
Greetings, ... sent it to ... correct ... This was discussed a while ago on the beta team list. The problem is how JAL handles the universal type which is any...
Greetings, ... byte*2). Argh -- this is another side effect of my introduction of pointers. I'll add it to the list. ... 1 you ... which it ... you need...
hi Kyle, ... <snip> ... When pushing the operands on the stack, I assume you notice the type of operands. So not optimal in code space, but fairly simple (at...
Hi Kyle, Thanks for that explanation. I was just going to give another example were the answer was not what I expected when I noticed your reply. It was a ...
Yes, by putting sbyte*3 around one of the operands the correct answer is produced. e.g. divhelper = sbyte*3(tmp[x]) * mixCh0[x] ;sbyte*3 = sbyte*2 * sbyte...
In the following line divhelper = sbyte*3(tmp[x]) * mixCh0[x] ;sbyte*3 = sbyte*2 * sbyte * 1 I get [Warning] (mixchannels.jal) [Line 560] signed/unsigned...
Greetings, ... example were ... What you're seeing here is some funkiness with the multiply and divide code -- it is written such that it will work with the...
Ahh, some of that funkiness is causing me some problems getting the job done in a limited amount of time. I need to do some calculations in a 10 ms time ...
Greetings, ... * sbyte ... something ... I get both warnings: test.jal:12: warning: assignment to smaller type; truncation possible test.jal:12: warning:...
... From your manual "If both operands are the same width, and one is unsigned, the result is unsigned." I just ran a small test: var byte a = 10 var sbyte b =...
