Dear Erel,
I develop hardware systems for a few year now, and some use Atmel chips. I have tested B4R, and it works well when using the UNO,ESP and some SMT32 cores, but fails if I use the Barebone cores (MightyCore and MiniCore for the Atmega8,16,32 etc. up to Atmega1284).
On the Atmel cores it seems to be related to operator 'new(unsigned int, void*)'.
My questions are:
Is this a bug on B4R and can it be fixed?
If it is not a bug, is it possible in the future the B4R to support these barebone cores?
I develop hardware systems for a few year now, and some use Atmel chips. I have tested B4R, and it works well when using the UNO,ESP and some SMT32 cores, but fails if I use the Barebone cores (MightyCore and MiniCore for the Atmega8,16,32 etc. up to Atmega1284).
On the Atmel cores it seems to be related to operator 'new(unsigned int, void*)'.
My questions are:
Is this a bug on B4R and can it be fixed?
If it is not a bug, is it possible in the future the B4R to support these barebone cores?
B4X:
Arduino: 1.8.13 (Windows 10), Board: "ATmega328, Yes (UART0), EEPROM retained, 328P / 328PA, BOD 4.3V, LTO enabled, External 16 MHz"
z:\Temp\ccPOMjPv.ltrans0.ltrans.o: In function `GetBytes':
sketch/B4RCore.cpp:335: undefined reference to `operator new(unsigned int, void*)'
z:\Temp\ccPOMjPv.ltrans0.ltrans.o: In function `SubString2':
sketch/ByteConverter.cpp:77: undefined reference to `operator new(unsigned int, void*)'
collect2.exe: error: ld returned 1 exit status
exit status 1
Error compiling for board ATmega328.
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.