Does USBDM stand alone programmer need Codewarrior etc? - Page 1
Forum section: electronics / general

author: Circlotron
author_rank: Super Contributor
timestamp: June 02, 2022, 02:01:57 pm
content: Got myself a USBDM programmer today and it works just great on S08 micros. I'm not interested in all the debug stuff, only want to download s19 files into the target board. The other day I installed an evaluation version of Codewarrior but it turns out it doesn't suit my requirements so I'm planning on deleting it.Seeing I don't need all the debug stuff, will the stand alone USBDM programmer work without Codewarrior installed?I installed it on Win7 and it works okay, but when I installed it on Mint Mate I couldn't get it to do anything. No GUI appears. Maybe I need to install extra stuff?

author: pgo
author_rank: Regular Contributor
timestamp: June 03, 2022, 12:37:42 am
content: Hi,The stand-alone programmers do not need any other software apart from dependencies e.g. wxWindows.I use it with Linux mint.Did you install the deb or build from scratch?There are often problems with dependencies if using the deb as version change rather often.Run the programmer in a shell and see if there are any messages.bye

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 12:53:45 am
content: Yeah, I installed from deb.From the command line it sayslibstdc++.so.6: version `GLIBCXX_3.4.26' not foundlibwx_gtk3u_core-3.0.so.0: version `WXU_3.0.5' not foundSo there's something for me to start looking for.

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 01:12:22 am
content: ...and as usual with Linux, this takes me down a thousand rabbit holes.Can someone tell me where to get these libraries and how to install them?Edit -> installing gcc 9 solved the first one.

author: pgo
author_rank: Regular Contributor
timestamp: June 03, 2022, 06:40:28 am
content: Trysudo apt-get install libwxgtk3.0BUT if I remember correctly with that error I was not able to get it to work at all. There is some change in wxWidgets that breaks in recent versions of Mint.I was able to build a deb file in an older version or a newer version but the builds were incompatible on the other version.The deb was built on 5.4.0-113-generic (from uname -r)The deb has a list of dependencies:Depends: libwxgtk3.0-gtk3-0v5, libgcc1, libstdc++6, libxerces-c3.2, libc6, libtcl8.6, libusb-1.0-0so they should have been intsalled anyway.I don't really understand Linux library versionsbye

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 09:32:56 am
content: In the meantime I tried installing using the following:Code:cd WorkDirectorysudo apt-get install gitgit clone https://github.com/podonoghue/usbdm-eclipse-makefiles-build.gitgit clone https://github.com/podonoghue/usbdm-eclipse-plugins.gitcd usbdm-eclipse-makefiles-buildsudo ./LinuxPackages./MakeAll./CreateDebFilesudo ./UpdateThat worked great with my lab pc and I'm happy as a pig in mud with it. I took the resulting deb file and installed it in my play pc but still wouldn't run. Starting it from the command line again said libwx_gtk3u_core-3.0.so.0: version `WXU_3.0.5' not found. So I tried making the deb file on the play pc and part way through got the following error:Code:Building usbdm-interface-arm 64-bit================================================================make dll -f Target.mk BUILDDIR=usbdm-interface-arm MODULE=bdm-interface-arm CDEFS=''-DCOMPILE_USBDM_INTERFACE_DLL'' BITNESS=64make: Entering directory '/home/my_name/usbdm-eclipse-makefiles-build/BdmInterface_DLL'-- Making directory ../PackageFiles/lib/x86_64-linux-gnumkdir -p ../PackageFiles/lib/x86_64-linux-gnu-- Making directory ../PackageFiles/bin/x86_64-linux-gnumkdir -p ../PackageFiles/bin/x86_64-linux-gnu-- Making directory usbdm-interface-arm.x86_64-linux-gnumkdir -p usbdm-interface-arm.x86_64-linux-gnu-- Building usbdm-interface-arm.x86_64-linux-gnu/BdmInterfaceCommon.o from src/BdmInterfaceCommon.cppg++ -fPIC -O3 -g3 -m64 -std=gnu++17 -Wall -shared -fvisibility=hidden -fvisibility-inlines-hidden -DCOMPILE_USBDM_INTERFACE_DLL -Isrc -I../Shared/src -MD -c src/BdmInterfaceCommon.cpp -o usbdm-interface-arm.x86_64-linux-gnu/BdmInterfaceCommon.oIn file included from ../Shared/src/BdmInterface.h:37:0,from src/BdmInterfaceCommon.h:11,from src/BdmInterfaceCommon.cpp:39:../Shared/src/AppSettings.h:33:10: fatal error: filesystem: No such file or directory#include <filesystem>^~~~~~~~~~~~compilation terminated.Target.mk:94: recipe for target 'usbdm-interface-arm.x86_64-linux-gnu/BdmInterfaceCommon.o' failedmake: *** [usbdm-interface-arm.x86_64-linux-gnu/BdmInterfaceCommon.o] Error 1make: Leaving directory '/home/my_name/usbdm-eclipse-makefiles-build/BdmInterface_DLL'Makefile-x64.mk:9: recipe for target 'usbdm-interface-arm' failedmake: *** [usbdm-interface-arm] Error 2make: Leaving directory '/home/my_name/usbdm-eclipse-makefiles-build/BdmInterface_DLL'Makefile-x64.mk:59: recipe for target 'build-BdmInterface_DLL' failedmake: *** [build-BdmInterface_DLL] Error 264-bit Make failedPress any key to continue...Given the astoundingly complex things that were scrolling up the screen, I have no idea what to do next

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 09:44:52 am
content: The error message says../Shared/src/AppSettings.h:33:10: fatal error: filesystem: No such file or directorybut the files appears to actually exist...

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 09:53:43 am
content: Quote from: pgo on June 03, 2022, 06:40:28 amTried that and then installed the pre-made deb and still no go.

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 12:04:34 pm
content: Quote from: Circlotron on June 03, 2022, 09:44:52 amCloser look - actual missing files areBdmInterfaceCommon.hBdmInterfaceCommon.cppWhat to do now?

author: pgo
author_rank: Regular Contributor
timestamp: June 03, 2022, 12:34:09 pm
content: Hi,Those files are in BDMInterface_DLL.I think the actual problem is that I have just introduced some C++19 featuresfilesystem::path.I have modified the files on Github to use a older style.Please try again.Alternatively - update to a later version of GCC.bye

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 12:53:47 pm
content: Okay, I'll try it again.Also i just had a look at the lab pc where everything works okay and neither of those files were on it either.

author: Circlotron
author_rank: Super Contributor
timestamp: June 03, 2022, 01:18:45 pm
content: Quote from: pgo on June 03, 2022, 12:34:09 pmWoohoo!Thanks heaps pgo. I really appreciate your help.P.S. That is Linux I'm running, but with Win2K window appearance.

author: Circlotron
author_rank: Super Contributor
timestamp: June 05, 2022, 09:34:36 am
content: Today I noticed that it wrongly identifies a 9S08PA16 as 9S08PA8.PA8 flash starts at $E000 and PA16 starts at $C000.

author: pgo
author_rank: Regular Contributor
timestamp: June 05, 2022, 02:08:24 pm
content: I believe the PA8 and PA16 have the same SDID value. They are described by the same reference manual.When you doDetect Chipit provides alistof matching devices (2 in this case).I would expect PA8 and PA16 to both be present.I do not have every possible device to verify this.byePS. It is quite possible that they are actually the same chip. The smaller device may be used to improve yield on partially defective devices.

author: Circlotron
author_rank: Super Contributor
timestamp: June 06, 2022, 12:27:04 am
content: Yes, it turns out that several variants have the same SDID value 0x0042 listed in the datasheet.PA8PA16PL16PT16