> Hi Rafael > > What kind of help do you need? > I'm using Shane's bootloader, slightly modified to suite my needs as far > as the CONFIG bits are concerned. I wrote my own downloader program for > OS/2, and the combination works OK. > With the type 'A'-PICs (16F87xA) and the special bootloader for these, > the hex-file must have a multiple of 4 code-words (insert NOPs if > needed). I had similar problems as you report when I wasn't aware of > this requirement. Well, I need some help to put it to work: some tips of what can be done, as you just gave me. With your hint about the 'A' PICs, which was great, i made a different try: I got a non A 16F877 and wrote the bootloader in it. It worked! I can now use the bootloader to send inhx32 hex files either from Windows or Linux. But there's one strange error in both Linux and Windows: - After uploading the code to the PIC, the bootloader activates the user code that starts running perfectly. All OK util now. - But if I reset the PIC, sometimes the user code runs, but most times it does not run. That's very strange...when i say sometimes the user code runs, i mean that......it's really hard to this "sometime" happen. As i need to program via bootloader botth 16F877A and 16F877 this problem is the first that i want help to solve. The second problem is the one i reported in the last email. I know that A pics have different flash writing procedures, but this should be concerned to the pic's firmware and not pc software. Finally the Windows Donwnloader works, so why does the Linux Downloader does not if it sends the same serial data that Windows sends. And for last: each time the Linux downloader sends a WRITE flag, the first two bytes are correctly written, but the others not. So the program memory has 2 instructions....2 instructions....nothing. Everty time a WRITE is sent 2 instructions are written... Thanks. Rafael -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body