for the life of me with the latest arduino ide 2.0.1
It always miss some files devnull.h or pro_micro.h BUT they are there or in the same folder than the ar488 ino file
even reverted to the old 1.8.x no luck
all come from : https://github.com/Twilight-Logic/AR488 and i use the latest SRC folder
and the arduino is the sparkfun pro micro at 16mhz : https://www.sparkfun.com/products/12640
I am sorry to hear this. I can't vouch for pro_micro_h as its part of the board library but am curious about the DEVNULL library. I have added instructions to the manual and the Readme indicating that the library needs to be installed using the Arduino IDE. I haven't tested the code in Arduino 2.0.x yet but it should work fine in 1.8.19. In the meantime, I will make a point of testing it in 2.0.x.
When you say it misses files, I presume you are getting error/warning messages during compile? If its still an issue, could I ask you to raise a case and post the related error messages here please:
https://github.com/Twilight-Logic/AR488/issuesThe DEVNULL library is quite simple and I could have just copied the code into one of my project files, but on the other hand it is not unusual for a project to depend on other third party libraries. It means that one does not have to re-invent the wheel and can simply download the library via the IDE from the maintainer. Doing so also gives them credit for the work. In the end I decided to add it as a dependency. If this is causing too much hassle then I am open to re-thinking that approach.
If you are using a case sensitive OS (filesystem) ... Ie. linux.
I have been "bitten" several times by the #include statement not matching the case of the file on the disk.
Usually won't be an issue on a M$ OS , but will be on linux & prob MAC too.
Not saying that this is the issue but ..... Worth a check.
This is a good point. On Microsoft Windows it doesn't matter since the FAT32 and NTFS filesystems are case insensitive. On other operating systems where file system are case sensitive, it will be importent to ensure that #include entries in code are specified in the same case as the ffilename. That having been said, I develop on Linux which IS case sensitive so, in theory, I should be catching any problem in that regard during development. On the other hand, my project files are on a shared NTFS drive. I therefore just checked the DEVNULL library. It's name is in uppercase in the Arduino IDE Library Manager. The filenames in libaries/DEVNULL are named DEVNULL.h and DEVNULL.cpp, both uppercase except for the extension, as is the already mentioned directory name. Its entry in the library_index is also upper case:
"providesIncludes": [
"DEVNULL.h"
"name": "DEVNULL",
For good measure, I also checked the developers GitHub page and its also in upper case there, so everything looks consistent.
Tried a new board NANO V3 BUT it as an Mega328 BP and once again it doesn't work with all the web tricks, another shi#$#$% clone, you have the old bootloader and the new bootloader ....
with the sketch blink ................ no led blink nada niet nothing
tried other boards support for the nano v3 with the BP variant web tricks no avail
What "web tricks" are you referring to? Are you using the Arduino Cloud editor by any chance?
Regarding that Nano V3, a quick search seems to indicate that the 328BP is different from the 328P and I will have a look at the detail. On eBay all the boards I found seem to have the 328P. Could you post a link to where you purchased the your Nano V3 board from?
I did also find a Nano 'red' board on eBay which has a 168P MCU. I have not tested either the 328PB or the 168P but perhaps it would perhaps not hurt to get a couple to try. If it differs, I would be able to create a layout for them.
It sounds like you have not had much 'fun' with your Sparkfun board. I have never tried one of these, but I was able to recover two 32u4 boards that had failed during upload by using a usbasp programmer to burn the bootloader back on to them. Woth regards to bootloaders, I would expect brand new Nano boards to be using the new bootloader, although if one has an old Nano board lying around it might still have the old bootloader on it. Of course with boards from the far east one never knows....
Incidentally I was considering to move the AR488 code to VsCode/PlatformIO at some point but haven't made a decision on that yet. However, before I get ahead of myself, I will test on Arduino IDE 2.0.x first.