subject:"\[jallib\] USB

It seems to me that flushing was the problem. It works with interrupts but
jal 1.7.0 seems to not have the usb serial interrupt sample for pic18f4550?

That delay is ok if you program the pic while is connected to usb. It tooks
a while until pc see the pic, but that depends on pc, os, etc. If you send
only once a text (as the sample is), there are big chances to not see it on
pc.


On Fri 16 Dec 2022, 9:02 PM Rob CJ  Hi Hans, Vasile,
>
> What has been changed that it now works?
>
> If I look at the setting for the chip I do not see a difference with the
> program that Hans had sent before.
>
> I see in the program below a delay of 5 seconds but that will cause a
> problem.
>
> There are two ways to use the USB library, without interrupt (which used
> to be the only way to use it) and with interrupt.
>
> If you use it without interrupt you have to call the *usb_serial_flush() 
> *routine
> regularly otherwise the USB wil stop working.
>
> If you cannot serve this function regulary then you should use the library
> in the mode that is uses the interrupt which I see is being used in the
> last example.
>
> If this 5 seconds delay was in the previous program then that may have
> caused the USB problem.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jallib@googlegroups.com  namens hans <
> hanze...@zeelandnet.nl>
> *Verzonden:* vrijdag 16 december 2022 18:52
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
>
> Hello Vasile
> I have always worked as you indicated. Program, unplug everything and then
> plug it back in. prompt response that the case was not recognized. See my
> previous message.
> Now your latest version, does nothing at all. Loaded the previous version
> again and it works as stated before.
> regards
> Hans
>
> Op vrijdag 16 december 2022 om 18:07:52 UTC+1 schreef vasile:
>
> Hans,
> I think you are doing in this way:
> 1. USB connection is kept permanently between your board and PC
> 2. your board is programmed with pickit and after programming you expect
> to see immediately the pic USB device in your PC
> right?
>
> After programming you have to disconnect your PC from USB and connect it
> again, wait a bit until the computer sees your device.
> I think the original sample will work in this way, however below is the
> the sample (using interrupts) which should work without disconnecting your
> PIC from USB after programming ( please note I did not tested, no
> PIC18F4450 or PIC2550 available now).
>
> Finally you may comment the 5s delay if you wish, but you may loss the "
> JALLIB USB Serial Demo" string.
> Hopefully will work for you.
>
> -- ---
> include 18f4550
>
>
> -- even though the external crystal is 20 MHz, the configuration is such
> that
> -- the CPU clock is derived from the 96 Mhz PLL clock (div2), therefore set
> -- target frequency to 48 MHz
> pragma target clock   48_000_000
>
>
> -- fuses
> pragma target PLLDIVP5  -- divide by 5 - 20MHZ_INPUT
> pragma target CPUDIVP1  -- [primary oscillator src: /1][96
> mhz pll src: /2]
> pragma target USBDIVP2  -- CLOCK_SRC_FROM_96MHZ_PLL_2
> pragma target OSC   HS_PLL
> pragma target FCMEN DISABLED
> pragma target IESO  DISABLED
> pragma target PWRTE DISABLED-- power up timer
> pragma target VREGENENABLED -- USB voltage regulator
> pragma target VOLTAGE   V21 -- brown out voltage
>
> pragma target BROWNOUT  DISABLED-- no brownout detection
> pragma target WDTPS P32K-- watch dog saler setting
> pragma target WDT   CONTROL -- watchdog software controlled
> pragma target CCP2MUX   pin_C1  -- CCP2 on pin C1
> pragma target PBADENDIGITAL -- digital input port<0..4>
> pragma target LPT1OSC   LOW_POWER   -- low power timer 1
> pragma target MCLR  EXTERNAL-- master reset on RE3
> pragma target STVR  DISABLED-- reset on stack over/under flow
> pragma target LVP   ENABLED -- allow low-voltage programming
>
> pragma target XINST DISABLED -- extended instruction set
> pragma target DEBUG DISABLED-- background debugging
> pragma target CP0   DISABLED-- code block 0 not protected
> pragma target CP1   DISABLED-- code block 1 not protected
> pragma target CP2   DISABLED-- code block 2 not protected
> pragma target CP3   DISABLED-- code block 3 not protected
> pragma target CPB   DISABLED-- bootblock code not write
> protected
> pragma target CPD   DISABLED--

Re: [jallib] USB_help

Aleluia! Say thanks to Rob which adjusted the usb serial lib with
interrupts.
The serial usb connectivity depends also on laptop and terminal. Use a
terminal which does not hang in a bunch of data. Do not disable intcon_gie
if use usb serial with interrupts. Do not expect to solve fast things in
pic while usb communication works. Maibe packing data and send it all from
time to time.
Nothing more to say.

On Fri 16 Dec 2022, 10:37 PM hans  Hi Vasile, Rob,
> Having often problems with the LVP I often disable this. I did this in the
> first program from Vasile and have forgotten this to mention.
> Doing the same in the last version and IT WORKS
> !!!
> But i had to start the PICKIT several times again with all trics i know.
> GRR
> regards
> Hans
>
>
>
> Op vrijdag 16 december 2022 om 20:02:47 UTC+1 schreef rob...@hotmail.com:
>
>> Hi Hans, Vasile,
>>
>> What has been changed that it now works?
>>
>> If I look at the setting for the chip I do not see a difference with the
>> program that Hans had sent before.
>>
>> I see in the program below a delay of 5 seconds but that will cause a
>> problem.
>>
>> There are two ways to use the USB library, without interrupt (which used
>> to be the only way to use it) and with interrupt.
>>
>> If you use it without interrupt you have to call the *usb_serial_flush()
>> *routine regularly otherwise the USB wil stop working.
>>
>> If you cannot serve this function regulary then you should use the
>> library in the mode that is uses the interrupt which I see is being used in
>> the last example.
>>
>> If this 5 seconds delay was in the previous program then that may have
>> caused the USB problem.
>>
>> Kind regards,
>>
>> Rob
>>
>> --
>> *Van:* jal...@googlegroups.com  namens hans <
>> hanz...@zeelandnet.nl>
>> *Verzonden:* vrijdag 16 december 2022 18:52
>>
>> *Aan:* jallib 
>> *Onderwerp:* Re: [jallib] USB_help
>> Hello Vasile
>> I have always worked as you indicated. Program, unplug everything and
>> then plug it back in. prompt response that the case was not recognized. See
>> my previous message.
>> Now your latest version, does nothing at all. Loaded the previous version
>> again and it works as stated before.
>> regards
>> Hans
>>
>> Op vrijdag 16 december 2022 om 18:07:52 UTC+1 schreef vasile:
>>
>> Hans,
>> I think you are doing in this way:
>> 1. USB connection is kept permanently between your board and PC
>> 2. your board is programmed with pickit and after programming you expect
>> to see immediately the pic USB device in your PC
>> right?
>>
>> After programming you have to disconnect your PC from USB and connect it
>> again, wait a bit until the computer sees your device.
>> I think the original sample will work in this way, however below is the
>> the sample (using interrupts) which should work without disconnecting your
>> PIC from USB after programming ( please note I did not tested, no
>> PIC18F4450 or PIC2550 available now).
>>
>> Finally you may comment the 5s delay if you wish, but you may loss the "
>> JALLIB USB Serial Demo" string.
>> Hopefully will work for you.
>>
>> -- ---
>> include 18f4550
>>
>>
>> -- even though the external crystal is 20 MHz, the configuration is such
>> that
>> -- the CPU clock is derived from the 96 Mhz PLL clock (div2), therefore
>> set
>> -- target frequency to 48 MHz
>> pragma target clock   48_000_000
>>
>>
>> -- fuses
>> pragma target PLLDIVP5  -- divide by 5 - 20MHZ_INPUT
>> pragma target CPUDIVP1  -- [primary oscillator src:
>> /1][96 mhz pll src: /2]
>> pragma target USBDIVP2  -- CLOCK_SRC_FROM_96MHZ_PLL_2
>> pragma target OSC   HS_PLL
>> pragma target FCMEN DISABLED
>> pragma target IESO  DISABLED
>> pragma target PWRTE DISABLED-- power up timer
>> pragma target VREGENENABLED -- USB voltage regulator
>> pragma target VOLTAGE   V21 -- brown out voltage
>>
>> pragma target BROWNOUT  DISABLED-- no brownout detection
>> pragma target WDTPS P32K-- watch dog saler setting
>> pragma target WDT   CONTROL -- watchdog software controlled
>> pragma target CCP2MUX   pin_C1  -- CCP2 on pin C1
>> pragma target PBADENDIGITAL -- digital input port<0..4>
>>

Re: [jallib] USB_help

Hi Vasile, Rob,
Having often problems with the LVP I often disable this. I did this in the 
first program from Vasile and have forgotten this to mention. 
Doing the same in the last version and IT WORKS 
!!!
But i had to start the PICKIT several times again with all trics i know. 
GRR
regards
Hans



Op vrijdag 16 december 2022 om 20:02:47 UTC+1 schreef rob...@hotmail.com:

> Hi Hans, Vasile,
>
> What has been changed that it now works?
>
> If I look at the setting for the chip I do not see a difference with the 
> program that Hans had sent before.
>
> I see in the program below a delay of 5 seconds but that will cause a 
> problem.
>
> There are two ways to use the USB library, without interrupt (which used 
> to be the only way to use it) and with interrupt.
>
> If you use it without interrupt you have to call the *usb_serial_flush() 
> *routine 
> regularly otherwise the USB wil stop working. 
>
> If you cannot serve this function regulary then you should use the library 
> in the mode that is uses the interrupt which I see is being used in the 
> last example.
>
> If this 5 seconds delay was in the previous program then that may have 
> caused the USB problem.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* vrijdag 16 december 2022 18:52
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
> Hello Vasile
> I have always worked as you indicated. Program, unplug everything and then 
> plug it back in. prompt response that the case was not recognized. See my 
> previous message.
> Now your latest version, does nothing at all. Loaded the previous version 
> again and it works as stated before.
> regards
> Hans
>
> Op vrijdag 16 december 2022 om 18:07:52 UTC+1 schreef vasile:
>
> Hans,
> I think you are doing in this way: 
> 1. USB connection is kept permanently between your board and PC
> 2. your board is programmed with pickit and after programming you expect 
> to see immediately the pic USB device in your PC
> right?
>
> After programming you have to disconnect your PC from USB and connect it 
> again, wait a bit until the computer sees your device.
> I think the original sample will work in this way, however below is the 
> the sample (using interrupts) which should work without disconnecting your 
> PIC from USB after programming ( please note I did not tested, no 
> PIC18F4450 or PIC2550 available now).
>
> Finally you may comment the 5s delay if you wish, but you may loss the " 
> JALLIB USB Serial Demo" string.
> Hopefully will work for you.
>
> -- ---
> include 18f4550
>
>
> -- even though the external crystal is 20 MHz, the configuration is such 
> that
> -- the CPU clock is derived from the 96 Mhz PLL clock (div2), therefore set
> -- target frequency to 48 MHz
> pragma target clock   48_000_000
>
>
> -- fuses
> pragma target PLLDIVP5  -- divide by 5 - 20MHZ_INPUT
> pragma target CPUDIVP1  -- [primary oscillator src: /1][96 
> mhz pll src: /2]
> pragma target USBDIVP2  -- CLOCK_SRC_FROM_96MHZ_PLL_2
> pragma target OSC   HS_PLL
> pragma target FCMEN DISABLED
> pragma target IESO  DISABLED
> pragma target PWRTE DISABLED-- power up timer
> pragma target VREGENENABLED -- USB voltage regulator
> pragma target VOLTAGE   V21 -- brown out voltage
>
> pragma target BROWNOUT  DISABLED-- no brownout detection
> pragma target WDTPS P32K-- watch dog saler setting
> pragma target WDT   CONTROL -- watchdog software controlled
> pragma target CCP2MUX   pin_C1  -- CCP2 on pin C1
> pragma target PBADENDIGITAL -- digital input port<0..4>
> pragma target LPT1OSC   LOW_POWER   -- low power timer 1
> pragma target MCLR  EXTERNAL-- master reset on RE3
> pragma target STVR  DISABLED-- reset on stack over/under flow
> pragma target LVP   ENABLED -- allow low-voltage programming
>
> pragma target XINST DISABLED -- extended instruction set
> pragma target DEBUG DISABLED-- background debugging
> pragma target CP0   DISABLED-- code block 0 not protected
> pragma target CP1   DISABLED-- code block 1 not protected
> pragma target CP2   DISABLED-- code block 2 not protected
> pragma target CP3   DISABLED-- code block 3 not protected
> pragma target CPB   DISABLED-- bootblock code not write 
> protected
> pragma target C

Re: [jallib] USB_help

2022-12-16 Thread Rob CJ

Hi Hans, Vasile,

What has been changed that it now works?

If I look at the setting for the chip I do not see a difference with the 
program that Hans had sent before.

I see in the program below a delay of 5 seconds but that will cause a problem.

There are two ways to use the USB library, without interrupt (which used to be 
the only way to use it) and with interrupt.

If you use it without interrupt you have to call the usb_serial_flush() routine 
regularly otherwise the USB wil stop working.

If you cannot serve this function regulary then you should use the library in 
the mode that is uses the interrupt which I see is being used in the last 
example.

If this 5 seconds delay was in the previous program then that may have caused 
the USB problem.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: vrijdag 16 december 2022 18:52
Aan: jallib 
Onderwerp: Re: [jallib] USB_help

Hello Vasile
I have always worked as you indicated. Program, unplug everything and then plug 
it back in. prompt response that the case was not recognized. See my previous 
message.
Now your latest version, does nothing at all. Loaded the previous version again 
and it works as stated before.
regards
Hans

Op vrijdag 16 december 2022 om 18:07:52 UTC+1 schreef vasile:
Hans,
I think you are doing in this way:
1. USB connection is kept permanently between your board and PC
2. your board is programmed with pickit and after programming you expect to see 
immediately the pic USB device in your PC
right?

After programming you have to disconnect your PC from USB and connect it again, 
wait a bit until the computer sees your device.
I think the original sample will work in this way, however below is the the 
sample (using interrupts) which should work without disconnecting your PIC from 
USB after programming ( please note I did not tested, no PIC18F4450 or PIC2550 
available now).

Finally you may comment the 5s delay if you wish, but you may loss the " JALLIB 
USB Serial Demo" string.
Hopefully will work for you.

-- ---
include 18f4550


-- even though the external crystal is 20 MHz, the configuration is such that
-- the CPU clock is derived from the 96 Mhz PLL clock (div2), therefore set
-- target frequency to 48 MHz
pragma target clock   48_000_000


-- fuses
pragma target PLLDIVP5  -- divide by 5 - 20MHZ_INPUT
pragma target CPUDIVP1  -- [primary oscillator src: /1][96 mhz 
pll src: /2]
pragma target USBDIVP2  -- CLOCK_SRC_FROM_96MHZ_PLL_2
pragma target OSC   HS_PLL
pragma target FCMEN DISABLED
pragma target IESO  DISABLED
pragma target PWRTE DISABLED-- power up timer
pragma target VREGENENABLED -- USB voltage regulator
pragma target VOLTAGE   V21 -- brown out voltage

pragma target BROWNOUT  DISABLED-- no brownout detection
pragma target WDTPS P32K-- watch dog saler setting
pragma target WDT   CONTROL -- watchdog software controlled
pragma target CCP2MUX   pin_C1  -- CCP2 on pin C1
pragma target PBADENDIGITAL -- digital input port<0..4>
pragma target LPT1OSC   LOW_POWER   -- low power timer 1
pragma target MCLR  EXTERNAL-- master reset on RE3
pragma target STVR  DISABLED-- reset on stack over/under flow
pragma target LVP   ENABLED -- allow low-voltage programming

pragma target XINST DISABLED -- extended instruction set
pragma target DEBUG DISABLED-- background debugging
pragma target CP0   DISABLED-- code block 0 not protected
pragma target CP1   DISABLED-- code block 1 not protected
pragma target CP2   DISABLED-- code block 2 not protected
pragma target CP3   DISABLED-- code block 3 not protected
pragma target CPB   DISABLED-- bootblock code not write protected
pragma target CPD   DISABLED-- eeprom code not write protected
pragma target WRT0  DISABLED-- table writeblock 0 not protected
pragma target WRT1  DISABLED-- table write block 1 not protected
pragma target WRT2  DISABLED-- table write block 2 not protected
pragma target WRT3  DISABLED-- table write block 3 not protected
pragma target WRTB  DISABLED-- bootblock not write protected
pragma target WRTD  DISABLED-- eeprom not write protected
pragma target WRTC  DISABLED-- config not write protected
pragma target EBTR0 DISABLED-- table read block 0 not protected
pragma target EBTR1 DISABLED-- table read block 1 not protected
pragma target EBTR2 DISABLED-- table read block 2 not protected
pragma target EBTR3 DISABLED-- table read block 3 not protected
pragma target EBTRB DISABLED-- boot block not protected

WDT

Re: [jallib] USB_help

>>> pragma target EBTRB DISABLED-- boot block not protected
>>>
>>> WDTCON_SWDTEN = OFF -- disable watchdog
>>>
>>> const USB_INTERRUPT_DRIVEN = TRUE
>>> include usb_serial
>>> include print
>>> include delay
>>>
>>> -- constants
>>> ; const  byte str_welcome[] = "JALLIB USB Serial Demo app\n"
>>>
>>> -- setup the USB serial library
>>> usb_serial_init()
>>>
>>> -- variables
>>> var bit has_shown_welcome_msg = true
>>> var byte ch
>>> var dword counter_dw  = 0x_
>>> var byte counter_b = 0
>>> var word timer = 0
>>>
>>> delay_1s (5)
>>>
>>> -- main loop
>>> forever loop
>>>
>>>if !defined(USB_INTERRUPT_DRIVEN) then
>>>   -- When the interrupt mode is not used we need to poll the usb ISR 
>>> function
>>>   -- on a regular base, in order to serve the USB requests otherwise
>>>   -- this call can be removed.
>>>   usb_serial_flush()
>>>end if
>>>
>>>
>>>
>>> ;   timer = timer + 1
>>> ;if timer == 500 then
>>> ;   timer = 0
>>>
>>> ;   print_byte_dec (usb_serial_data, counter_b)
>>> ;   _usec_delay( 1 )
>>> ;   usb_serial_data = " "
>>>print_dword_dec( usb_serial_data, counter_dw )
>>> ;   _usec_delay( 1 )
>>>print_crlf(usb_serial_data)
>>> ;   counter_dw = counter_dw + 1
>>> ;   counter_b = counter_b + 1
>>> ;end if
>>> ;   _usec_delay( 1 )
>>>
>>> end loop
>>>
>>> On Fri, Dec 16, 2022 at 3:20 PM hans  wrote:
>>>
>>>> Hey ,
>>>> I have now received the 18F4550 and the 16F1455 and have tried both 
>>>> with the usb_serial samples. programming with PicKit_3, but in all cases I 
>>>> get a warning on my PC (both on win10 and win7) that the USB is not 
>>>> recognized. The Vusb with capacitor reads 3.3 volts and I have programmed 
>>>> both with and without LVP. identical to my previous attempts.
>>>> Apparently USB is not allowed to me
>>>> Hans
>>>>
>>>> Op woensdag 14 december 2022 om 14:19:16 UTC+1 schreef 
>>>> zet@gmail.com:
>>>>
>>>>> Hi Matt
>>>>>
>>>>> I see your question 10-12 now: Wednesday 14-12
>>>>>
>>>>> I am not at home for 2 days.
>>>>>
>>>>> I can test. You hear as soon as possible.
>>>>>
>>>>>  
>>>>>
>>>>> Regards
>>>>>
>>>>> Peter
>>>>>
>>>>>  
>>>>>
>>>>> *Van:* jal...@googlegroups.com [mailto:jal...@googlegroups.com] *Namens 
>>>>> *Matthew Schinkel
>>>>> *Verzonden:* zondag 11 december 2022 04:18
>>>>> *Aan:* jallib 
>>>>> *Onderwerp:* Re: [jallib] USB_help
>>>>>
>>>>>  
>>>>>
>>>>> Hi Hans, what chip is it working on?
>>>>>
>>>>>  
>>>>>
>>>>> Is anyone else able to test the 18f4455 blink usb sample?
>>>>>
>>>>> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>>>>>
>>>>> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't 
>>>>> work. Then I restarted Bert van Dam's old business and tried the same 
>>>>> program on it. that works as it should.
>>>>> I have also tested ports D+ and D- (24 and 23) as inputs and those 
>>>>> ports work as well. I now doubt whether the PIC is broken or something 
>>>>> else 
>>>>> is going on.
>>>>> regards
>>>>> Hans
>>>>>
>>>>> Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
>>>>>
>>>>> Hello champs,
>>>>> I have reassembled everything and I can only conclude that the PIC 
>>>>> itself (has done some things before) is defective. Unfortunately, I no 
>>>>> longer have a PIC with USB, so I put it back in the fridge. I will have 
>>>>> to 
>>>>> look for another one but the market is scarce.
>>>>> Thanks again for your great responses.
&

Re: [jallib] USB_help

serial_data = " "
>>print_dword_dec( usb_serial_data, counter_dw )
>> ;   _usec_delay( 1 )
>>print_crlf(usb_serial_data)
>> ;   counter_dw = counter_dw + 1
>> ;   counter_b = counter_b + 1
>> ;end if
>> ;   _usec_delay( 1 )
>>
>> end loop
>>
>> On Fri, Dec 16, 2022 at 3:20 PM hans  wrote:
>>
>>> Hey ,
>>> I have now received the 18F4550 and the 16F1455 and have tried both with
>>> the usb_serial samples. programming with PicKit_3, but in all cases I get a
>>> warning on my PC (both on win10 and win7) that the USB is not recognized.
>>> The Vusb with capacitor reads 3.3 volts and I have programmed both with and
>>> without LVP. identical to my previous attempts.
>>> Apparently USB is not allowed to me
>>> Hans
>>>
>>> Op woensdag 14 december 2022 om 14:19:16 UTC+1 schreef zet@gmail.com
>>> :
>>>
>>>> Hi Matt
>>>>
>>>> I see your question 10-12 now: Wednesday 14-12
>>>>
>>>> I am not at home for 2 days.
>>>>
>>>> I can test. You hear as soon as possible.
>>>>
>>>>
>>>>
>>>> Regards
>>>>
>>>> Peter
>>>>
>>>>
>>>>
>>>> *Van:* jal...@googlegroups.com [mailto:jal...@googlegroups.com] *Namens
>>>> *Matthew Schinkel
>>>> *Verzonden:* zondag 11 december 2022 04:18
>>>> *Aan:* jallib 
>>>> *Onderwerp:* Re: [jallib] USB_help
>>>>
>>>>
>>>>
>>>> Hi Hans, what chip is it working on?
>>>>
>>>>
>>>>
>>>> Is anyone else able to test the 18f4455 blink usb sample?
>>>>
>>>> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>>>>
>>>> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't
>>>> work. Then I restarted Bert van Dam's old business and tried the same
>>>> program on it. that works as it should.
>>>> I have also tested ports D+ and D- (24 and 23) as inputs and those
>>>> ports work as well. I now doubt whether the PIC is broken or something else
>>>> is going on.
>>>> regards
>>>> Hans
>>>>
>>>> Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
>>>>
>>>> Hello champs,
>>>> I have reassembled everything and I can only conclude that the PIC
>>>> itself (has done some things before) is defective. Unfortunately, I no
>>>> longer have a PIC with USB, so I put it back in the fridge. I will have to
>>>> look for another one but the market is scarce.
>>>> Thanks again for your great responses.
>>>> regards
>>>> Hans
>>>>
>>>> Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
>>>>
>>>> Yep. Matt has right.
>>>>
>>>> 1.The clock speed is esential.
>>>>
>>>> 2. You will notice quite a long delay (5s or so) between plugging the
>>>> pic usb and the moment when OS recognize it on pc. This depends by your
>>>> computer speed and pic firmware contents. If pic clk is wrong, you will not
>>>> see any usb device. After it appears, check on printer/pheripheral for your
>>>> device but watch for any warnings there
>>>>
>>>> On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel >>> wrote:
>>>>
>>>> Also use the code in 18f455_blink_hs_usb.jal
>>>>
>>>>
>>>>
>>>> You are missing this one:
>>>>
>>>> OSCCON_SCS = 0  -- select primary oscillator
>>>>
>>>> On Friday, December 9, 2022 at 9:54:43 PM UTC-5 Matthew Schinkel wrote:
>>>>
>>>> Hi Hans,
>>>>
>>>>
>>>>
>>>> There must be an issue with your circuit. Do you have the correct clock
>>>> speed? Make sure a blink sample and normal serial port is working. Try
>>>> another PC. Windows should pick it up.
>>>>
>>>>
>>>>
>>>> Matt.
>>>>
>>>> On Friday, December 9, 2022 at 3:12:12 PM UTC-5 hans wrote:
>>>>
>>>> Hello,
>>>> Thank you. I did what you recommended. Last Bee and tip from Vasile.
>>>> Same message from windows, not recognized and causing a malfun

Re: [jallib] USB_help

nd loop
>
> On Fri, Dec 16, 2022 at 3:20 PM hans  wrote:
>
>> Hey ,
>> I have now received the 18F4550 and the 16F1455 and have tried both with 
>> the usb_serial samples. programming with PicKit_3, but in all cases I get a 
>> warning on my PC (both on win10 and win7) that the USB is not recognized. 
>> The Vusb with capacitor reads 3.3 volts and I have programmed both with and 
>> without LVP. identical to my previous attempts.
>> Apparently USB is not allowed to me
>> Hans
>>
>> Op woensdag 14 december 2022 om 14:19:16 UTC+1 schreef zet@gmail.com:
>>
>>> Hi Matt
>>>
>>> I see your question 10-12 now: Wednesday 14-12
>>>
>>> I am not at home for 2 days.
>>>
>>> I can test. You hear as soon as possible.
>>>
>>>  
>>>
>>> Regards
>>>
>>> Peter
>>>
>>>  
>>>
>>> *Van:* jal...@googlegroups.com [mailto:jal...@googlegroups.com] *Namens 
>>> *Matthew Schinkel
>>> *Verzonden:* zondag 11 december 2022 04:18
>>> *Aan:* jallib 
>>> *Onderwerp:* Re: [jallib] USB_help
>>>
>>>  
>>>
>>> Hi Hans, what chip is it working on?
>>>
>>>  
>>>
>>> Is anyone else able to test the 18f4455 blink usb sample?
>>>
>>> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>>>
>>> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't 
>>> work. Then I restarted Bert van Dam's old business and tried the same 
>>> program on it. that works as it should.
>>> I have also tested ports D+ and D- (24 and 23) as inputs and those ports 
>>> work as well. I now doubt whether the PIC is broken or something else is 
>>> going on.
>>> regards
>>> Hans
>>>
>>> Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
>>>
>>> Hello champs,
>>> I have reassembled everything and I can only conclude that the PIC 
>>> itself (has done some things before) is defective. Unfortunately, I no 
>>> longer have a PIC with USB, so I put it back in the fridge. I will have to 
>>> look for another one but the market is scarce.
>>> Thanks again for your great responses.
>>> regards
>>> Hans
>>>
>>> Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
>>>
>>> Yep. Matt has right.
>>>
>>> 1.The clock speed is esential.
>>>
>>> 2. You will notice quite a long delay (5s or so) between plugging the 
>>> pic usb and the moment when OS recognize it on pc. This depends by your 
>>> computer speed and pic firmware contents. If pic clk is wrong, you will not 
>>> see any usb device. After it appears, check on printer/pheripheral for your 
>>> device but watch for any warnings there
>>>
>>> On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel >> wrote:
>>>
>>> Also use the code in 18f455_blink_hs_usb.jal
>>>
>>>  
>>>
>>> You are missing this one:
>>>
>>> OSCCON_SCS = 0  -- select primary oscillator
>>>
>>> On Friday, December 9, 2022 at 9:54:43 PM UTC-5 Matthew Schinkel wrote:
>>>
>>> Hi Hans, 
>>>
>>>  
>>>
>>> There must be an issue with your circuit. Do you have the correct clock 
>>> speed? Make sure a blink sample and normal serial port is working. Try 
>>> another PC. Windows should pick it up. 
>>>
>>>  
>>>
>>> Matt.
>>>
>>> On Friday, December 9, 2022 at 3:12:12 PM UTC-5 hans wrote:
>>>
>>> Hello,
>>> Thank you. I did what you recommended. Last Bee and tip from Vasile. 
>>> Same message from windows, not recognized and causing a malfunction. 
>>> Pff/
>>> regards
>>> Hans
>>>
>>> Op vrijdag 9 december 2022 om 18:43:24 UTC+1 schreef rob...@hotmail.com:
>>>
>>> Hi Hans,
>>>
>>>  
>>>
>>> As Vasile already mentioned Windows 10 will detect your device as a 
>>> serial (COM) port without the need of installing a separate driver.
>>>
>>>  
>>>
>>> Make sure you have the USB connections right. The signals are not 
>>> crossed like for USART, so D+ to D+ and D- to D-.
>>>
>>>  
>>>
>>> I attached a schematic diagram based on the PIC16F1455 for your 
>>> information and the USB connectors and what the signals

Re: [jallib] USB_help

ards
>>
>> Peter
>>
>>
>>
>> *Van:* jal...@googlegroups.com [mailto:jal...@googlegroups.com] *Namens 
>> *Matthew
>> Schinkel
>> *Verzonden:* zondag 11 december 2022 04:18
>> *Aan:* jallib 
>> *Onderwerp:* Re: [jallib] USB_help
>>
>>
>>
>> Hi Hans, what chip is it working on?
>>
>>
>>
>> Is anyone else able to test the 18f4455 blink usb sample?
>>
>> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>>
>> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't
>> work. Then I restarted Bert van Dam's old business and tried the same
>> program on it. that works as it should.
>> I have also tested ports D+ and D- (24 and 23) as inputs and those ports
>> work as well. I now doubt whether the PIC is broken or something else is
>> going on.
>> regards
>> Hans
>>
>> Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
>>
>> Hello champs,
>> I have reassembled everything and I can only conclude that the PIC itself
>> (has done some things before) is defective. Unfortunately, I no longer have
>> a PIC with USB, so I put it back in the fridge. I will have to look for
>> another one but the market is scarce.
>> Thanks again for your great responses.
>> regards
>> Hans
>>
>> Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
>>
>> Yep. Matt has right.
>>
>> 1.The clock speed is esential.
>>
>> 2. You will notice quite a long delay (5s or so) between plugging the pic
>> usb and the moment when OS recognize it on pc. This depends by your
>> computer speed and pic firmware contents. If pic clk is wrong, you will not
>> see any usb device. After it appears, check on printer/pheripheral for your
>> device but watch for any warnings there
>>
>> On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel > wrote:
>>
>> Also use the code in 18f455_blink_hs_usb.jal
>>
>>
>>
>> You are missing this one:
>>
>> OSCCON_SCS = 0  -- select primary oscillator
>>
>> On Friday, December 9, 2022 at 9:54:43 PM UTC-5 Matthew Schinkel wrote:
>>
>> Hi Hans,
>>
>>
>>
>> There must be an issue with your circuit. Do you have the correct clock
>> speed? Make sure a blink sample and normal serial port is working. Try
>> another PC. Windows should pick it up.
>>
>>
>>
>> Matt.
>>
>> On Friday, December 9, 2022 at 3:12:12 PM UTC-5 hans wrote:
>>
>> Hello,
>> Thank you. I did what you recommended. Last Bee and tip from Vasile. Same
>> message from windows, not recognized and causing a malfunction. Pff/
>> regards
>> Hans
>>
>> Op vrijdag 9 december 2022 om 18:43:24 UTC+1 schreef rob...@hotmail.com:
>>
>> Hi Hans,
>>
>>
>>
>> As Vasile already mentioned Windows 10 will detect your device as a
>> serial (COM) port without the need of installing a separate driver.
>>
>>
>>
>> Make sure you have the USB connections right. The signals are not crossed
>> like for USART, so D+ to D+ and D- to D-.
>>
>>
>>
>> I attached a schematic diagram based on the PIC16F1455 for your
>> information and the USB connectors and what the signals look like.
>>
>>
>>
>> Good luck!
>>
>>
>>
>> Kind regards,
>>
>>
>> Rob
>>
>>
>> --
>>
>> *Van:* jal...@googlegroups.com  namens
>> vsurducan 
>> *Verzonden:* vrijdag 9 december 2022 18:12
>> *Aan:* jal...@googlegroups.com 
>> *Onderwerp:* Re: [jallib] USB_help
>>
>>
>>
>> Hi Hans,
>>
>> for win10 you do not need any special driver, just a good terminal like
>> Teraterm.
>>
>> Download the last jal package, Rob did some modifications on USB driver,
>>
>> my suggestion is to use const USB_INTERRUPT_DRIVEN = TRUE
>>
>> The maximum speed is about 100kbps.
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Dec 9, 2022 at 5:42 PM hans  wrote:
>>
>> Hello,
>> I am trying to learn more about USB and have tried a sample program( ex
>> 18F2450)  (see attachment) I keep getting the remark that windows 10 does
>> not recognize the connection and cannot install the driver. What am I doing
>> wrong??
>> regards
>> Hans
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "jallib" group.
>> To unsubsc

Re: [jallib] USB_help

2022-12-16 Thread Rob CJ

Hi Hans,

Can you share the schematic diagram for the 16F1455? I assume you used the
standard sample program for the 16F1455.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: vrijdag 16 december 2022 14:20
Aan: jallib
Onderwerp: Re: [jallib] USB_help

Hey ,
I have now received the 18F4550 and the 16F1455 and have tried both with the
usb_serial samples. programming with PicKit_3, but in all cases I get a warning
on my PC (both on win10 and win7) that the USB is not recognized. The Vusb with
capacitor reads 3.3 volts and I have programmed both with and without LVP.
identical to my previous attempts.
Apparently USB is not allowed to me
Hans

Op woensdag 14 december 2022 om 14:19:16 UTC+1 schreef zet@gmail.com:

Hi Matt

I see your question 10-12 now: Wednesday 14-12

I am not at home for 2 days.

I can test. You hear as soon as possible.

Regards

Peter

Van: jal...@googlegroups.com [mailto:jal...@googlegroups.com] Namens Matthew
Schinkel
Verzonden: zondag 11 december 2022 04:18
Aan: jallib
Onderwerp: Re: [jallib] USB_help

Hi Hans, what chip is it working on?

Is anyone else able to test the 18f4455 blink usb sample?

On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:

Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. Then
I restarted Bert van Dam's old business and tried the same program on it. that
works as it should.
I have also tested ports D+ and D- (24 and 23) as inputs and those ports work
as well. I now doubt whether the PIC is broken or something else is going on.
regards
Hans

Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:

Hello champs,
I have reassembled everything and I can only conclude that the PIC itself (has
done some things before) is defective. Unfortunately, I no longer have a PIC
with USB, so I put it back in the fridge. I will have to look for another one
but the market is scarce.
Thanks again for your great responses.
regards
Hans

Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:

Yep. Matt has right.

1.The clock speed is esential.

2. You will notice quite a long delay (5s or so) between plugging the pic usb
and the moment when OS recognize it on pc. This depends by your computer speed
and pic firmware contents. If pic clk is wrong, you will not see any usb
device. After it appears, check on printer/pheripheral for your device but
watch for any warnings there

On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel namens vsurducan

Verzonden: vrijdag 9 december 2022 18:12
Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] USB_help

Hi Hans,

for win10 you do not need any special driver, just a good terminal like
Teraterm.

Download the last jal package, Rob did some modifications on USB driver,

my suggestion is to use const USB_INTERRUPT_DRIVEN = TRUE

The maximum speed is about 100kbps.

On Fri, Dec 9, 2022 at 5:42 PM hans wrote:

Hello,
I am trying to learn more about USB and have tried a sample program( ex
18F2450) (see attachment) I keep getting the remark that windows 10 does not
recognize the connection and cannot install the driver. What am I doing wrong??
regards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com?utm_medium=email_source=footer>.

To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com?utm_medium=email_source=footer>.

To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com?utm_medium=email_source=footer>.

To view thi

Re: [jallib] USB_help

Hey ,
I have now received the 18F4550 and the 16F1455 and have tried both with 
the usb_serial samples. programming with PicKit_3, but in all cases I get a 
warning on my PC (both on win10 and win7) that the USB is not recognized. 
The Vusb with capacitor reads 3.3 volts and I have programmed both with and 
without LVP. identical to my previous attempts.
Apparently USB is not allowed to me
Hans

Op woensdag 14 december 2022 om 14:19:16 UTC+1 schreef zet@gmail.com:

> Hi Matt
>
> I see your question 10-12 now: Wednesday 14-12
>
> I am not at home for 2 days.
>
> I can test. You hear as soon as possible.
>
>  
>
> Regards
>
> Peter
>
>  
>
> *Van:* jal...@googlegroups.com [mailto:jal...@googlegroups.com] *Namens 
> *Matthew 
> Schinkel
> *Verzonden:* zondag 11 december 2022 04:18
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
>
>  
>
> Hi Hans, what chip is it working on?
>
>  
>
> Is anyone else able to test the 18f4455 blink usb sample?
>
> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>
> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. 
> Then I restarted Bert van Dam's old business and tried the same program on 
> it. that works as it should.
> I have also tested ports D+ and D- (24 and 23) as inputs and those ports 
> work as well. I now doubt whether the PIC is broken or something else is 
> going on.
> regards
> Hans
>
> Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
>
> Hello champs,
> I have reassembled everything and I can only conclude that the PIC itself 
> (has done some things before) is defective. Unfortunately, I no longer have 
> a PIC with USB, so I put it back in the fridge. I will have to look for 
> another one but the market is scarce.
> Thanks again for your great responses.
> regards
> Hans
>
> Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
>
> Yep. Matt has right.
>
> 1.The clock speed is esential.
>
> 2. You will notice quite a long delay (5s or so) between plugging the pic 
> usb and the moment when OS recognize it on pc. This depends by your 
> computer speed and pic firmware contents. If pic clk is wrong, you will not 
> see any usb device. After it appears, check on printer/pheripheral for your 
> device but watch for any warnings there
>
> On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel 
> Also use the code in 18f455_blink_hs_usb.jal
>
>  
>
> You are missing this one:
>
> OSCCON_SCS = 0  -- select primary oscillator
>
> On Friday, December 9, 2022 at 9:54:43 PM UTC-5 Matthew Schinkel wrote:
>
> Hi Hans, 
>
>  
>
> There must be an issue with your circuit. Do you have the correct clock 
> speed? Make sure a blink sample and normal serial port is working. Try 
> another PC. Windows should pick it up. 
>
>  
>
> Matt.
>
> On Friday, December 9, 2022 at 3:12:12 PM UTC-5 hans wrote:
>
> Hello,
> Thank you. I did what you recommended. Last Bee and tip from Vasile. Same 
> message from windows, not recognized and causing a malfunction. Pff/
> regards
> Hans
>
> Op vrijdag 9 december 2022 om 18:43:24 UTC+1 schreef rob...@hotmail.com:
>
> Hi Hans,
>
>  
>
> As Vasile already mentioned Windows 10 will detect your device as a serial 
> (COM) port without the need of installing a separate driver.
>
>  
>
> Make sure you have the USB connections right. The signals are not crossed 
> like for USART, so D+ to D+ and D- to D-.
>
>  
>
> I attached a schematic diagram based on the PIC16F1455 for your 
> information and the USB connectors and what the signals look like.
>
>  
>
> Good luck!
>
>  
>
> Kind regards,
>
>
> Rob
>
>  
> --
>
> *Van:* jal...@googlegroups.com  namens vsurducan 
> 
> *Verzonden:* vrijdag 9 december 2022 18:12
> *Aan:* jal...@googlegroups.com 
> *Onderwerp:* Re: [jallib] USB_help 
>
>  
>
> Hi Hans,
>
> for win10 you do not need any special driver, just a good terminal like 
> Teraterm.
>
> Download the last jal package, Rob did some modifications on USB driver, 
>
> my suggestion is to use const USB_INTERRUPT_DRIVEN = TRUE
>
> The maximum speed is about 100kbps.
>
>  
>
>  
>
>  
>
> On Fri, Dec 9, 2022 at 5:42 PM hans  wrote:
>
> Hello,
> I am trying to learn more about USB and have tried a sample program( ex 
> 18F2450)  (see attachment) I keep getting the remark that windows 10 does 
> not recognize the connection and cannot install the driver. What am I doing 
> wrong??
> regards
> Hans
>
> -- 
> You received this message because

RE: [jallib] USB_help

2022-12-14 Thread zet.weeh

Hi Matt

I see your question 10-12 now: Wednesday 14-12

I am not at home for 2 days.

I can test. You hear as soon as possible.

Regards

Peter

Van: jallib@googlegroups.com [mailto:jallib@googlegroups.com] Namens Matthew
Schinkel
Verzonden: zondag 11 december 2022 04:18
Aan: jallib
Onderwerp: Re: [jallib] USB_help

Hi Hans, what chip is it working on?

Is anyone else able to test the 18f4455 blink usb sample?

On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:

Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:

Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:

Yep. Matt has right.

1.The clock speed is esential.

On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel mailto:rob...@hotmail.com> :

Hi Hans,

As Vasile already mentioned Windows 10 will detect your device as a serial
(COM) port without the need of installing a separate driver.

Make sure you have the USB connections right. The signals are not crossed like
for USART, so D+ to D+ and D- to D-.

I attached a schematic diagram based on the PIC16F1455 for your information and
the USB connectors and what the signals look like.

Good luck!

Kind regards,

Rob

Van: jal...@googlegroups.com <mailto:jal...@googlegroups.com>
mailto:jal...@googlegroups.com> > namens vsurducan
mailto:vsur...@gmail.com> >
Verzonden: vrijdag 9 december 2022 18:12
Aan: jal...@googlegroups.com <mailto:jal...@googlegroups.com>
mailto:jal...@googlegroups.com> >
Onderwerp: Re: [jallib] USB_help

Hi Hans,

for win10 you do not need any special driver, just a good terminal like
Teraterm.

Download the last jal package, Rob did some modifications on USB driver,

my suggestion is to use const USB_INTERRUPT_DRIVEN = TRUE

The maximum speed is about 100kbps.

On Fri, Dec 9, 2022 at 5:42 PM hans mailto:hanz...@zeelandnet.nl> > wrote:

<https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com?utm_medium=email_source=footer>
.

To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com

<https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com?utm_medium=email_source=footer>
.

To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com

<https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com?utm_medium=email_source=footer>
.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To u

Re: [jallib] USB_help

Hi Kiste/Rob
I have two PCB's on which the PIC should work, both fail. It seems strong 
to me that both the xtal would not be good. All the things I try work with 
it. Unfortunately I only have one PIC18F4455
I have already ordered the 16F1455's.
greetings and thanks for your response
Hans

Op maandag 12 december 2022 om 07:39:47 UTC+1 schreef Kiste:

> Hi Hans,
>
> to be really sure, put something like this to the beginning of your 
> program:
>
> for 10 loop
>   LED=on
>   _usec_delay(100_000)
>   LED=off
>   _usec_delay(900_000)
> end loop
>
> Compare the flashes with a ticking clock: If there's one flash per second, 
> you've checked that
>
> 1. the PIC runs at all
> 2. the PIC runs at the speed the compiler assumes it to
> 3. the crystal is fine
>
> Like every other thing in the world, also crystals may break. But, if they 
> break, they're usually not 1% or 2% off of their rated frequency, but 50% 
> or more. You would see such a wrong frequency with this test.
>
> If, however, the crystal oscillator is loaded with wrong capacitors (say, 
> 2x100pF instead of 2x27pF), there might result a frequency which "looks" 
> right, but is out of spec for USB, which requires very small tolerances.
>
> Greets,
> Kiste
>
> Am Montag, 12. Dezember 2022, 07:15:49 MEZ hat Rob CJ  
> Folgendes geschrieben: 
>
>
> Hi Hans,
>
> If it is printed on the crystal you may assume that it is correct. 
>
> Met vriendelijke groet,
> Rob Jansen 
> --
> *From:* jal...@googlegroups.com  on behalf of 
> hans 
> *Sent:* Sunday, December 11, 2022 7:56:54 PM
> *To:* jallib 
> *Subject:* Re: [jallib] USB_help 
>  
> Hi Rob, 
> on the xtal is written 20.000, how can i know if this is true?
> regards
> Hans
>
> Op zondag 11 december 2022 om 16:51:08 UTC+1 schreef rob...@hotmail.com:
>
> Hi Hans,
>
> The USB driver should work for the 18F.
>
> It is important that the PIC runs at 48 MHz for the USB to work correctly. 
> In the sample program that you use, you have to connect a 20 MHz crystal in 
> order to let the PIC run at 48 MHz.
>
> Are you using a 20 MHz crystal?
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 12:37
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
> Hello Rob,
> That's right. Turned off LVP and the blinkers work. The USB does not work. 
> I will order a pair of 16F1455 in hopes that will work.
> regards
> Hans
>
> Op zondag 11 december 2022 om 10:44:21 UTC+1 schreef rob...@hotmail.com:
>
> Hi Hans,
>
> One of the differences is the use of Low Voltage Programming (LVP).
>
> I think the Wisp does not support that, does it? Did you try programming 
> it with a PICKit2 or PICKit3?
>
> A few years ago all blink samples changed to LVP for those devices that 
> support this.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 10:26
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
> Blink a led tested with an old sample, this works : 
>
> -- --
> -- Title: Blink-a-led of the Microchip pic18f4455
> --
> -- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
> --
> -- Adapted-by:
> --
> -- Revision: $Revision: 2902 $
> --
> -- Compiler: 2.4o
> --
> -- This file is part of jallib  (http://jallib.googlecode.com)
> -- Released under the BSD license (
> http://www.opensource.org/licenses/bsd-license.php)
> --
> -- Description:
> -- Sample blink-a-led program for Microchip PIC18f4455.
> --
> -- Sources:
> --
> -- Notes:
> --  - File creation date/time: 7 Dec 2011 14:14:17.
> --
> -- --
> --
> include 18f4455-- target PICmicro
> --
> -- This program assumes that a 20 MHz resonator or crystal
> -- is connected to pins OSC1 and OSC2.
> -- (unspecified configuration bits may cause a different frequency!)
> pragma target clock 20_000_000 -- oscillator frequency
> -- configuration memory settings (fuses)
> pragma target OSC  HS   -- HS crystal or resonator
> pragma target PLLDIV   P1   -- no divide
> pragma target CPUDIV   P1   -- no Fosc divisor
> --pragma target WDT  disabled -- no watchdog
> pragma target XINSTdisabled -- not supported by JalV2
> pragma target DEBUGdisabled -- no debugging
>

Re: [jallib] USB_help

2022-12-11 Thread 'Oliver Seitz' via jallib

 Hi Hans,
to be really sure, put something like this to the beginning of your program:
for 10 loop  LED=on  _usec_delay(100_000)  LED=off  _usec_delay(900_000)end loop
Compare the flashes with a ticking clock: If there's one flash per second, 
you've checked that
1. the PIC runs at all2. the PIC runs at the speed the compiler assumes it to3. 
the crystal is fine
Like every other thing in the world, also crystals may break. But, if they 
break, they're usually not 1% or 2% off of their rated frequency, but 50% or 
more. You would see such a wrong frequency with this test.
If, however, the crystal oscillator is loaded with wrong capacitors (say, 
2x100pF instead of 2x27pF), there might result a frequency which "looks" right, 
but is out of spec for USB, which requires very small tolerances.
Greets,Kiste
Am Montag, 12. Dezember 2022, 07:15:49 MEZ hat Rob CJ  
Folgendes geschrieben:  
 
 Hi Hans,
If it is printed on the crystal you may assume that it is correct. 
Met vriendelijke groet,Rob Jansen From: jallib@googlegroups.com 
 on behalf of hans 
Sent: Sunday, December 11, 2022 7:56:54 PM
To: jallib 
Subject: Re: [jallib] USB_help Hi Rob,on the xtal is written 20.000, how can i 
know if this is true?regardsHans

Op zondag 11 december 2022 om 16:51:08 UTC+1 schreef rob...@hotmail.com:

Hi Hans,
The USB driver should work for the 18F.
It is important that the PIC runs at 48 MHz for the USB to work correctly. In 
the sample program that you use, you have to connect a 20 MHz crystal in order 
to let the PIC run at 48 MHz.
Are you using a 20 MHz crystal?
Kind regards,
Rob
Van:jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 12:37
Aan: jallib 
Onderwerp: Re: [jallib] USB_helpHello Rob,
That's right. Turned off LVP and the blinkers work. The USB does not work. I 
will order a pair of 16F1455 in hopes that will work.
regards
Hans

Op zondag 11 december 2022 om 10:44:21 UTC+1 schreef rob...@hotmail.com:

Hi Hans,
One of the differences is the use of Low Voltage Programming (LVP).
I think the Wisp does not support that, does it? Did you try programming it 
with a PICKit2 or PICKit3?
A few years ago all blink samples changed to LVP for those devices that support 
this.
Kind regards,
Rob
Van:jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:26
Aan: jallib 
Onderwerp: Re: [jallib] USB_helpBlink a led tested with an old sample, this 
works :
-- --
-- Title: Blink-a-led of the Microchip pic18f4455
--
-- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
--
-- Adapted-by:
--
-- Revision: $Revision: 2902 $
--
-- Compiler: 2.4o
--
-- This file is part of jallib  (http://jallib.googlecode.com)
-- Released under the BSD license 
(http://www.opensource.org/licenses/bsd-license.php)
--
-- Description:
-- Sample blink-a-led program for Microchip PIC18f4455.
--
-- Sources:
--
-- Notes:
--  - File creation date/time: 7 Dec 2011 14:14:17.
--
-- --
--
include 18f4455                    -- target PICmicro
--
-- This program assumes that a 20 MHz resonator or crystal
-- is connected to pins OSC1 and OSC2.
-- (unspecified configuration bits may cause a different frequency!)
pragma target clock 20_000_000     -- oscillator frequency
-- configuration memory settings (fuses)
pragma target OSC      HS               -- HS crystal or resonator
pragma target PLLDIV   P1           -- no divide
pragma target CPUDIV   P1           -- no Fosc divisor
--pragma target WDT      disabled     -- no watchdog
pragma target XINST    disabled     -- not supported by JalV2
pragma target DEBUG    disabled     -- no debugging
pragma target LVP      disabled     -- no Low Voltage Programming
pragma target MCLR     external     -- reset externally
-- These configuration bit settings are only a selection, sufficient for
-- this program, but other programs may need more or different settings.
--
enable_digital_io()                -- make all pins digital I/O
--
-- Specify the pin to which the LED is connected.
-- A low current (2 mA) led with 2.2K series resistor is recommended
-- since not all pins may be able to drive an ordinary 20mA led.
alias   led      is pin_A0
pin_A0_direction =  output
--
forever loop
   led = on
   _usec_delay(250_000)
   led = off
   _usec_delay(250_000)
end loop
--

Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:

Hi Hans,
I am not at home the coming week so I am not able to test but I assume it 
should work since blink samples are at least tested once when a new device is 
added.
Maybe somebody is able to help you, otherwise I can test it next weekend on a 
PIC18F4550 (same family).
Kind regards,
Rob
Van:jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:07
Aan: jallib 
Onderwerp: Re: [jallib] USB_help Hi Matt,
I first tested with the 18F4455. It does not work with both the sample 
18F4455-bl

Re: [jallib] USB_help

Hi Hans,

If it is printed on the crystal you may assume that it is correct.

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of hans 

Sent: Sunday, December 11, 2022 7:56:54 PM
To: jallib 
Subject: Re: [jallib] USB_help

Hi Rob,
on the xtal is written 20.000, how can i know if this is true?
regards
Hans

Op zondag 11 december 2022 om 16:51:08 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

The USB driver should work for the 18F.

It is important that the PIC runs at 48 MHz for the USB to work correctly. In 
the sample program that you use, you have to connect a 20 MHz crystal in order 
to let the PIC run at 48 MHz.

Are you using a 20 MHz crystal?

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 12:37

Aan: jallib 
Onderwerp: Re: [jallib] USB_help
Hello Rob,
That's right. Turned off LVP and the blinkers work. The USB does not work. I 
will order a pair of 16F1455 in hopes that will work.
regards
Hans

Op zondag 11 december 2022 om 10:44:21 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

One of the differences is the use of Low Voltage Programming (LVP).

I think the Wisp does not support that, does it? Did you try programming it 
with a PICKit2 or PICKit3?

A few years ago all blink samples changed to LVP for those devices that support 
this.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:26

Aan: jallib 
Onderwerp: Re: [jallib] USB_help
Blink a led tested with an old sample, this works :

-- --
-- Title: Blink-a-led of the Microchip pic18f4455
--
-- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
--
-- Adapted-by:
--
-- Revision: $Revision: 2902 $
--
-- Compiler: 2.4o
--
-- This file is part of jallib  (http://jallib.googlecode.com)
-- Released under the BSD license 
(http://www.opensource.org/licenses/bsd-license.php)
--
-- Description:
-- Sample blink-a-led program for Microchip PIC18f4455.
--
-- Sources:
--
-- Notes:
--  - File creation date/time: 7 Dec 2011 14:14:17.
--
-- --
--
include 18f4455-- target PICmicro
--
-- This program assumes that a 20 MHz resonator or crystal
-- is connected to pins OSC1 and OSC2.
-- (unspecified configuration bits may cause a different frequency!)
pragma target clock 20_000_000 -- oscillator frequency
-- configuration memory settings (fuses)
pragma target OSC  HS   -- HS crystal or resonator
pragma target PLLDIV   P1   -- no divide
pragma target CPUDIV   P1   -- no Fosc divisor
--pragma target WDT  disabled -- no watchdog
pragma target XINSTdisabled -- not supported by JalV2
pragma target DEBUGdisabled -- no debugging
pragma target LVP  disabled -- no Low Voltage Programming
pragma target MCLR external -- reset externally
-- These configuration bit settings are only a selection, sufficient for
-- this program, but other programs may need more or different settings.
--
enable_digital_io()-- make all pins digital I/O
--
-- Specify the pin to which the LED is connected.
-- A low current (2 mA) led with 2.2K series resistor is recommended
-- since not all pins may be able to drive an ordinary 20mA led.
alias   led  is pin_A0
pin_A0_direction =  output
--
forever loop
   led = on
   _usec_delay(250_000)
   led = off
   _usec_delay(250_000)
end loop
--

Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

I am not at home the coming week so I am not able to test but I assume it 
should work since blink samples are at least tested once when a new device is 
added.

Maybe somebody is able to help you, otherwise I can test it next weekend on a 
PIC18F4550 (same family).

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:07
Aan: jallib 
Onderwerp: Re: [jallib] USB_help

Hi Matt,
I first tested with the 18F4455. It does not work with both the sample 
18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old Picdev2, 
I did without changing the pcb.
Now I have exchanged the pic for the 18F4520 and the blink does not work there 
either with the 18F4520_blink_hs.jal.
  I can't test that in the Bert environment because  this pic was not included 
in his package.
I do use the wisp for programming.
Hans
Bert's program:
--JAL2.4j
include 18f4455_bert
--
pin_A0_direction = OUTPUT-- for led
--
forever loop
   pin_A0= ON
   _usec_delay(100_000)
   pin_A0 = OFF
   _usec_delay(400_000)
end loop
-- main loop
Op zondag 11 december 2022 om 04:17:43 UTC+1 schreef mattsc...@hotmail.com:
Hi Hans, what chip is it working on?

Is anyone else able to test the 18f4455 blink usb sample?

On Saturday, December 10

Re: [jallib] USB_help

Hi Rob,
on the xtal is written 20.000, how can i know if this is true?
regards
Hans

Op zondag 11 december 2022 om 16:51:08 UTC+1 schreef rob...@hotmail.com:

> Hi Hans,
>
> The USB driver should work for the 18F.
>
> It is important that the PIC runs at 48 MHz for the USB to work correctly. 
> In the sample program that you use, you have to connect a 20 MHz crystal in 
> order to let the PIC run at 48 MHz.
>
> Are you using a 20 MHz crystal?
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 12:37
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
> Hello Rob,
> That's right. Turned off LVP and the blinkers work. The USB does not work. 
> I will order a pair of 16F1455 in hopes that will work.
> regards
> Hans
>
> Op zondag 11 december 2022 om 10:44:21 UTC+1 schreef rob...@hotmail.com:
>
> Hi Hans,
>
> One of the differences is the use of Low Voltage Programming (LVP).
>
> I think the Wisp does not support that, does it? Did you try programming 
> it with a PICKit2 or PICKit3?
>
> A few years ago all blink samples changed to LVP for those devices that 
> support this.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 10:26
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
> Blink a led tested with an old sample, this works : 
>
> -- --
> -- Title: Blink-a-led of the Microchip pic18f4455
> --
> -- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
> --
> -- Adapted-by:
> --
> -- Revision: $Revision: 2902 $
> --
> -- Compiler: 2.4o
> --
> -- This file is part of jallib  (http://jallib.googlecode.com)
> -- Released under the BSD license (
> http://www.opensource.org/licenses/bsd-license.php)
> --
> -- Description:
> -- Sample blink-a-led program for Microchip PIC18f4455.
> --
> -- Sources:
> --
> -- Notes:
> --  - File creation date/time: 7 Dec 2011 14:14:17.
> --
> -- --
> --
> include 18f4455-- target PICmicro
> --
> -- This program assumes that a 20 MHz resonator or crystal
> -- is connected to pins OSC1 and OSC2.
> -- (unspecified configuration bits may cause a different frequency!)
> pragma target clock 20_000_000 -- oscillator frequency
> -- configuration memory settings (fuses)
> pragma target OSC  HS   -- HS crystal or resonator
> pragma target PLLDIV   P1   -- no divide
> pragma target CPUDIV   P1   -- no Fosc divisor
> --pragma target WDT  disabled -- no watchdog
> pragma target XINSTdisabled -- not supported by JalV2
> pragma target DEBUGdisabled -- no debugging
> pragma target LVP  disabled -- no Low Voltage Programming
> pragma target MCLR external -- reset externally
> -- These configuration bit settings are only a selection, sufficient for
> -- this program, but other programs may need more or different settings.
> --
> enable_digital_io()-- make all pins digital I/O
> --
> -- Specify the pin to which the LED is connected.
> -- A low current (2 mA) led with 2.2K series resistor is recommended
> -- since not all pins may be able to drive an ordinary 20mA led.
> alias   led  is pin_A0
> pin_A0_direction =  output
> --
> forever loop
>led = on
>_usec_delay(250_000)
>led = off
>_usec_delay(250_000)
> end loop
> --
>
> Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:
>
> Hi Hans,
>
> I am not at home the coming week so I am not able to test but I assume it 
> should work since blink samples are at least tested once when a new device 
> is added.
>
> Maybe somebody is able to help you, otherwise I can test it next weekend 
> on a PIC18F4550 (same family).
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 10:07
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help 
>  
> Hi Matt,
> I first tested with the 18F4455. It does not work with both the sample 
> 18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old 
> Picdev2, I did without changing the pcb.
> Now I have exchanged the pic for the 18F4520 and the blink does not work 
> there either with the 18F4520_blink_hs.jal.
>   I can't test that in the Bert env

Re: [jallib] USB_help

Hi Hans,

The USB driver should work for the 18F.

It is important that the PIC runs at 48 MHz for the USB to work correctly. In 
the sample program that you use, you have to connect a 20 MHz crystal in order 
to let the PIC run at 48 MHz.

Are you using a 20 MHz crystal?

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 12:37
Aan: jallib 
Onderwerp: Re: [jallib] USB_help

Hello Rob,
That's right. Turned off LVP and the blinkers work. The USB does not work. I 
will order a pair of 16F1455 in hopes that will work.
regards
Hans

Op zondag 11 december 2022 om 10:44:21 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

One of the differences is the use of Low Voltage Programming (LVP).

I think the Wisp does not support that, does it? Did you try programming it 
with a PICKit2 or PICKit3?

A few years ago all blink samples changed to LVP for those devices that support 
this.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:26

Aan: jallib 
Onderwerp: Re: [jallib] USB_help
Blink a led tested with an old sample, this works :

-- --
-- Title: Blink-a-led of the Microchip pic18f4455
--
-- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
--
-- Adapted-by:
--
-- Revision: $Revision: 2902 $
--
-- Compiler: 2.4o
--
-- This file is part of jallib  (http://jallib.googlecode.com)
-- Released under the BSD license 
(http://www.opensource.org/licenses/bsd-license.php)
--
-- Description:
-- Sample blink-a-led program for Microchip PIC18f4455.
--
-- Sources:
--
-- Notes:
--  - File creation date/time: 7 Dec 2011 14:14:17.
--
-- --
--
include 18f4455-- target PICmicro
--
-- This program assumes that a 20 MHz resonator or crystal
-- is connected to pins OSC1 and OSC2.
-- (unspecified configuration bits may cause a different frequency!)
pragma target clock 20_000_000 -- oscillator frequency
-- configuration memory settings (fuses)
pragma target OSC  HS   -- HS crystal or resonator
pragma target PLLDIV   P1   -- no divide
pragma target CPUDIV   P1   -- no Fosc divisor
--pragma target WDT  disabled -- no watchdog
pragma target XINSTdisabled -- not supported by JalV2
pragma target DEBUGdisabled -- no debugging
pragma target LVP  disabled -- no Low Voltage Programming
pragma target MCLR external -- reset externally
-- These configuration bit settings are only a selection, sufficient for
-- this program, but other programs may need more or different settings.
--
enable_digital_io()-- make all pins digital I/O
--
-- Specify the pin to which the LED is connected.
-- A low current (2 mA) led with 2.2K series resistor is recommended
-- since not all pins may be able to drive an ordinary 20mA led.
alias   led  is pin_A0
pin_A0_direction =  output
--
forever loop
   led = on
   _usec_delay(250_000)
   led = off
   _usec_delay(250_000)
end loop
--

Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

I am not at home the coming week so I am not able to test but I assume it 
should work since blink samples are at least tested once when a new device is 
added.

Maybe somebody is able to help you, otherwise I can test it next weekend on a 
PIC18F4550 (same family).

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:07
Aan: jallib 
Onderwerp: Re: [jallib] USB_help

Hi Matt,
I first tested with the 18F4455. It does not work with both the sample 
18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old Picdev2, 
I did without changing the pcb.
Now I have exchanged the pic for the 18F4520 and the blink does not work there 
either with the 18F4520_blink_hs.jal.
  I can't test that in the Bert environment because  this pic was not included 
in his package.
I do use the wisp for programming.
Hans
Bert's program:
--JAL2.4j
include 18f4455_bert
--
pin_A0_direction = OUTPUT-- for led
--
forever loop
   pin_A0= ON
   _usec_delay(100_000)
   pin_A0 = OFF
   _usec_delay(400_000)
end loop
-- main loop
Op zondag 11 december 2022 om 04:17:43 UTC+1 schreef mattsc...@hotmail.com:
Hi Hans, what chip is it working on?

Is anyone else able to test the 18f4455 blink usb sample?

On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. Then 
I restarted Bert van Dam's old business and tried the same program on it. that 
works as it should.
I have also tested ports D+ and D- (24 and 23) as inputs and those ports work 
as well. I now doubt whether the PIC is broken or something else is going on.
regards
Hans

Op zaterdag 10 december 2022 om 10:30:14 UTC+1

Re: [jallib] USB_help

Hello Rob,
That's right. Turned off LVP and the blinkers work. The USB does not work. 
I will order a pair of 16F1455 in hopes that will work.
regards
Hans

Op zondag 11 december 2022 om 10:44:21 UTC+1 schreef rob...@hotmail.com:

> Hi Hans,
>
> One of the differences is the use of Low Voltage Programming (LVP).
>
> I think the Wisp does not support that, does it? Did you try programming 
> it with a PICKit2 or PICKit3?
>
> A few years ago all blink samples changed to LVP for those devices that 
> support this.
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 10:26
>
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help
> Blink a led tested with an old sample, this works : 
>
> -- --
> -- Title: Blink-a-led of the Microchip pic18f4455
> --
> -- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
> --
> -- Adapted-by:
> --
> -- Revision: $Revision: 2902 $
> --
> -- Compiler: 2.4o
> --
> -- This file is part of jallib  (http://jallib.googlecode.com)
> -- Released under the BSD license (
> http://www.opensource.org/licenses/bsd-license.php)
> --
> -- Description:
> -- Sample blink-a-led program for Microchip PIC18f4455.
> --
> -- Sources:
> --
> -- Notes:
> --  - File creation date/time: 7 Dec 2011 14:14:17.
> --
> -- --
> --
> include 18f4455-- target PICmicro
> --
> -- This program assumes that a 20 MHz resonator or crystal
> -- is connected to pins OSC1 and OSC2.
> -- (unspecified configuration bits may cause a different frequency!)
> pragma target clock 20_000_000 -- oscillator frequency
> -- configuration memory settings (fuses)
> pragma target OSC  HS   -- HS crystal or resonator
> pragma target PLLDIV   P1   -- no divide
> pragma target CPUDIV   P1   -- no Fosc divisor
> --pragma target WDT  disabled -- no watchdog
> pragma target XINSTdisabled -- not supported by JalV2
> pragma target DEBUGdisabled -- no debugging
> pragma target LVP  disabled -- no Low Voltage Programming
> pragma target MCLR external -- reset externally
> -- These configuration bit settings are only a selection, sufficient for
> -- this program, but other programs may need more or different settings.
> --
> enable_digital_io()-- make all pins digital I/O
> --
> -- Specify the pin to which the LED is connected.
> -- A low current (2 mA) led with 2.2K series resistor is recommended
> -- since not all pins may be able to drive an ordinary 20mA led.
> alias   led  is pin_A0
> pin_A0_direction =  output
> --
> forever loop
>led = on
>_usec_delay(250_000)
>led = off
>_usec_delay(250_000)
> end loop
> --
>
> Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:
>
> Hi Hans,
>
> I am not at home the coming week so I am not able to test but I assume it 
> should work since blink samples are at least tested once when a new device 
> is added.
>
> Maybe somebody is able to help you, otherwise I can test it next weekend 
> on a PIC18F4550 (same family).
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 10:07
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help 
>  
> Hi Matt,
> I first tested with the 18F4455. It does not work with both the sample 
> 18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old 
> Picdev2, I did without changing the pcb.
> Now I have exchanged the pic for the 18F4520 and the blink does not work 
> there either with the 18F4520_blink_hs.jal.
>   I can't test that in the Bert environment because  this pic was not 
> included in his package.
> I do use the wisp for programming.
> Hans
> Bert's program: 
> --JAL2.4j
> include 18f4455_bert
> --
> pin_A0_direction = OUTPUT-- for led
> --
> forever loop
>pin_A0= ON
>_usec_delay(100_000)
>pin_A0 = OFF
>_usec_delay(400_000)
> end loop
> -- main loop
> Op zondag 11 december 2022 om 04:17:43 UTC+1 schreef mattsc...@hotmail.com
> :
>
> Hi Hans, what chip is it working on?
>
> Is anyone else able to test the 18f4455 blink usb sample?
>
> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>
> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. 
> Then I restarted Bert van Dam's

Re: [jallib] USB_help

Hi Hans,

One of the differences is the use of Low Voltage Programming (LVP).

I think the Wisp does not support that, does it? Did you try programming it 
with a PICKit2 or PICKit3?

A few years ago all blink samples changed to LVP for those devices that support 
this.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:26
Aan: jallib 
Onderwerp: Re: [jallib] USB_help

Blink a led tested with an old sample, this works :

-- --
-- Title: Blink-a-led of the Microchip pic18f4455
--
-- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
--
-- Adapted-by:
--
-- Revision: $Revision: 2902 $
--
-- Compiler: 2.4o
--
-- This file is part of jallib  (http://jallib.googlecode.com)
-- Released under the BSD license 
(http://www.opensource.org/licenses/bsd-license.php)
--
-- Description:
-- Sample blink-a-led program for Microchip PIC18f4455.
--
-- Sources:
--
-- Notes:
--  - File creation date/time: 7 Dec 2011 14:14:17.
--
-- --
--
include 18f4455-- target PICmicro
--
-- This program assumes that a 20 MHz resonator or crystal
-- is connected to pins OSC1 and OSC2.
-- (unspecified configuration bits may cause a different frequency!)
pragma target clock 20_000_000 -- oscillator frequency
-- configuration memory settings (fuses)
pragma target OSC  HS   -- HS crystal or resonator
pragma target PLLDIV   P1   -- no divide
pragma target CPUDIV   P1   -- no Fosc divisor
--pragma target WDT  disabled -- no watchdog
pragma target XINSTdisabled -- not supported by JalV2
pragma target DEBUGdisabled -- no debugging
pragma target LVP  disabled -- no Low Voltage Programming
pragma target MCLR external -- reset externally
-- These configuration bit settings are only a selection, sufficient for
-- this program, but other programs may need more or different settings.
--
enable_digital_io()-- make all pins digital I/O
--
-- Specify the pin to which the LED is connected.
-- A low current (2 mA) led with 2.2K series resistor is recommended
-- since not all pins may be able to drive an ordinary 20mA led.
alias   led  is pin_A0
pin_A0_direction =  output
--
forever loop
   led = on
   _usec_delay(250_000)
   led = off
   _usec_delay(250_000)
end loop
--

Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

I am not at home the coming week so I am not able to test but I assume it 
should work since blink samples are at least tested once when a new device is 
added.

Maybe somebody is able to help you, otherwise I can test it next weekend on a 
PIC18F4550 (same family).

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: zondag 11 december 2022 10:07
Aan: jallib 
Onderwerp: Re: [jallib] USB_help

Hi Matt,
I first tested with the 18F4455. It does not work with both the sample 
18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old Picdev2, 
I did without changing the pcb.
Now I have exchanged the pic for the 18F4520 and the blink does not work there 
either with the 18F4520_blink_hs.jal.
  I can't test that in the Bert environment because  this pic was not included 
in his package.
I do use the wisp for programming.
Hans
Bert's program:
--JAL2.4j
include 18f4455_bert
--
pin_A0_direction = OUTPUT-- for led
--
forever loop
   pin_A0= ON
   _usec_delay(100_000)
   pin_A0 = OFF
   _usec_delay(400_000)
end loop
-- main loop
Op zondag 11 december 2022 om 04:17:43 UTC+1 schreef mattsc...@hotmail.com:
Hi Hans, what chip is it working on?

Is anyone else able to test the 18f4455 blink usb sample?

On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. Then 
I restarted Bert van Dam's old business and tried the same program on it. that 
works as it should.
I have also tested ports D+ and D- (24 and 23) as inputs and those ports work 
as well. I now doubt whether the PIC is broken or something else is going on.
regards
Hans

Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
Hello champs,
I have reassembled everything and I can only conclude that the PIC itself (has 
done some things before) is defective. Unfortunately, I no longer have a PIC 
with USB, so I put it back in the fridge. I will have to look for another one 
but the market is scarce.
Thanks again for your great responses.
regards
Hans
Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
Yep. Matt has right.
1.The clock speed is esential.
2. You will notice quite a long delay (5s or so) between plugging the pic usb 
and the moment when OS recognize it on pc. This depends by your computer speed 
and pic firmware contents. If pic clk is wrong, you will not see any usb

Re: [jallib] USB_help

Blink a led tested with an old sample, this works :

-- --
-- Title: Blink-a-led of the Microchip pic18f4455
--
-- Author: Rob Hamerling, Copyright (c) 2008..2011, all rights reserved.
--
-- Adapted-by:
--
-- Revision: $Revision: 2902 $
--
-- Compiler: 2.4o
--
-- This file is part of jallib  (http://jallib.googlecode.com)
-- Released under the BSD license 
(http://www.opensource.org/licenses/bsd-license.php)
--
-- Description:
-- Sample blink-a-led program for Microchip PIC18f4455.
--
-- Sources:
--
-- Notes:
--  - File creation date/time: 7 Dec 2011 14:14:17.
--
-- --
--
include 18f4455-- target PICmicro
--
-- This program assumes that a 20 MHz resonator or crystal
-- is connected to pins OSC1 and OSC2.
-- (unspecified configuration bits may cause a different frequency!)
pragma target clock 20_000_000 -- oscillator frequency
-- configuration memory settings (fuses)
pragma target OSC  HS   -- HS crystal or resonator
pragma target PLLDIV   P1   -- no divide
pragma target CPUDIV   P1   -- no Fosc divisor
--pragma target WDT  disabled -- no watchdog
pragma target XINSTdisabled -- not supported by JalV2
pragma target DEBUGdisabled -- no debugging
pragma target LVP  disabled -- no Low Voltage Programming
pragma target MCLR external -- reset externally
-- These configuration bit settings are only a selection, sufficient for
-- this program, but other programs may need more or different settings.
--
enable_digital_io()-- make all pins digital I/O
--
-- Specify the pin to which the LED is connected.
-- A low current (2 mA) led with 2.2K series resistor is recommended
-- since not all pins may be able to drive an ordinary 20mA led.
alias   led  is pin_A0
pin_A0_direction =  output
--
forever loop
   led = on
   _usec_delay(250_000)
   led = off
   _usec_delay(250_000)
end loop
--

Op zondag 11 december 2022 om 10:20:59 UTC+1 schreef rob...@hotmail.com:

> Hi Hans,
>
> I am not at home the coming week so I am not able to test but I assume it 
> should work since blink samples are at least tested once when a new device 
> is added.
>
> Maybe somebody is able to help you, otherwise I can test it next weekend 
> on a PIC18F4550 (same family).
>
> Kind regards,
>
> Rob
>
> --
> *Van:* jal...@googlegroups.com  namens hans <
> hanz...@zeelandnet.nl>
> *Verzonden:* zondag 11 december 2022 10:07
> *Aan:* jallib 
> *Onderwerp:* Re: [jallib] USB_help 
>  
> Hi Matt,
> I first tested with the 18F4455. It does not work with both the sample 
> 18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old 
> Picdev2, I did without changing the pcb.
> Now I have exchanged the pic for the 18F4520 and the blink does not work 
> there either with the 18F4520_blink_hs.jal.
>   I can't test that in the Bert environment because  this pic was not 
> included in his package.
> I do use the wisp for programming.
> Hans
> Bert's program: 
> --JAL2.4j
> include 18f4455_bert
> --
> pin_A0_direction = OUTPUT-- for led
> --
> forever loop
>pin_A0= ON
>_usec_delay(100_000)
>pin_A0 = OFF
>_usec_delay(400_000)
> end loop
> -- main loop
> Op zondag 11 december 2022 om 04:17:43 UTC+1 schreef mattsc...@hotmail.com
> :
>
> Hi Hans, what chip is it working on?
>
> Is anyone else able to test the 18f4455 blink usb sample?
>
> On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
>
> Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. 
> Then I restarted Bert van Dam's old business and tried the same program on 
> it. that works as it should.
> I have also tested ports D+ and D- (24 and 23) as inputs and those ports 
> work as well. I now doubt whether the PIC is broken or something else is 
> going on.
> regards
> Hans
>
> Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
>
> Hello champs,
> I have reassembled everything and I can only conclude that the PIC itself 
> (has done some things before) is defective. Unfortunately, I no longer have 
> a PIC with USB, so I put it back in the fridge. I will have to look for 
> another one but the market is scarce.
> Thanks again for your great responses.
> regards
> Hans
> Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
>
> Yep. Matt has right.
> 1.The clock speed is esential.
> 2. You will notice quite a long delay (5s or so) between plugging the pic 
> usb and the moment when OS recognize it on pc. This depends by your 
> computer speed and pic firmware contents. If pic clk is wrong, you will not 
> see any usb device. Afte

Re: [jallib] USB_help

Hi Hans,

I am not at home the coming week so I am not able to test but I assume it
should work since blink samples are at least tested once when a new device is
added.

Maybe somebody is able to help you, otherwise I can test it next weekend on a
PIC18F4550 (same family).

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zondag 11 december 2022 10:07
Aan: jallib
Onderwerp: Re: [jallib] USB_help

Hi Matt,
I first tested with the 18F4455. It does not work with both the sample
18F4455-blink_hs.jal and the 18F4455_blink_hs_usb.jal. With Bert's old Picdev2,
I did without changing the pcb.
Now I have exchanged the pic for the 18F4520 and the blink does not work there
either with the 18F4520_blink_hs.jal.
I can't test that in the Bert environment because this pic was not included
in his package.
I do use the wisp for programming.
Hans
Bert's program:
--JAL2.4j
include 18f4455_bert
--
pin_A0_direction = OUTPUT-- for led
--
forever loop
pin_A0= ON
_usec_delay(100_000)
pin_A0 = OFF
_usec_delay(400_000)
end loop
-- main loop
Op zondag 11 december 2022 om 04:17:43 UTC+1 schreef mattsc...@hotmail.com:
Hi Hans, what chip is it working on?

Is anyone else able to test the 18f4455 blink usb sample?

On Saturday, December 10, 2022 at 1:18:39 PM UTC-5 hans wrote:
Hello, I tested the sample 18f4455 Blink_hs_usb.jal. This one didn't work. Then
I restarted Bert van Dam's old business and tried the same program on it. that
works as it should.
I have also tested ports D+ and D- (24 and 23) as inputs and those ports work
as well. I now doubt whether the PIC is broken or something else is going on.
regards
Hans

Op zaterdag 10 december 2022 om 10:30:14 UTC+1 schreef hans:
Hello champs,
I have reassembled everything and I can only conclude that the PIC itself (has
done some things before) is defective. Unfortunately, I no longer have a PIC
with USB, so I put it back in the fridge. I will have to look for another one
but the market is scarce.
Thanks again for your great responses.
regards
Hans
Op zaterdag 10 december 2022 om 06:18:17 UTC+1 schreef vasile:
Yep. Matt has right.
1.The clock speed is esential.
2. You will notice quite a long delay (5s or so) between plugging the pic usb
and the moment when OS recognize it on pc. This depends by your computer speed
and pic firmware contents. If pic clk is wrong, you will not see any usb
device. After it appears, check on printer/pheripheral for your device but
watch for any warnings there

On Sat 10 Dec 2022, 4:59 AM Matthew Schinkel namens vsurducan

Verzonden: vrijdag 9 december 2022 18:12
Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] USB_help

Hi Hans,
for win10 you do not need any special driver, just a good terminal like
Teraterm.
Download the last jal package, Rob did some modifications on USB driver,
my suggestion is to use const USB_INTERRUPT_DRIVEN = TRUE
The maximum speed is about 100kbps.

On Fri, Dec 9, 2022 at 5:42 PM hans wrote:
Hello,
I am trying to learn more about USB and have tried a sample program( ex
18F2450) (see attachment) I keep getting the remark that windows 10 does not
recognize the connection and cannot install the driver. What am I doing wrong??
regards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an em

Re: [jallib] USB_help

2022-12-11 Thread vsurducan

gt;>>>
>>>>>>> Hi Hans,
>>>>>>>
>>>>>>> There must be an issue with your circuit. Do you have the correct
>>>>>>> clock speed? Make sure a blink sample and normal serial port is working.
>>>>>>> Try another PC. Windows should pick it up.
>>>>>>>
>>>>>>> Matt.
>>>>>>>
>>>>>>> On Friday, December 9, 2022 at 3:12:12 PM UTC-5 hans wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>> Thank you. I did what you recommended. Last Bee and tip from
>>>>>>>> Vasile. Same message from windows, not recognized and causing a
>>>>>>>> malfunction. Pffffff/
>>>>>>>> regards
>>>>>>>> Hans
>>>>>>>>
>>>>>>>> Op vrijdag 9 december 2022 om 18:43:24 UTC+1 schreef
>>>>>>>> rob...@hotmail.com:
>>>>>>>>
>>>>>>>>> Hi Hans,
>>>>>>>>>
>>>>>>>>> As Vasile already mentioned Windows 10 will detect your device as
>>>>>>>>> a serial (COM) port without the need of installing a separate driver.
>>>>>>>>>
>>>>>>>>> Make sure you have the USB connections right. The signals are not
>>>>>>>>> crossed like for USART, so D+ to D+ and D- to D-.
>>>>>>>>>
>>>>>>>>> I attached a schematic diagram based on the PIC16F1455 for your
>>>>>>>>> information and the USB connectors and what the signals look like.
>>>>>>>>>
>>>>>>>>> Good luck!
>>>>>>>>>
>>>>>>>>> Kind regards,
>>>>>>>>>
>>>>>>>>> Rob
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Van:* jal...@googlegroups.com  namens
>>>>>>>>> vsurducan 
>>>>>>>>> *Verzonden:* vrijdag 9 december 2022 18:12
>>>>>>>>> *Aan:* jal...@googlegroups.com 
>>>>>>>>> *Onderwerp:* Re: [jallib] USB_help
>>>>>>>>>
>>>>>>>>> Hi Hans,
>>>>>>>>> for win10 you do not need any special driver, just a good terminal
>>>>>>>>> like Teraterm.
>>>>>>>>> Download the last jal package, Rob did some modifications on USB
>>>>>>>>> driver,
>>>>>>>>> my suggestion is to use const USB_INTERRUPT_DRIVEN = TRUE
>>>>>>>>> The maximum speed is about 100kbps.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Dec 9, 2022 at 5:42 PM hans  wrote:
>>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>> I am trying to learn more about USB and have tried a sample
>>>>>>>>> program( ex 18F2450)  (see attachment) I keep getting the remark that
>>>>>>>>> windows 10 does not recognize the connection and cannot install the 
>>>>>>>>> driver.
>>>>>>>>> What am I doing wrong??
>>>>>>>>> regards
>>>>>>>>> Hans
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "jallib" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to jallib+un...@googlegroups.com.
>>>>>>>>> To view this discussion on the web visit
>>>>>>>>> https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com
>>>>>>>>> <https://groups.google.com/d/msgid/jallib/c92e6cb2-a584-4b1b-a77f-d8bf943560b2n%40googlegroups.com?utm_medium=email_source=footer>
>>>>>>>>> .
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>>> Groups "jallib" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>>>> send an email to jallib+un...@googlegroups.com.
>>>>>>>>> To view this discussion on the web visit
>>>>>>>>> https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com
>>>>>>>>> <https://groups.google.com/d/msgid/jallib/CAM%2Bj4quO70sp3CP%2BezE5_6jDU%2BpsJ2D7-MAU9bzRm1U1RbmACA%40mail.gmail.com?utm_medium=email_source=footer>
>>>>>>>>> .
>>>>>>>>>
>>>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "jallib" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to jallib+un...@googlegroups.com.
>>>>>>
>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com
>>>>>> <https://groups.google.com/d/msgid/jallib/df1d95ac-2ed5-46e2-80c6-47021bf19395n%40googlegroups.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>>
>>>>> --
> You received this message because you are subscribed to the Google Groups
> "jallib" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jallib+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jallib/d6f2eb77-c5dc-4518-8560-fd45bf6a854fn%40googlegroups.com
> <https://groups.google.com/d/msgid/jallib/d6f2eb77-c5dc-4518-8560-fd45bf6a854fn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qv0Yj_XgzjmqdS1XH63O4AV8%3D3JegxmaGqx626KTEaa8A%40mail.gmail.com.

Re: [jallib] USB_help