5c14780403
This converts all the YAML files to JSON files, as json parsing is built into python instead of being a separate library requiring installation. YAML is a superset of JSON, but putting comments in is not quite as obvious as it is in yaml. The following glue was used to convert yaml to json: python -c 'import sys, yaml, json; json.dump(yaml.load(sys.stdin), sys.stdout, indent=4)' < $1 > $2 Clearly I haven't tested this on every single platform, and this doesn't address the large blobs of yaml in the lpc4300 scripts directory, only the cortex NVIC generation process. I've tested a few IRQ driven example apps, and I've checked the generated output of some known cases like the LM3s that has explicit gaps, and they are all generated correctly.
75 lines
1.5 KiB
JSON
75 lines
1.5 KiB
JSON
{
|
|
"irqs": [
|
|
"wwdg",
|
|
"pvd",
|
|
"tamper",
|
|
"rtc",
|
|
"flash",
|
|
"rcc",
|
|
"exti0",
|
|
"exti1",
|
|
"exti2",
|
|
"exti3",
|
|
"exti4",
|
|
"dma1_channel1",
|
|
"dma1_channel2",
|
|
"dma1_channel3",
|
|
"dma1_channel4",
|
|
"dma1_channel5",
|
|
"dma1_channel6",
|
|
"dma1_channel7",
|
|
"adc1_2",
|
|
"usb_hp_can_tx",
|
|
"usb_lp_can_rx0",
|
|
"can_rx1",
|
|
"can_sce",
|
|
"exti9_5",
|
|
"tim1_brk",
|
|
"tim1_up",
|
|
"tim1_trg_com",
|
|
"tim1_cc",
|
|
"tim2",
|
|
"tim3",
|
|
"tim4",
|
|
"i2c1_ev",
|
|
"i2c1_er",
|
|
"i2c2_ev",
|
|
"i2c2_er",
|
|
"spi1",
|
|
"spi2",
|
|
"usart1",
|
|
"usart2",
|
|
"usart3",
|
|
"exti15_10",
|
|
"rtc_alarm",
|
|
"usb_wakeup",
|
|
"tim8_brk",
|
|
"tim8_up",
|
|
"tim8_trg_com",
|
|
"tim8_cc",
|
|
"adc3",
|
|
"fsmc",
|
|
"sdio",
|
|
"tim5",
|
|
"spi3",
|
|
"uart4",
|
|
"uart5",
|
|
"tim6",
|
|
"tim7",
|
|
"dma2_channel1",
|
|
"dma2_channel2",
|
|
"dma2_channel3",
|
|
"dma2_channel4_5",
|
|
"dma2_channel5",
|
|
"eth",
|
|
"eth_wkup",
|
|
"can2_tx",
|
|
"can2_rx0",
|
|
"can2_rx1",
|
|
"can2_sce",
|
|
"otg_fs"
|
|
],
|
|
"partname_humanreadable": "STM32 F1 series",
|
|
"partname_doxygen": "STM32F1",
|
|
"includeguard": "LIBOPENCM3_STM32_F1_NVIC_H"
|
|
} |