new user help

[richardb]

OK so after not getting anyware with windows 10 I thought id start again on a windows 7 machine.
So I have just freshly installed windows 7 on a machine, installed firewing, plugged in the firewing 32 board and then installed the driver supplied by using the have disk method.

all ok at this point the board had some previous code in it and displays to a terminal just fine.

I then tried to compile without modification the progarduino.bas from the tft user libs location.

on firewing 8 and firewing 16 it compiles fine. but when selecting firewing32 I get an error.
"one ore more errors have been reported during linking, build sourcefile in mplab to identify cause (progArduino.c)


so I thought it best to stop at this point and ask for help. last time i went on to install xc tool suite but that may have been the wrong thing to do.


any help would be great

Richard

[Coccoliso]

Hi,

the problem is in Sin(), Cos() and Tan() functions when compiled in "Firewing 32".
This does not happen using the MC32 toolsuite

[richardb]

This is odd as I've posted to this once and checked it...

anyway

Question 1. how do you know the problem is "in Sin(), Cos() and Tan() functions " , what do I need to install to debug this?


Question 2 do I just need to follow these instruction
http://www.firewing.info/pmwiki.php?n=FirewingUser.XC32Toolsuite
should I place the install directory in a different location ?


Regards

Richard

[Coccoliso]

Hi,
1) as mentioned in various posts and documents for debug MPLAB (v8_92) with XC32 (xc32-v1.30) compiler
2) toolsuites must be recognized by ide so MUST go here "C:\Program Files (x86)\Mecanique\Firewing\Bin\Toolsuite" folder

[richardb]

ok so you suggest

1) as mentioned in various posts and documents for debug MPLAB (v8_92) with XC32 (xc32-v1.30) compiler

and in the following link it links directly to v2.05
http://www.firewing.info/pmwiki.php?n=FirewingUser.XC32Toolsuite

I will try and find version 1.30 and see what happens


Richard

[Coccoliso]

Hi,

for compiler you can use 2.50 but then you will have to install the legacy includes (for gcc 32) also otherwise you will have problems with the device descriptors
( see MC post here http://www.microchip.com/forums/m877060.aspx - NB: link to MC dw page is broken )
In the past I had problems with more updated versions of IDE / XC compilers.
I use legacy IDE and XC and it certainly works in multiple installations.

[richardb]

ok so I tried again installing v2.05 from the link david provided.
and followed the instructions
it suggests the following

at the very top of your program. You should see the device change in the code explorer window, like this:

it doesn't.

I have also installed the Legacy Peripheral Libraries


and I'm still getting unable to locate linker file p32mx150f128b.lb

this is currently located in the following directory

C:\Program Files\Microchip\xc32\v2.05\pic32mx\lib\proc\

not sure where I should copy this to to fix ythe issue.

Richard

[Coccoliso]

Immagine1a.jpg (126.71 KiB) Viewed 42239 times

p32MX150F128B.ld not p32MX150F128B.lb
is here "C:\Program Files (x86)\Microchip\xc32\$COMPILER_VERSION$\pic32mx\lib\proc\32MX150F128B\" into a folder called 32MX150F128B.

Location is not a restriction for a PATH variable set in Windows path.

[Jerry Messina]

If you follow the link on the toolsuite page you'll automatically get the latest version of XC32 (2.05).

If that causes you problems I'd suggest an older version like 1.30 or 1.31 which you can get from the mchip archive page
http://www.microchip.com/development-tools/pic-and-dspic-downloads-archive

Sometimes the XC version matters since the code produced by firewing was tested with a particular version

[richardb]

@jerry
at the moment I have installed the 2.05version but I can go back to a pervious snapshot and install the 1.3 version.
what would you recommend?

Do you know what is happening with firewing? is it a dead project or ....