Commit Graph

410 Commits

Author SHA1 Message Date
hathach ec1a06843c
more try/catch for labeler 2024-04-09 17:37:12 +07:00
hathach cbbfbbb57e
add cpuctl and pinctl to tuh_configure() option for max3421 2024-04-08 13:16:08 +07:00
hathach 252e630433
try catch labeler rest api 2024-04-03 13:05:53 +07:00
Ha Thach 62864d5356
Update labeler.yml 2024-03-28 12:12:07 +07:00
hathach 7f1e327be3
add sudo usbreset 2024-03-26 17:13:02 +07:00
hathach ecea890fdc
use usbreset to reset built-in usb 2.0 hub VIA Labs before each test 2024-03-26 16:56:13 +07:00
hathach 98b8e960aa
Merge branch 'master' into add-tuh-deinit 2024-03-25 17:46:28 +07:00
hathach a555266174
add new labeler workflow 2024-03-25 13:54:35 +07:00
hathach ad5c449f1e
bump up download artifacts to v4 2024-03-22 20:12:25 +07:00
hathach 54e35dd3cf
bump up upload artifact to v4 2024-03-22 18:52:52 +07:00
hathach 3d3bf45102
frdm k64f usb work well, add kinetis_k to ci cmake 2024-02-24 00:36:07 +07:00
hathach d1f77e08ac
build esp32 ci with v5.1 2024-02-02 13:08:42 +07:00
hathach 14d44171b5
bump up to actions/setup-python@v5 2024-01-25 19:13:11 +07:00
hathach 64f86ef8e7
build workflow with hil-test when test/hil changes 2024-01-24 11:32:28 +07:00
hathach 3349e40276 add cmake support for lpc17 2024-01-11 17:32:21 +07:00
hathach c314cb2903
remove usage of linkermap, update checkout to v4 2023-12-18 20:07:17 +07:00
hathach 8633a2643a
update h5 build make/cmake 2023-12-15 18:08:19 +07:00
hathach 84839fa5f1
reset pi4 usb bus before checkout/download, so that we could skip delay 2023-12-14 16:52:45 +07:00
hathach 31c33ca853
tweak usb reset wait time, fix test script with IAR server 2023-12-13 19:18:08 +07:00
hathach b343ac6d0f
reset usb before running test 2023-12-13 19:05:44 +07:00
hathach 19d7d62e80
try to add samd51 to hil pool using doublereset (rpi gpio) and bossac 2023-12-13 18:54:00 +07:00
hathach f986f1f22d
add reset usb bus 2023-12-12 12:23:07 +07:00
hathach b5448a7987
add feather nrf52840 express to hil pool 2023-12-12 11:59:37 +07:00
hathach f5f087e99c
skip iar build for f4 and h7 to save build time 2023-12-11 15:56:48 +07:00
hathach e1142d4527
wrap up s3 hil test 2023-12-11 14:52:21 +07:00
hathach c829116830
extract artifacts to same folder structure as ci build 2023-12-11 14:43:54 +07:00
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