PIC and AVR DIY development boards

[ATE]

Share ko lang ito:

http://kuya-tronics.blogspot.com/2009/05/diy-atmel-40-pin-avr-development-board.html

http://kuya-tronics.blogspot.com/2009/05/pic18f4550-usb-development-board.html

Magsstart na ako sa blogging, hehe. Pwede kaya akong yumaman dito?

[marcelino]

Pogi point for you kuya!!!

mwah!

[ATE]

salamat...
sa blog ko din ipopost yung mga projects at mga reviews ng mga tools na meron ako...
i-tatarget ko one post per week...

[marcelino]

salamat...
sa blog ko din ipopost yung mga projects at mga reviews ng mga tools na meron ako...
i-tatarget ko one post per week...

may mga USB PIC kasi ako dito... di ko pa nasisimulan aralin yan. nwei, thanks.

[ATE]

Ako naman puro demo pa lang nagagawa 
Lahat na ata ng demo sa PICDEM FS USB nagawa ko... pinakagusto ko yung sa mouse... kusang umiikot yung pointer... ang sarap gamitin para mang-asar ng ibang computer user.

Hirap humanap ng oras

[marcelino]

papano ba gumamit ng PIC FS USB?

halimbawa, gusto mo gumawa ng blinking LED, kahit isang pin lang. Papano ba?

ginawa ko din kasi yung ganyang kay kuya, pero naguguluhan ako ng mga files... heheh

nalagyan ko na ng bootloader, at na detect na ng PC ko. pero sunod nun, di ko na alam... heheh


help naman... kahit yung pinakasimpleng blinking led lamang.

salamat.

[marcelino]

eto nga pala yung version ko... pero pareho ding schematic.



mine is a PIC18F4450

[motion55]

In the PICDEM FS USB, there is button you press while pressing the reset button or powering up. AFAIK by default the button is connected to RB4. The PIC will enter the bootloader. This can be detected by the Windows PICDEM Demo program. From the demo program you can download the hex file to the PICDEM.

It is recommended to use the PIC USB software framework. You only have to modify a few files to suit your application.

[paranz]

eto nga pala yung version ko... pero pareho ding schematic.



mine is a PIC18F4450

astig na board! ganada point to you sis 

It is recommended to use the PIC USB software framework. You only have to modify a few files to suit your application.

agree madali lang talaga if using the framework, assuming you know what to modify. Kaya suggest ko lang to read also the usb appnote sa microchip

[ATE]

do ko masyadong kabisado kung pwede yung bootloader sa 18f4450. Sa pagkakalam ko, dalawa yung bootloader, may isang HID tapos yung isa MCHPFSUSB. Magkaiba sila ng user interface para sa loading ng files eh. yung gamit ko is yung default na bootloader ng PICDEM FS USB.

eto yung loader:


sabi sa loader: I-hold daw yung S2 tapos i-reset para makapasok sa bootloading mode. Pagkareset, pwede nang i-release ung S2. Tapos, may drop down menu sa Select PICDEM FS USB Board. Select yung board.
Kung reset lang yung ginawa, pwede lang sya magconnect sa demo mode

eto yung demo mode:



kapag nasa demo mode, pwede mo nang icontrol yung led sa board by toggling LED D4

[marcelino]

Thank you sir...

BTW, I got that chip from the sampling program of circuitcellar... sayang naman. dapat gimitin at pagtutunan. I made a simple board based on kuya's post. on good thing about kuya's post is that, it is based from the PIC FS USB demo board.

yes sir, i have already tried that...
I guess the switch on the left side is the switch you are referring. Ang ginawa ko, hold-press ko po yun, then I press the reset switch. It was detected...

I am actually confused of the required files from PIC USB framework... nakakalito po...
basta ang naiintindihan ko lang, yung user.c and user.h lamang daw ang babaguhin ko.

[marcelino]

astig na board! ganada point to you sis 


agree madali lang talaga if using the framework, assuming you know what to modify. Kaya suggest ko lang to read also the usb appnote sa microchip

thank you sister....

yan talga ang problem ko... di ko maintindihan kung papano ko gagamitin yung mga files... i can't even find them! heheh

humihingi lang ako actually ng konting guidance... heheh

[marcelino]

^kuya, nakarating na ako sa part na yan...

PIC18F4450 ay kapareho lang ng 18F4550. mas konti lang yung space.

[paranz]

sis marce, ganito gawin mo to test your first sample codes like "blinker" and usb communication.

1. download the usb framework sample code
2. open the CDC demo (and compile/build to check if ok ba ang project settings like compiler, etc.)
3. Open user.c and check the code to familiarize before modifying
4. There are blank functions to serve as sample exercises in user.c, like

Code: [Select]


void Exercise_03(void){
    /*
     * Write code in this function that reads data from USB and
     * toggles LED D4 when the data read equals ASCII character '1' (0x31)
     *
     * Useful functions:
     *  byte getsUSBUSART(char *buffer, byte len)   See cdc.c for details
     *  mLED_4_Toggle();
     *
     * Use input_buffer[] to store data read from USB.
     */
}


Modify the code completing the exercises code. There are about 5 sample exercises. If you don't know the answer, no worries check the folder

C:\MCHPFSUSB\fw\Cdc\user\solutions

for the answer. If you already know C, madali na lang yan.

5. Download to your board to test code, or simply use proteus  
6. Enjoy!

[ATE]

eto ung mga files ng driver, bootloader, saka demo tool na ginamit ko
http://depositfiles.com/files/r9jd18hw2
http://rapidshare.com/files/241480912/pic_fs_usb_bootloader_hex__demo_tool__and_driver.rar

dami kasing files kaya, nilagay ko na lang dito yung hex, driver, saka tool para sa mga gustong gumawa.

[ATE]

I am actually confused of the required files from PIC USB framework... nakakalito po...
basta ang naiintindihan ko lang, yung user.c and user.h lamang daw ang babaguhin ko.

Ako rin nalito, nung dinownload ko yung latest version ng framework.

[ATE]

sis marce, ganito gawin mo to test your first sample codes like "blinker" and usb communication.

1. download the usb framework sample code
2. open the CDC demo (and compile/build to check if ok ba ang project settings like compiler, etc.)
3. Open user.c and check the code to familiarize before modifying
4. There are blank functions to serve as sample exercises in user.c, like

Code: [Select]


void Exercise_03(void){
    /*
     * Write code in this function that reads data from USB and
     * toggles LED D4 when the data read equals ASCII character '1' (0x31)
     *
     * Useful functions:
     *  byte getsUSBUSART(char *buffer, byte len)   See cdc.c for details
     *  mLED_4_Toggle();
     *
     * Use input_buffer[] to store data read from USB.
     */
}


Modify the code completing the exercises code. There are about 5 sample exercises. If you don't know the answer, no worries check the folder

for the answer. If you already know C, madali na lang yan.

5. Download to your board to test code, or simply use proteus  
6. Enjoy!

itatry ko din to... mukhang meron na kaming tutor ni marce dito ah.

[marcelino]

alam ko na... tama ka kuya!

lahat ng mga tutorials sa net, ay iba pa ang structure ng mga folders...

I am using MCHPFSUSB v2.2... eto na ang folder structure nya..



sige... pagtuunanko na muna ng pansin to...

KUYA, try ko yan mamaya kapag di ko to nakuha. heheh

[ATE]

alam ko na... tama ka kuya!

lahat ng mga tutorials sa net, ay iba pa ang structure ng mga folders...

I am using MCHPFSUSB v2.2... eto na ang folder structure nya..



sige... pagtuunanko na muna ng pansin to...

KUYA, try ko yan mamaya kapag di ko to nakuha. heheh

tinry ko yung v2.2, lahat ata ng bootloader dun ginamit ko pero, ayaw madetect... so ginamit ko v1.2, kasi madaling hanapin yung hex, driver, saka tool.. pero sa mga latest version, daming demo na pwedeng pag-aralan...

[motion55]

I think the PIC18F4450 should work. The only difference is the size of the program memory. You can change the linker script file to "rm18f4550.lkr" to define areas in memory to instruct the linker how to put program and data,

Assuming you are using USB framework 1.2 because I am familiar with that and not with version 2 and up:

Aside from the user.c and user.h, you can change io.cfg to redefine I/O locations to suit your hardware.

You can also modify "usbdsc.c" to change the VID/PID so that Windows will differentiate your device from the PICDEM. I would recommend to use the same VID (Microchip's 0x4D8) and just change to product ID. You have to patch the driver's inf file to reflect the changes. The descriptor string is likewise found in the "usbdsc.c".

I took a glance at framework version 2 and I think it is a cleaner framework.