Change order of board selection in 'tools' tab

[Deva_Rishi]

Hi,

When i encountered an issue with uploading to an ATTiny, i was referred to the 'boards.txt' file which solved the issue, and then i found that by modifying this file i could easily change the order in which certain options appear in the menu. That was great, now when i select an ESP8285 generic board, 128k SPIFFS is the default selection for the SPIFFS size (which is what i normally use) so chances of me accidentally overwriting the SPIFFS are greatly reduced.
Now i am looking to change the order in which the different packages show up on the list. Understandably i would prefer the boards that i use more often to be nearer to the top, and the ESP32 package with all it's varieties down the bottom. Anybody know in what file this information is kept ?
In other words, 'where are the links to the different boards.txt files stored ?'

[UKHeliBob]

As far as I know it is in boards.txt

I have moved the boards that I use mostly to the top to make them easier to select but be aware that any update to the boards will overwrite your changes

An example from C:\Users\Bob2\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.6\boards.txt

##############################################################
### DO NOT PUT BOARDS ABOVE THE OFFICIAL ESPRESSIF BOARDS! ###
##############################################################

d1_mini32.name=WEMOS D1 MINI ESP32

d1_mini32.upload.tool=esptool_py
d1_mini32.upload.maximum_size=1310720
d1_mini32.upload.maximum_data_size=327680
d1_mini32.upload.wait_for_upload_port=true

d1_mini32.serial.disableDTR=true
d1_mini32.serial.disableRTS=true

d1_mini32.build.mcu=esp32
d1_mini32.build.core=esp32
d1_mini32.build.variant=d1_mini32
d1_mini32.build.board=D1_MINI32

d1_mini32.build.f_cpu=240000000L
d1_mini32.build.flash_mode=dio
d1_mini32.build.flash_size=4MB
d1_mini32.build.boot=dio
d1_mini32.build.partitions=default
d1_mini32.build.defines=

d1_mini32.menu.FlashFreq.80=80MHz
d1_mini32.menu.FlashFreq.80.build.flash_freq=80m
d1_mini32.menu.FlashFreq.40=40MHz
d1_mini32.menu.FlashFreq.40.build.flash_freq=40m

d1_mini32.menu.PartitionScheme.default=Default
d1_mini32.menu.PartitionScheme.default.build.partitions=default
d1_mini32.menu.PartitionScheme.no_ota=No OTA (Large APP)
d1_mini32.menu.PartitionScheme.no_ota.build.partitions=no_ota
d1_mini32.menu.PartitionScheme.no_ota.upload.maximum_size=2097152
d1_mini32.menu.PartitionScheme.min_spiffs=Minimal SPIFFS (Large APPS with OTA)
d1_mini32.menu.PartitionScheme.min_spiffs.build.partitions=min_spiffs
d1_mini32.menu.PartitionScheme.min_spiffs.upload.maximum_size=1966080

d1_mini32.menu.CPUFreq.240=240MHz (WiFi/BT)
d1_mini32.menu.CPUFreq.240.build.f_cpu=240000000L
d1_mini32.menu.CPUFreq.160=160MHz (WiFi/BT)
d1_mini32.menu.CPUFreq.160.build.f_cpu=160000000L
d1_mini32.menu.CPUFreq.80=80MHz (WiFi/BT)
d1_mini32.menu.CPUFreq.80.build.f_cpu=80000000L
d1_mini32.menu.CPUFreq.40=40MHz (40MHz XTAL)
d1_mini32.menu.CPUFreq.40.build.f_cpu=40000000L
d1_mini32.menu.CPUFreq.26=26MHz (26MHz XTAL)
d1_mini32.menu.CPUFreq.26.build.f_cpu=26000000L
d1_mini32.menu.CPUFreq.20=20MHz (40MHz XTAL)
d1_mini32.menu.CPUFreq.20.build.f_cpu=20000000L
d1_mini32.menu.CPUFreq.13=13MHz (26MHz XTAL)
d1_mini32.menu.CPUFreq.13.build.f_cpu=13000000L
d1_mini32.menu.CPUFreq.10=10MHz (40MHz XTAL)
d1_mini32.menu.CPUFreq.10.build.f_cpu=10000000L

d1_mini32.menu.UploadSpeed.921600=921600
d1_mini32.menu.UploadSpeed.921600.upload.speed=921600
d1_mini32.menu.UploadSpeed.115200=115200
d1_mini32.menu.UploadSpeed.115200.upload.speed=115200
d1_mini32.menu.UploadSpeed.256000.windows=256000
d1_mini32.menu.UploadSpeed.256000.upload.speed=256000
d1_mini32.menu.UploadSpeed.230400.windows.upload.speed=256000
d1_mini32.menu.UploadSpeed.230400=230400
d1_mini32.menu.UploadSpeed.230400.upload.speed=230400
d1_mini32.menu.UploadSpeed.460800.linux=460800
d1_mini32.menu.UploadSpeed.460800.macosx=460800
d1_mini32.menu.UploadSpeed.460800.upload.speed=460800
d1_mini32.menu.UploadSpeed.512000.windows=512000
d1_mini32.menu.UploadSpeed.512000.upload.speed=512000

##############################################################


esp32cam.name=AI Thinker ESP32-CAM

esp32cam.upload.tool=esptool_py
esp32cam.upload.maximum_size=3145728
esp32cam.upload.maximum_data_size=327680
esp32cam.upload.wait_for_upload_port=true
esp32cam.upload.speed=460800
etc

Shows as

[Deva_Rishi]

Yeah i figured that one out as well, it's more about the order of the packages, i want the microcore to show up before the whole esp32 package

[UKHeliBob]

I don't find the order of the general board type ie MiniCore, AVR, ESP32 etc a problem but putting my boards at the top of each list certainly helped

[Deva_Rishi]

@UKHeliBob

I don’t find the order of the general board type ie MiniCore, AVR, ESP32 etc a problem

A problem is a big word, but for an ATTiny13 i need to scroll all the way down beyond all of those ESP32 boards. So you don't know ?

[UKHeliBob]

I am confused. Please post a screen shot of how and where you select the ATTiny13. Which boards.txt file is it in ?

[Deva_Rishi]

It is in the boards.txt of 'microcore' on my machine located at

C:\Users\deva_\AppData\Local\Arduino15\packages\MicroCore\hardware\avr\2.0.2\boards.txt

The packages show up in the same order as in the boards manager, but that is not the same order as in which the repositories are referenced in the preferences.
May it be that they show up in alphabetical order of the core name ? (eg Arduino, ATTiny, ESP32, ESP8266, MicroCore) That is actually fairly likely. Hmm maybe i can rename them....