Commit Graph

384 Commits

Author SHA1 Message Date
hathach 3689c4c604
more test 2023-12-11 14:38:37 +07:00
hathach 721ae45ebb
update hil test to support s3 2023-12-11 14:29:11 +07:00
hathach 0642a6d9e7
more artifacts 2023-12-11 11:56:04 +07:00
hathach fd55b96ca1
test changing upload artifacts for hil test 2023-12-11 11:45:50 +07:00
Ha Thach 338ff2daba
Merge pull request #2351 from IVOES/master
Add CodeQL Workflow for Code Security Analysis
2023-11-30 11:56:52 +07:00
hathach 66b9bd52d6
minor tweak to codeql.yml 2023-11-30 11:38:54 +07:00
hathach 0504192fb7
update buildscript 2023-11-29 22:30:58 +07:00
hathach fe4bb40207
fix pre-commit typo 2023-11-29 17:22:33 +07:00
hathach 1c1c2dc3b9
Merge branch 'master' into codeql 2023-11-29 17:21:21 +07:00
hathach 83840041a8
update esp32 to also be supported by hil test
test run locally well
2023-11-29 17:09:52 +07:00
hathach b45ad57c50
spare checkout test/hil and correct hil_pi4 uuid 2023-11-28 23:02:26 +07:00
hathach 0a4d92a71e
update hil for pi4 to use new hil_test.py 2023-11-28 18:28:45 +07:00
Brian 00484d18a5
Update codeql-buildscript.sh
Update script name
2023-11-27 12:14:38 -05:00
hathach e54a2c4f3c
rename build_family.py to build_make.py 2023-11-23 11:46:39 +07:00
Brian 490343b4d3 Add CodeQL Workflow for Code Security Analysis
Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
- Runs daily.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for git submodules, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/).

Signed-off-by: Brian <bayuan@purdue.edu>
2023-10-29 15:28:27 -04:00
Brian 3cc82d656e Add CodeQL Workflow for Code Security Analysis
Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
- Runs daily.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for git submodules, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/).

Signed-off-by: Brian <bayuan@purdue.edu>
2023-10-20 01:02:27 -04:00
Brian b8ae3d55d4 Add CodeQL Workflow for Code Security Analysis
Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
- Runs daily.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for git submodules, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/).

Signed-off-by: Brian <bayuan@purdue.edu>
2023-10-18 16:50:07 -04:00
Brian d6acbd0ea5 Add CodeQL Workflow for Code Security Analysis
Add CodeQL Workflow for Code Security Analysis

This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats.

We added a new CodeQL workflow file (.github/workflows/codeql.yml) that
- Runs on every push and pull request to the main branch.
- Excludes queries with a high false positive rate or low-severity findings.
- Does not display results for third-party code, focusing only on our own codebase.

Testing:
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.

Deployment:
Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps:
1. Under the repository name, click on the Security tab.
2. In the left sidebar, click Code scanning alerts.

Additional Information:
- You can further customize the workflow to adapt to your specific needs by modifying the workflow file.
- For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation.

Signed-off-by: Brian <bayuan@purdue.edu>
2023-10-11 19:59:23 -04:00
hathach 8348631bf5
improve esp32 ci, build esp32 with -DDMAX3421_HOST=1 for max3421 testing
revert change in hcd.h
2023-09-28 16:15:31 +07:00
Ha Thach 68c4009bba
Merge branch 'master' into add-in_isr-to-hcd_int_hanlder 2023-09-27 17:01:40 +07:00
hathach 0a4fb6963d
fix build with lpc54 2023-09-27 16:19:39 +07:00
hathach 8cdcd0fa9d fix build and add u5 to ci 2023-09-19 18:35:15 +07:00
hathach 1eb0cb0c65
update readme to include max3421 support 2023-09-11 15:45:26 +07:00
hathach 2dea4ce6a2 add cmake support for samd21.
update ci cmake
2023-09-07 16:58:40 +07:00
hathach bb5d43e9c5
add samd51 to cmake 2023-09-07 15:31:43 +07:00
hathach 088180e3d8
add iar support for lpc43, add lpcxpresso43s67 to hil farm 2023-08-14 20:58:00 +07:00
hathach 8e690df1da
rename hitl to hil 2023-08-09 19:03:56 +07:00
hathach 1268d1a093
update hil test and json (remove troublesome lpc54608), run hil test on ci with IAR build 2023-08-09 18:46:23 +07:00
hathach 3c746e8bb0
add usb serial for hw l412 test 2023-08-04 21:33:44 +07:00
hathach 25bace5e81
add cmake for all board in stm32f4. fix build, also move ci for f4 from makefile to cmake 2023-08-04 12:49:26 +07:00
hathach ef5bd9ee6c
Merge branch 'master' into enhance-bsp 2023-08-04 00:31:12 +07:00
hathach a160da1f2b
add lpc43 family 2023-08-03 17:19:47 +07:00
hathach 40833b585b
enable flto for ra makefile
- remove ra from ci make build since it is already in cmake ci
2023-08-01 15:44:54 +07:00
hathach a268e0b7a3
add lpc40 to cmake 2023-07-24 15:18:41 +07:00
hathach 14f1123bbd
remove left-over build_arm 2023-07-01 17:55:36 +07:00
hathach 99e75e6a8a
rework ra build 2023-07-01 12:41:12 +07:00
hathach 06d93e95d1
update hw test l4 2023-06-25 10:15:05 +07:00
hathach 2ecd7c148d
fix ci with lpc55 and kl, move hw test l4 to cmake iar 2023-06-25 09:55:05 +07:00
hathach 15376397b1
run ci with -DCMAKE_BUILD_TYPE=MinSizeRel 2023-06-25 00:05:23 +07:00
hathach 30ccfe0832
more cmake less make 2023-06-24 23:36:52 +07:00
hathach 9b2b4ce647
move some family ci make to cmake 2023-06-24 23:32:24 +07:00
hathach 430f16bf76
move all IAR to cmake 2023-06-24 22:36:53 +07:00
hathach 2a96ef2519
add cmake for f0, f1 2023-06-24 21:47:55 +07:00
hathach 7d0ce5605a
allow to skip CPU_CORE 2023-06-24 19:08:37 +07:00
hathach b59b65d2ed
rename to kinetis_k32l2, rename OPT_MCU_KINETIS_K32 to OPT_MCU_KINETIS_K32L 2023-06-24 18:26:51 +07:00
hathach 268ce0287f
correct cmake iar build 2023-06-16 19:39:03 +07:00
hathach 1419091923
update h7 to cmake, and move iar build to cmake 2023-06-16 16:47:32 +07:00
hathach e754795d3a
fix build warnings 2023-06-16 15:29:34 +07:00
hathach 1a37777f59
fix ci with win/mac 2023-06-15 13:11:21 +07:00
hathach 11fb837b51
fix ci 2023-06-02 16:15:26 +07:00