Hi everybody,

Some fresh news before the end of this year.
A damned maintenance guy has erased all my disk c: so I had to reinstall eveything, including many applications (CAD...) !!!

Back to my MPLAB installation.
For MPLAB 8, I had the famous message saying that mpasmwin could not be found. As I remembered an old matter of path I have reinstalled PBP3.1 directly under C:\. In fact this was not was necessary, the key point is to apply the recommendations from here : http://melabs.com/support/mplab.htm and to replace the PBPX.EXE by PBPMPLAB.BAT in the step two. Then it works.

I have an important question, maybe for Charles, at that point. The 18F27K40 looks as being a little bit "special". Does PBP3.1 support it under MPLAB 8 ?. I cannot find it in the list of the Project Wizard. However I find it in the two folders DEVICE and DEVICE_REFERENCE in the PBP3_1 directory. So ... ???



About MPLAB X now. The installation is quite easy. The reference is http://www.picbasic.co.uk/forum/showthread.php?t=18520. Thank you Ionnis ! Simply in the second step of installing the PBP chain one must be carefull to designate PBP_3 and not one of its directories. I have spent hours with this. My fault !

Making PBP3.1 working with MPLAB X is an other story. I have chosen to rebuild a new project from the source files used with MPLAB 8 and not to use the project migration function. I have four .asm files and one .pbp file. All have to be installed into the source section of the project. I made no modification to them with a right click as suggested by pedja089.

In my pbp source file those asm files are included by : #include "file.asm".

I did not want to include any path. So while building the project I choose to install the files in the project folder (tick the corresponding box) and selected the absolute path option. This leads to a project structure close to what we have under MPLAB 8. I have also ticked the long support in the compiler properties because I use this kind of variable.

A that point I am stucked after launching the build, with the message :' No rule to make target 'build/default/production/_ext/1465533315/file.o' where file.asm is my first asm files. Google shows that this is a very common message but with a wide vaiety of reasons. I have built a small project with only one .asm file. The same message is displayed but a correct .hex file is built in this case. Nothing is produced with the full project and 4 asm files.

I continue to dig

MikeBzh