ContributionsMost RecentMost LikesSolutionsRe: What QUARTUS Release fixes Year 2038 bug? I found out that GCC is *NOT* the one controlling time_t/time64_t it is done by the "C Library" which I am sure in this case is the ALTERA (now IBM) C Library (per below)... So AGAIN, what version of QUARTUS is needed to (ideally) have a 32-bit UNSIGNED Time or have a 64-bit SIGNED Time in the QUARTUS C Libarary? QUARTUS 11.1sp2 has "time_t" in: c:\altera\11.1sp2\nios2eds\bin\gnu\H-i686-mingw32\nios2-elf\include\sys\types.h and there is no "time64_t" defined in that file! From GCC: On Wed, 7 Jul 2021, 21:10 Steger, Matthew via Gcc-help, <gcc-help@gcc.gnu.org> wrote: What version (exactly) of GCC added the "time64_t" and all TIME Related functions (including Printing formats) allowed 64-bit time (to FIX the Year 2038 issue with "time_t") Those functions are not part of GCC. They are provided by the C library, not GCC. If you are using Linux, your C library is probably glibc. It is a completely separate project from GCC with its own releases. Also did *ANY* version of GCC support 32-bit UNSIGNED time (good until 2106) including all TIME Related fucntions (and Printing formats)? GCC supports whatever the C library does. What QUARTUS Release fixes Year 2038 bug? We are using Cyclone IV chips (one is EP4CE30F23) with Quartus 11.1sp2 Build 259 and this NIOSII "system" *HAS* the Year 2038 bug because "time_t" is defined as a SIGNED 32-bit integer. This is a PROBLEM, see https://en.wikipedia.org/wiki/Year_2038_problem What version of QUARTUS (including GCC and RE-definition of "time_t") can I upgrade to in order to ensure dates after 2038 will work. NOTE: I do *NOT* Care about dates PRIOR to 1970 so I am OK (and would actually PREFER) a simple change of "time_t" to UNSIGNED 32-bit Integer which would give us until 2106 (per link above)...our products won't last that long, but they certainly will be around past 2038. We use SmartCards in our system and they generally have a 10 year Expiration Date so RIGHT NOW that is MID 2031...so we are getting CLOSE to having issues (cards will start expiring PRIOR to 1970 and thus would be EXPIRED). What QUARTUS Release fixes Year 2038 bug? We are using Cyclone IV chips (one is EP4CE30F23) with Quartus 11.1sp2 Build 259 and this NIOSII "system" *HAS* the Year 2038 bug because "time_t" is defined as a SIGNED 32-bit integer. This is a PROBLEM, see https://en.wikipedia.org/wiki/Year_2038_problem What version of QUARTUS (including GCC and RE-definition of "time_t") can I upgrade to in order to ensure dates after 2038 will work. NOTE: I do *NOT* Care about dates PRIOR to 1970 so I am OK (and would actually PREFER) a simple change of "time_t" to UNSIGNED 32-bit Integer which would give us until 2106 (per link above)...our products won't last that long, but they certainly will be around past 2038. We use SmartCards in our system and they generally have a 10 year Expiration Date so RIGHT NOW that is MID 2031...so we are getting CLOSE to having issues (cards will start expiring PRIOR to 1970 and thus would be EXPIRED). Re: Why can't I download the following link anymore...it used to work when it was under ALTERA, seems like whoever changed the links over to INTEL broke something?I got it thanks! Matthew B. Steger | Sr. Software Engineer T +1.847.871.1177 | M +1.630.254.2243 Genfare | 800 Arthur Ave | Elk Grove Village IL 60007 Genfare.com<https://www.genfare.com/> | LinkedIn<https://www.linkedin.com/company/genfare> | Customer Care<https://www.genfare.com/customer-care/> The information contained in this electronic mail transmission is intended by SPX Corporation for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender’s address records can be corrected.Re: Why can't I download the following link anymore...it used to work when it was under ALTERA, seems like whoever changed the links over to INTEL broke something?It didn’t work on first try, but I didn’t get the error and the “Download your file now<http://download.altera.com/akdlm/software/acds/11.1sp2/259/standalone/11.1sp2_259_quartus_free_windows.exe>” link on that page worked, Thanks! Matthew B. Steger | Sr. Software Engineer T +1.847.871.1177 | M +1.630.254.2243 Genfare | 800 Arthur Ave | Elk Grove Village IL 60007 Genfare.com<https://www.genfare.com/> | LinkedIn<https://www.linkedin.com/company/genfare> | Customer Care<https://www.genfare.com/customer-care/> The information contained in this electronic mail transmission is intended by SPX Corporation for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender’s address records can be corrected.Why can't I download the following link anymore...it used to work when it was under ALTERA, seems like whoever changed the links over to INTEL broke something? If you try to download from here: https://www.intel.com/content/www/us/en/programmable/downloads/software/quartus-ii-we/111sp2.html You get this: Invalid URL The requested URL "[no URL]", is invalid. Reference #9.f6cd317.1575306069.20e2170 Please let me know when this is FIXED, I am getting a new PC and I have to re-install it on my new PC… Re: How to fix "OutOfMemoryError: Java heap space" error We have an 8MB EPCS Flash and 16MB RAM and he RESET vector points to EPCS (BOOT). Lower 1MB of this is FPGA and BOOT Upper 7MB of this is our (zipped) APP ... which is built with SAME FPGA as BOOT (but does not have another copy) At Power Up: The FPGA is loaded by H/W from EPCS Flash The BOOT is copied into RAM and Vectored to in RAM by H/W BOOT sees APP image in EPCS is VALID and unzips it to RAM and jumps to it (BOOT is now DONE) APP image runs out of 16MB RAM (using FPGA loaded from BOOT) Re: How to fix "OutOfMemoryError: Java heap space" error The EPCS is 8M and we have no problem fitting in that (code only no RAM) even though GCC Build thinks it won't fit due to us putting a BOOT (small code and FPGA load) in 1MB of EPCS and a ZIPPED Application in remaining 7MB. GCC Build thinks APP won't fit (and without being ZIPPED it probably wouldn't). RAM is 16MB Total which must fit the APP code (no FPGA since that is loaded by BOOT) and all RAM variables. Re: How to fix "OutOfMemoryError: Java heap space" error Have you decided what EXACTLY (including WAS/NOW) in the BSP you want me to change? Re: How to fix "OutOfMemoryError: Java heap space" error Increasing RAM Size on the boards is out-of-spec, we have 15,000 boards already in-service that new S/W updates. As I stated, it has be "a while" since I tweaked any settings in the BSP. Please list EXACTLY what you want me to change in the BSP (not loose terms) including FROM and TO values and I can try that!