64bit Linux

[ghamblin]

Hi Rick,

Welcome to my world. :-(.
Beyond just responding to me that it works in 64-bit Linux, and I'm missing libraries (Wouldn't say which ones), It's just crickets.

So as I'm certain that there are not enough of us using Linux to care about. I would, as I'm sure you would be willing to try testing for them. But, they (CCS) don't appear to be concerned about us at all.

I have been building headers to try to make my old code compile and run in XC8, with very limited success. If I get it working, I'll share it.

Glenn
_________________
-Glenn

[ghamblin]

Hmm, After a quick search it may be worth my while to switch to XC8 or XC compilers in general;
https://www.burningimage.net/cattrack/ccs-c-vs-microchip-xc8-compiler-comparison/
_________________
-Glenn

[temtronic]

Why not just dedicate a bare bones Windows based PC for PIC development ? I've done that for 2+ decades,saves LOT of headaches.
by barebones, I mean.. Windows OS and CCS. No internet,no 'aps', etc.

[ghamblin]

So that means using the old 32-bit MPLABX, on a version of windows that is obsolete (Not to mention that I really dislike Windoze). That's no better than running it in a VM or booting to my old 32 bit Linux. Not optimal.

I think it's just time for me to switch to a supported Linux compiler. I should have probably done it a long time ago, but I'm old and lazy. Learning is tougher than it used to be, but it'll be good for me.

Thanks for the suggestion though.
_________________
-Glenn

[alan]

Running fine in Ubuntu 18

output of ./ccsc +v

[temtronic]

I suggested a bare PC/Windows/Compiler system as it has no real issues, cut and burn.... no time lost trying to figure out OS commands, syntax, conflicts or other 'random acts of insanity'.

I program PICs on 3 different Windows PCs; Win98, XPP, W7U and don't care that the OS is 'obsolete'. All 3 of them run fine, no BSOD or other 'hiccups'.
I've used CCS PCM since V2.54 using MPLAB as the 'conduit' to burn code into PICs using PICStart-PLUSes and now PICkit3s.
Everything between the compiler and PIC doesn't matter to me, as long as it gets the bits into the PIC.

At 66, I've spent 1/2 my life 'playing with PICs' and, well, too old to change. Apparently you're 'supposed' to code in debug, simulate then release. I got Microchip to change MPLAB for me around 8v5 or so. What I have works fine for me. Easily create programs and burn into 18F46K22s, all day long, no problems...except typing ....that age thing and missing finger.
I don't need the 'latest and greatest' OS or ap, what's truly required is a stable, reliable 'platform'.
Heck my version of PCM is way out of date, 'obsolete', yet it does everything (and more) that I need it to do.
Jumping to another compiler will cost a LOT of time (and money). Different commands, syntax, loss of built-in functions, etc. Just getting 'up to speed' could be several man months.

[rickwalker]

Ok. ccsc +fh runs on glibc version 2.17, but fails on 2.30.

CCS support tells me that they think it fails from 2.28 and onward.

It's a bug in the glibc 32-bit compatibility. Support says "It is not clear if we will have a solution for the glibc bug or a 64 bit build first. Either solution is likely weeks away."

As a workaround I'm running it on an old Centos7 machine rather than my Ubuntu19.1 system. I'm also looking into Microchip compiler as an option or moving our new design to an ARM (Samd51) since we need a board spin anyway. The new ARM chips have massively more RAM/ROM for the same price and are supported directly by gcc.

--
Rick Walker

[ghamblin]

That's great Rick, At least you actually got an answer!

-Glenn
_________________
-Glenn

[alan]

Might be correct. Just checked and I am using 2.27 without problems.

[ghamblin]

Has anyone heard of any progress on the 64 bit Linux issue?
_________________
-Glenn

[jeremiah]

I have not heard of anything, but they have been pretty responsive when I call support, so you might try giving them a call during business hours and chatting with them.

[ghamblin]

Good idea. I'll try them Monday.
Thanks.
_________________
-Glenn

[ghamblin]

I did finally manage to call last week. And he said they are close but not ready to release yet.

I offered to help in any way that they think I could.
_________________
-Glenn

[bkamen]

FWIW -- if you're careful, you can convert (or install) an old OS to run inside a VM.

Virtualbox is free. Runs on Linux. Runs on windows.

Make a VM and load up something old like WinXP or Win7. (I have both kicking around)

If you're on Redhat, libvirt will probably work too.
_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D

[Tomi]

I don't know your problem is already solved or not, but WHY do you want to use CCS LINUX compiler(s)? I had bad experiences in the past (Win version was -and is- the main stream for the compiler - linux verison had poor maintenance). Anyway, CCS Win compilers run fine under wine in Linux. So I would suggest to install the "regular and up-to-date" windows CCS C compilers (pcb,pcm,pcd command line) running the installer exe file from wine64, then create some shortcuts and setup wine drive e.g. "Z:\" to your home (or root) directory. Then you can easily invoke the compiler using something like this:
WINEDEBUG=-all wine64 "/home/your_name/.wine/dosdevices/c:/Program Files/PICC/Ccsc.exe" +FD +LY -J -D +EA +EX $1
(The example assumes 24FJ pic, and the line is in a bash script; $1 is the filename as input parameter for the script)
I had no problem with this method in the last 6 years. My current config:
-Ubuntu 20.04.1 64 bit
-PCWHD compiler (pcwhdupd.exe)
-Geany IDE with custom script "compile.sh" associated with F5 button