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 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 [email protected]: > 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:* [email protected] <[email protected]> namens hans < > [email protected]> > *Verzonden:* zondag 11 december 2022 10:07 > *Aan:* jallib <[email protected]> > *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 [email protected] > : > > 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 <[email protected] 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. Pffffff/ > regards > Hans > > Op vrijdag 9 december 2022 om 18:43:24 UTC+1 schreef [email protected]: > > 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:* [email protected] <[email protected]> namens vsurducan > <[email protected]> > *Verzonden:* vrijdag 9 december 2022 18:12 > *Aan:* [email protected] <[email protected]> > *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 <[email protected]> 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 [email protected]. > 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&utm_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 [email protected]. > 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&utm_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 [email protected]. > > 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&utm_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 [email protected]. > 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&utm_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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/30b9e9b5-47be-4a79-84b0-bb6e3d7f8af2n%40googlegroups.com.
