gnupic: Thread: Re: [gnupic] Re: MCHPFSUSB AN950, AN956, ...

Hi  list.

This is what I get, trying to compile the code:

Easys-Mac:~/Prog/PIC/usb/MCHPFSUSB sdcc/fw/Cdc easyb$ make
sdcc -mpic16 -p18f2550 -I . -c -c system/usb/usb9/usb9.c -o system/ 
usb/usb9/usb9.o
Processor: 18f2550
gen.c:10532: failed assertion `IS_DATA_PTR(operandType(left))'
Caught signal 6: SIGABRT
make: *** [system/usb/usb9/usb9.o] Error 1

My sdcc version:

SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/ 
hc08 2.5.4 #1142 (Nov  2 2005) (UNIX)

Anybody?

Cheers,
Ezra.

Anfang der weitergeleiteten E-Mail:

> Von: ####@####.####
> Datum: 7. November 2005 11:34:19 GMT+01:00
> An: "GNUPIC List" ####@####.####
> Betreff: [gnupic] Re: MCHPFSUSB  AN950, AN956, ...
> Antwort an: ####@####.####
>
> Thanx for sharing Julian
>
> For everybody who's interested, I uploaded it to my site:
>
> http://electro.easyb.ch/files/MCHPFSUSB.tgz
>
> Although when I tried to build it the other day, it failed. Gota  
> have a
> closer look as soon as I have time.
>
> BTW, I ordered USB connectors, so I'm soon ready to test the
> functionality.
>
> Cheers,
> Ezra.
> ---------Nachricht integriert----------
>> Date: Sun, 6 Nov 2005 13:42:02 -0800
>> From: "julian green" ####@####.####
>> Reply-To: "julian green" ####@####.####
>> To: ####@####.####
>> Subject: MCHPFSUSB  AN950, AN956, ...
>>
>> Here is the tar file of the MCHPFSUSB code -
>> microchips applicaion note for implementing a RS232
>> device over USB.  I am sorry I have no idea if the
>> code works as I do not have a programmer yet.
>>
>> Untar the file then:
>>
>>  cd MCHPFSUSB/fw/Cdc
>>  make
>>
>> This is the version of sdcc I have - I had to compile
>> from source.
>>
>> [viper1@joshua Cdc]$ sdcc -v
>> SDCC :
>> mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08
>> 2.5.3 #1111 (Sep 19 2005) (UNIX)
>>
>> (sent from my non-work email account)
>>
>> Julian
>>
>>
>> 	
>> 		
>> __________________________________
>> Yahoo! Mail - PC Magazine Editors' Choice 2005
>> http://mail.yahoo.com UID 4020
> ---------Ende ursprüngliche Nachricht----------
> ----
> sunrise ADSL: gratis und so sicher wie noch nie
> http://www.sunrise.ch/home/proint/proint_ads-2.htm
> ----
> sunrise ADSL: Gratuit et plus sûr que jamais!
> http://www.sunrise.ch/fr/home/proint/proint_ads-2.htm
> ----
> sunrise ADSL: Gratis e sicuro come non mai!
> http://www.sunrise.ch/it/home/proint/proint_ads-2.htm
> ----
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

The same error occurs here under Windows SDCC.

Regards,
Xiaofan

xiaofan@PC-386 /c/software/sdcc/MCHPFSUSB/fw/Cdc
$ sdcc -v
SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/
xa51/ds400/hc08 2.5.4 #1138 (Oct 31 2005) (MINGW32)

xiaofan@PC-386 /c/software/sdcc/MCHPFSUSB/fw/Cdc
$ make
sdcc -mpic16 -p18f2550 -I . -c -c system/usb/usbdrv/usbdrv.c -o 
system/usb/usbdrv/usbdrv.o
Processor: 18f2550
sdcc -mpic16 -p18f2550 -I . -c -c system/usb/usbmmap.c -o 
system/usb/usbmmap.o
Processor: 18f2550
sdcc -mpic16 -p18f2550 -I . -c -c main.c -o main.o
Processor: 18f2550
sdcc -mpic16 -p18f2550 -I . -c -c system/usb/usb9/usb9.c -o 
system/usb/usb9/usb9.o
Processor: 18f2550
Assertion failed: IS_DATA_PTR(operandType(left)), 
file gen.c, line 10532

This application has requested the Runtime to terminate 
it in an unusual way.
Please contact the application's support team for more 
information.
Caught signal 22: SIGABRT
make: *** [system/usb/usb9/usb9.o] Error 1

>Yes please test it.  I have not got a method of getting the code onto a
>chip yet - so I have no idea if it works.  It may be worth checking that I
>have got the config bits set correctly since its the first iteration
>after reading the manual.

I think you may want to try Wisp628 using xwisp2 1.8.1 version.
It supports the 18F USB parts and many more chips.

>The output of the compilation is exactly what I get from the 19th Sept
>version im using, except for the 'warning: processor mismatch in...'
>messages.

I know these warning messages can be turned off. Perhaps it is related
to the gputils package difference. Anyway, this is not a problem.

>so versions of sdcc that work are: 2.5.3 Oct 19 2005 and 2.5.3 Sep 19 2005
>
>Julian

For the newer version, I think there is a work-around. Even though the
make process failed because of the compiling issue. The asm files have been
created. They can be assembled by using "gpasm -c". Then we can manually
use gplink to link the object files and create the hex file. I will
try out this later.

Regards,
Xiaofan

>For the newer version, I think there is a work-around. Even though the
>make process failed because of the compiling issue. The asm files have been
>created. They can be assembled by using "gpasm -c". Then we can manually
>use gplink to link the object files and create the hex file. I will
>try out this later.
>
>Regards,
>Xiaofan

I just tried out this simple fix under Windows and MSys. It at least 
generated the hex file.

The three files need to manual assembled are the following:
system/usb/usb9/usb9.asm;
system/usb/usbctrltrf/usbctrltrf.asm;
system/usb/class/cdc/cdc.asm.

Regards,
Xiaofan

$ sdcc -v
SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08
2.5.4 #1150 (Nov  9 2005) (MINGW32)

xiaofan@PC-386 /c/software/sdcc/MCHPFSUSB/fw/Cdc
$ ls -la *.hex
-rw-r--r--    1 xiaofan  Administ    20845 Nov 11 13:27 main.hex

Hi John

I saw that you use the 18f4455. What other changes did you perform?  
While building Julians code the SIGABRT is gone now. But instead I  
get a SIGSEGV while compiling usbctrltrf.c. I just don't get why sdcc  
crashes with one code and with the other one it doesn't.

Cheers,
Ezra.

Am 12.11.2005 um 07:50 schrieb John Swensen:

> Chen Xiao Fan <xiaofan <at> sg.pepperl-fuchs.com> writes:
>
>>
>> The same error occurs here under Windows SDCC.
>>
>> Regards,
>> Xiaofan
>>
>> Assertion failed: IS_DATA_PTR(operandType(left)),
>> file gen.c, line 10532
>>
>>
>
> I kept getting this, even with a recent snapshot.  So I used his  
> package as a
> model and went back and tried to make as few changes as possible.   
> I finally got
> it working on various new and old version of sdcc.  It can be found at
>
> http://swenmac.homeip.net:8080/MC2.tbz
>
> I think there might be some startup and interrupt issues that need  
> resolved, but
> I am pretty sure it will compile for any somewhat-recent version of  
> sdcc.
>
> John
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

>
>I actually was able to get this to compile for 
>18f2450/2455/2550/2555 also.
>
>John

The latest snapshot solve the building problem. Both Julian 
and John's SDCC port can now be built. I have a problem with 
gplink for John's Makefile code (missing definition for symbol)
but I can adapt Julian's Makefile and solve the problem.

xiaofan@PC-386 /c/software/sdcc/MC2/fw/Cdc
$ sdcc -v
SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51
/ds400/hc08 2.5.4 #1152 (Nov 13 2005) (MINGW32)

The original code is for 18F4550 (PICDEM FS USB) and uses Port D.
Port D does not exist in the 28 pin 18F USB parts (18F2455 and 
18F2550 and the future 18F2450). Therefore I think we at least
need to change io_cfg.h if we want to adapt the codes to 18F2455
or 18F2550. It is a bit strange that SDCC compiles the code
for 18F2550 without the need to change io_cfg.h.

Julian has removed user/temperature.c from the project since it
does not compile under sdcc (missing spi.h). John's sdcc port
from the HiTech C port seems to be okay with that file.

I've tried to adapt the code to PICkit 2 hardware (but keep the
bootloader) using Julian's port as the base. Somehow it compiles 
but it turns PICkit 2 to a useless paperweight (too light as well) 
after flashing the Cdc firmware. ;-( 

I have to re-flash the PICKit 2 firmware using a Promate III.
I'd better build a simple 18F2550 test boards for the testing. 
I will try to get it working first with MPLAB C18 codes and 
then try the SDCC port. This will take some time though.

Regards,
Xiaofan

I successfully compiled Johns port for the 18f2550. I just changed  
the LEDs to Port C. I flashed it to my test board, but it didn't  
work. I figured out that the config words aren't set in the code  
(right?) so I added them. Anyway, still no luck. The only thing I  
managed was making my USB freeze. I definitely need to take a closer  
look at my setup.
Sadly I'll haven't have to much time the next three weeks, gota go to  
the army..., but I'll take my laptop. So I'm looking forward to  
reading about the results.

Cheers,
Ezra.

Am 14.11.2005 um 04:07 schrieb Chen Xiao Fan:

>>
>> I actually was able to get this to compile for
>> 18f2450/2455/2550/2555 also.
>>
>> John
>
> The latest snapshot solve the building problem. Both Julian
> and John's SDCC port can now be built. I have a problem with
> gplink for John's Makefile code (missing definition for symbol)
> but I can adapt Julian's Makefile and solve the problem.
>
> xiaofan@PC-386 /c/software/sdcc/MC2/fw/Cdc
> $ sdcc -v
> SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51
> /ds400/hc08 2.5.4 #1152 (Nov 13 2005) (MINGW32)
>
> The original code is for 18F4550 (PICDEM FS USB) and uses Port D.
> Port D does not exist in the 28 pin 18F USB parts (18F2455 and
> 18F2550 and the future 18F2450). Therefore I think we at least
> need to change io_cfg.h if we want to adapt the codes to 18F2455
> or 18F2550. It is a bit strange that SDCC compiles the code
> for 18F2550 without the need to change io_cfg.h.
>
> Julian has removed user/temperature.c from the project since it
> does not compile under sdcc (missing spi.h). John's sdcc port
> from the HiTech C port seems to be okay with that file.
>
> I've tried to adapt the code to PICkit 2 hardware (but keep the
> bootloader) using Julian's port as the base. Somehow it compiles
> but it turns PICkit 2 to a useless paperweight (too light as well)
> after flashing the Cdc firmware. ;-(
>
> I have to re-flash the PICKit 2 firmware using a Promate III.
> I'd better build a simple 18F2550 test boards for the testing.
> I will try to get it working first with MPLAB C18 codes and
> then try the SDCC port. This will take some time though.
>
> Regards,
> Xiaofan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>