afull’s reputation

afull 42 Rep.

afull's reputation

Total 42

0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

June 22, 2016 Asked GNUARM-NONEV16.01-EABI Compiler Crash

June 8, 2016 Commented Hi, OK. I will put a document together, however I am very busy and it may take a while. Do you also want me to include samples that make the compiler crash too? For example: cc1plus.exe: out of memory allocating 107868728 bytes src/relative_pose/modules/sixpt/subdir.mk:18: recipe for target 'src/relative_pose/modules/sixpt/modules2.o' failed make: *** [src/relative_pose/modules/sixpt/modules2.o] Error 1 Or are these errors outside the scope of E2Studio and in the realm of machine virtual memory settings? Best regards, Adam.

May 25, 2016 Commented Hi, Please keep this open as it is still full un-answered & time is required to put a sample project together. Best regards, Adam.

May 25, 2016 Commented The include files have dissapeared from the page, they are: iostream fstream stdlib.h stdio.h memory functional atomic limits.h

May 25, 2016 Commented Hi, I'm sorry I deleted the workspace .metadata folder. This folder quickly becomes huge and as far as I can see contains only a few preferences, which I am quite happy to reset. I keep the workspace in a separate folder to the project files and it is not under version control. The archive file and include file bugs are also in V16.01. To reproduce the include file bugs simply generate a C++ static library project with -mfloat-abi=hard. Then add the following standard headers to one of the sample C++ files: #include #include #include #include #include #include #include #include If you try to build the project it will fail because E2Studio has failed to add any include paths. If you want the code to build then manually add the following paths: ${TCINSTALL}/arm-none-eabi/include ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION} ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION}/arm-none-eabi/fpu ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include-fixed Then in the compiler options add the option -std=gnu++11. Only then will the library compile. Using the V16.01 tool chain generate a C++ project changing only Floating Point ABI to Hard (there is no option for vfpv3). In order for it to link you have to manually change the option to vfp3. Then add gnu++11 option to the compiler settings and the include files to projectname.cpp & yet again it fails to link. As the documentation is as much use as a chocolate fire guard, the best option is to go to https://gcc.gnu.org/mirrors.html and download the source code to the appropriate GCC version (5.2 for V16.01). This is the only way that user's of E2Studio will be able to figure out what the include folders should be and how to initialise the C++ standard library. I have never had so many issues with the quality of the tool integration in any other IDE. I hope that future releases of E2Studio are better documented and address the issues with the project generators for the GNUARM-NONE-EABI Toolchain. Best regards, Adam

May 23, 2016 Commented Hi, In summary the documentation for libstc++ is missing from C:\Program Files (x86)\KPIT\GNUARM-NONEv16.01-EABI\. There is some documentation at https://gcc.gnu.org/onlinedocs/gcc-4.9.2/libstdc++/manual/ and https://gcc.gnu.org/onlinedocs/gcc-4.9.2/libstdc++/api/ which may be of some help but there is no documentation pertinent to the build used by the tool chain. There are bugs in E2Studio with regards to the archive libraries and file path includes for both toolchain versions 14.02 & 16.01 where the user has to figure out which paths to use. For a C++ project with tool chain 14.02 & -mfloat-abi=hard the following include paths are required: ${TCINSTALL}/arm-none-eabi/include ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION} ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION}/arm-none-eabi/fpu ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include-fixed The following archive search directories are required: "${CONFIGDIR}" "${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/fpu" "${TCINSTALL}/arm-none-eabi/lib/fpu/interwork" And the following archive files: ${BuildArtifactFileBaseName} gcc stdc++ There is a bug in E2Studio where the C/C++ Build Change Toolchain Version entry disappears. The work-around is to import the projects into another workspace and it re-appears. Best regards, Adam.

May 18, 2016 Commented Hi, Thank you for your continued support. However this does not completely answer the question. Firstly, can you provide a code sample showing the copy technique particularly obtaining the source and destination addresses and lengths of the section from the linker. Secondly there are many extra sections which are defined in addition to .text, .data, .bss for C++. How are these to be handled? After the sections have been copied then the global objects must be constructed. If you want I can put a simple project together (for V14.02) which you could modify to demonstrate this? I think it would be a useful example for other users of the GNU tool chain. Best regards, Adam.

May 17, 2016 Commented Hi Darius, Thanks, I'll am really struggling with the linker script! The question is about section mapping, I don't know that the question was particularly clear. So the linker creates an executable image which is linked to the address 0x1800 0000. Within that image I'd like sections of code and data to be placed at 0x6000 0000 and 0x4800 000. The code at 0x1800 0000 will initialise the SDRAM, SRAM, L1 Cache, L2 Cache and TLB then copy sections of code and initialised data to the respective destinations. The question is how do I tell the linker that the functions in a particular section (which it has assigned an address within the 0x18XX XXXX range) are "mapped" to addresses 0x6XXX XXXX and 0x48XX XXX? Can you make a simple project with a linker script that demonstrates this? Best regards, Adam.

May 16, 2016 Asked Is there any documentation or an application note on section mapping with the GNUARM-NONE-EABI tool chain?

May 13, 2016 Commented Hi Darius, Finally after resolving the link errors I ran the application and it almost instantly hit the abort vector. I don't have time to spend the next week of my life debugging the dog turd that dropped out of the linker, so I thought that I could just change the tool chain version back to 14.02. However I was unable to find the option. So I uninstalled V16.01, Close E2Studio, reverted the project. Then when I re-opened the project, E2Studio unregistered the tool chain then reported that V16.01 was missing and it would use V14.02. Is this the only way to do it? Best regards, Adam.

May 13, 2016 Commented Hi Darius, This is from the console: -L“C:\PROGRA~2\KPIT\GNUARM~2.01-\ARM-NO~1\ARM-NO~1/arm-none-eabi/lib/armv7-ar/thumb/fpu�? There appears to be yet another bug in the E2Studio tool support. The path passed to the linker contains an invalid character. Deleting the entry and re-entering it fixes the problem. Then, finally, when it links there is an undefined reference: C:\PROGRA~2\KPIT\GNUARM~2.01-\ARM-NO~1\ARM-NO~1/arm-none-eabi/lib/armv7-ar/thumb/fpu\libstdc++.a(time_members.o): In function `std::__timepunct::_M_put(wchar_t*, unsigned int, wchar_t const*, tm const*) const': time_members.cc:(.text._ZNKSt11__timepunctIwE6_M_putEPwjPKwPK2tm+0x3e): undefined reference to `wcsftime' Are there any release notes for libstdc++ to indicated the differences between the V14.02 and V16.01 tool chains? Best regards, Adam.

May 12, 2016 Commented Hi Darius, Thanks for your help. I have installed 16.01, upgraded the tool chains for the project and associated libraries. Then changed the the vfpv3 option as described. Previously I had the settings so the project linked and worked with V14.02, now it is back to the arm-none-eabi-ld: cannot find -lstdc++ link error. E2Studio has the following archive file paths, in the order shown below: "${CONFIGDIR}" "${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/armv7-ar/thumb/fpu" “${TCINSTALL}/arm-none-eabi/lib/armv7-ar/thumb/fpu” In the "C:\Program Files (x86)\KPIT\GNUARM-NONEv16.01-EABI\arm-none-eabi\arm-none-eabi\arm-none-eabi\lib\armv7-ar\thumb\fpu\" folder there is a libstdc++.a file. Any idea of what else is wrong? Best regards, Adam.

May 11, 2016 Commented Hi Darius, Thanks, however I believe that this documentation is for glibc. E2Studio uses newlib, so while some of it appears to apply there are bits missing from newlib. So C++ code which builds with glibc has errors with newlib, which would be easier to avoid if it were documented. Without any documentation I have had to use a trial and error approach to establish which archive files and library paths to use. Using the E2Studio project generator to make a C++ project with default options bar vfpu=hard adds the following archive search directories: Archive search directories "${CONFIGDIR}" "${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/fpu/interwork" "${TCINSTALL}/arm-none-eabi/lib/fpu/interwork" And the following archive library files: ${BuildArtifactFileBaseName} gcc stdc++ And include directories: ${TCINSTALL}/arm-none-eabi/include ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include In order for the C++ to build and link I had to change the archive search directories to: "${CONFIGDIR}" "${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/fpu" "${TCINSTALL}/arm-none-eabi/lib/fpu/interwork" And add the following include directories: ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION} ${TCINSTALL}/arm-none-eabi/include/c++/${GCC_VERSION}/arm-none-eabi/fpu ${TCINSTALL}/lib/gcc/arm-none-eabi/${GCC_VERSION}/include-fixed Although the code links and runs OK without any documentation it is difficult to know if this is correct. Best regards, Adam.

May 10, 2016 Commented Hi Darius, I'm using e2 studio Version: 5.0.0.043 with the Build support for Renesas RZ devices using the KPIT GNUARM-NONE Toolchain V14.02. I have solved the problem by calling std::ios_base::Init, this gets the file handles from stdin, stdout and stderr. However, where is the documentation? I still have many other questions which I am sure I would find the answers to, if only I knew where it was! Best regards, Adam.

May 9, 2016 Asked Where is the documentation which describes the initialisation of the C++ standard library?

May 9, 2016 registration

« Previous 1 2