Merge branch 'dev' into 'main'

Dev

See merge request tedc/doc!1

.gitignore

+*.tmp

README.md

-# doc
+# 同济大学电子设计竞赛 培训网
 
+正在更新中。。。
 
+## 赛事简介
 
-## Getting started
+[赛事宗旨](./contest/purpose.md)
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+[2024赛事安排](./contest/2024/arrangment.md)
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+[2024报名信息](./contest/2024/enrollment.md)
 
-## Add your files
+## 培训流程
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+[培训大纲](./flow/training_brief.md)
 
-```
-cd existing_repo
-git remote add origin https://git.tongji.edu.cn/tedc/doc.git
-git branch -M main
-git push -uf origin main
-```
+[流程与自查清单](./flow/flow_and_checklist.md)
 
-## Integrate with your tools
+## 基础培训
 
-- [ ] [Set up project integrations](https://git.tongji.edu.cn/tedc/doc/-/settings/integrations)
+[焊接与制作](./basic/soldering.md)
 
-## Collaborate with your team
+[元器件识别与选用](./basic/components.md)
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+[读电路图](./basic/read_sch.md)
 
-## Test and Deploy
+[常用电子测量仪器的使用](./basic/measurements.md)
 
-Use the built-in continuous integration in GitLab.
+## 电路设计
 
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+[方案设计](./circuit_design/scheme_design.md)
 
-***
+[电路仿真](./circuit_design/circuit_simulation.md)
 
-# Editing this README
+[电路原理图绘制](./circuit_design/schematic_capture.md)
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+[PCB版图设计](./circuit_design/pcb_design.md)
 
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+[元器件的采购](./circuit_design/component_purchase.md)
 
-## Name
-Choose a self-explaining name for your project.
+[如何进行PCB生产](./circuit_design/pcb_manufacture.md)
 
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+[焊接与组装](./circuit_design/soldering_and_assemble.md)
 
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+[如何调试电路](./circuit_design/circuit_debugging.md)
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+## 电路设计案例
 
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
 
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
 
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+## 单片机入门
 
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
+[常见单片机平台及各自特点](./mcu_dev/mcu_overview.md)
 
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
+[开发板与调试器](./mcu_dev/dev_board_and_debug_probe.md)
 
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+[基于Arduino开发环境的ESP32开发方法](./mcu_dev/esp32_arduino_dev.md)
 
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+[基于Arduino开发环境的STM32开发方法](./mcu_dev/stm32_arduino_dev.md)
+
+[基于VSCode和Platform IO的单片机开发流程](./mcu_dev/mcu_dev_on_vscode.md)
+
+## 单片机开发例程
+
+#### ESP32例程（基于Arduino环境）
+
+[点灯](./mcu_demo/esp32_arduino/blinky.md)
+
+[串口打印](./mcu_demo/esp32_arduino/print.md)
+
+[定时器](./mcu_demo/esp32_arduino/timer.md)
+
+[ADC模拟量采集](./mcu_demo/esp32_arduino/adc.md)
+
+[PWM输出](./mcu_demo/esp32_arduino/pwm.md)
 
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
 
-## License
-For open source projects, say how it is licensed.
 
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

contest/2024/arrangment.md

+# 2024赛事安排
+

contest/2024/enrollment.md

+# 2024 同济大学电子设计竞赛报名信息
\ No newline at end of file

contest/purpose.md

+# 同济大学电子设计竞赛 赛事简介与竞赛宗旨
+
+
+

flow/training_brief.md

+# 同济大学电子设计竞赛培训大纲
+