T1974 000:007.675 SEGGER J-Link V7.22b Log File
T1974 000:007.774 DLL Compiled: Jun 17 2021 17:22:49
T1974 000:007.780 Logging started @ 2023-10-18 02:01
T1974 000:007.785 - 7.788ms
T1974 000:007.793 JLINK_SetWarnOutHandler(...)
T1974 000:007.800 - 0.009ms
T1974 000:007.806 JLINK_OpenEx(...)
T1974 000:009.674 Firmware: J-Link V9 compiled May 7 2021 16:26:12
T1974 000:010.303 Firmware: J-Link V9 compiled May 7 2021 16:26:12
T1974 000:010.430 Decompressing FW timestamp took 104 us
T1974 000:018.966 Hardware: V9.40
T1974 000:018.981 S/N: 69400779
T1974 000:018.988 OEM: SEGGER
T1974 000:018.993 Feature(s): RDI, GDB, FlashDL, FlashBP, JFlash
T1974 000:020.754 TELNET listener socket opened on port 19021
T1974 000:020.843 WEBSRV Starting webserver
T1974 000:020.939 WEBSRV Webserver running on local port 19080
T1974 000:020.946 - 13.142ms returns "O.K."
T1974 000:020.958 JLINK_GetEmuCaps()
T1974 000:020.961 - 0.005ms returns 0xB9FF7BBF
T1974 000:020.968 JLINK_TIF_GetAvailable(...)
T1974 000:021.313 - 0.348ms
T1974 000:021.320 JLINK_SetErrorOutHandler(...)
T1974 000:021.323 - 0.004ms
T1974 000:021.334 JLINK_ExecCommand("ProjectFile = "E:\dlm_fw\Board\test\ads1110_test\MDK-ARM\JLinkSettings.ini"", ...).
T1974 000:028.694 - 7.373ms returns 0x00
T1974 000:028.752 JLINK_ExecCommand("Device = STM32F407ZGTx", ...).
T1974 000:029.337 Device "STM32F407ZG" selected.
T1974 000:029.577 - 0.823ms returns 0x00
T1974 000:029.589 JLINK_GetHardwareVersion()
T1974 000:029.593 - 0.005ms returns 94000
T1974 000:029.597 JLINK_GetDLLVersion()
T1974 000:029.600 - 0.004ms returns 72202
T1974 000:029.605 JLINK_GetOEMString(...)
T1974 000:029.609 JLINK_GetFirmwareString(...)
T1974 000:029.614 - 0.006ms
T1974 000:030.018 JLINK_GetDLLVersion()
T1974 000:030.025 - 0.008ms returns 72202
T1974 000:030.029 JLINK_GetCompileDateTime()
T1974 000:030.032 - 0.004ms
T1974 000:030.105 JLINK_GetFirmwareString(...)
T1974 000:030.110 - 0.006ms
T1974 000:030.171 JLINK_GetHardwareVersion()
T1974 000:030.176 - 0.006ms returns 94000
T1974 000:030.229 JLINK_GetSN()
T1974 000:030.234 - 0.006ms returns 69400779
T1974 000:030.285 JLINK_GetOEMString(...)
T1974 000:030.385 JLINK_TIF_Select(JLINKARM_TIF_SWD)
T1974 000:031.877 - 1.498ms returns 0x00
T1974 000:031.887 JLINK_HasError()
T1974 000:031.896 JLINK_SetSpeed(5000)
T1974 000:032.143 - 0.249ms
T1974 000:032.148 JLINK_GetId()
T1974 000:032.580 InitTarget() start
T1974 000:032.589 J-Link Script File: Executing InitTarget()
T1974 000:043.670 InitTarget() end
T1974 000:044.692 Found SW-DP with ID 0x2BA01477
T1974 000:047.985 DPIDR: 0x2BA01477
T1974 000:048.052 Scanning AP map to find all available APs
T1974 000:049.167 AP[1]: Stopped AP scan as end of AP map has been reached
T1974 000:049.230 AP[0]: AHB-AP (IDR: 0x24770011)
T1974 000:049.286 Iterating through AP map to find AHB-AP to use
T1974 000:050.562 AP[0]: Core found
T1974 000:050.624 AP[0]: AHB-AP ROM base: 0xE00FF000
T1974 000:051.363 CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
T1974 000:051.422 Found Cortex-M4 r0p1, Little endian.
T1974 000:153.174 -- Max. mem block: 0x00010E60
T1974 000:153.645 CPU_ReadMem(4 bytes @ 0xE000EDF0)
T1974 000:154.403 CPU_ReadMem(4 bytes @ 0xE0002000)
T1974 000:155.207 FPUnit: 6 code (BP) slots and 2 literal slots
T1974 000:155.219 CPU_ReadMem(4 bytes @ 0xE000EDFC)
T1974 000:155.841 CPU_WriteMem(4 bytes @ 0xE000EDFC)
T1974 000:156.432 CPU_ReadMem(4 bytes @ 0xE0001000)
T1974 000:157.087 CPU_WriteMem(4 bytes @ 0xE0001000)
T1974 000:157.689 CPU_ReadMem(4 bytes @ 0xE000ED88)
T1974 000:158.251 CPU_WriteMem(4 bytes @ 0xE000ED88)
T1974 000:158.854 CPU_ReadMem(4 bytes @ 0xE000ED88)
T1974 000:159.376 CPU_WriteMem(4 bytes @ 0xE000ED88)
T1974 000:159.982 CoreSight components:
T1974 000:160.044 ROMTbl[0] @ E00FF000
T1974 000:160.052 CPU_ReadMem(64 bytes @ 0xE00FF000)
T1974 000:160.911 CPU_ReadMem(32 bytes @ 0xE000EFE0)
T1974 000:161.681 ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
T1974 000:161.726 CPU_ReadMem(32 bytes @ 0xE0001FE0)
T1974 000:162.484 ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
T1974 000:162.495 CPU_ReadMem(32 bytes @ 0xE0002FE0)
T1974 000:163.289 ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
T1974 000:163.300 CPU_ReadMem(32 bytes @ 0xE0000FE0)
T1974 000:164.052 ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
T1974 000:164.063 CPU_ReadMem(32 bytes @ 0xE0040FE0)
T1974 000:165.115 ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
T1974 000:165.127 CPU_ReadMem(32 bytes @ 0xE0041FE0)
T1974 000:165.951 ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
T1974 000:166.393 - 134.250ms returns 0x2BA01477
T1974 000:166.406 JLINK_GetDLLVersion()
T1974 000:166.410 - 0.005ms returns 72202
T1974 000:166.414 JLINK_CORE_GetFound()
T1974 000:166.418 - 0.005ms returns 0xE0000FF
T1974 000:166.490 JLINK_GetDebugInfo(0x100 = JLINKARM_ROM_TABLE_ADDR_INDEX)
T1974 000:166.499 Value=0xE00FF000
T1974 000:166.503 - 0.015ms returns 0
T1974 000:166.583 JLINK_GetDebugInfo(0x100 = JLINKARM_ROM_TABLE_ADDR_INDEX)
T1974 000:166.588 Value=0xE00FF000
T1974 000:166.593 - 0.012ms returns 0
T1974 000:166.597 JLINK_GetDebugInfo(0x101 = JLINKARM_DEBUG_INFO_ETM_ADDR_INDEX)
T1974 000:166.600 Value=0xE0041000
T1974 000:166.605 - 0.009ms returns 0
T1974 000:166.612 JLINK_ReadMemEx(0xE0041FD0, 0x20 Bytes, Flags = 0x02000004)
T1974 000:166.631 CPU_ReadMem(32 bytes @ 0xE0041FD0)
T1974 000:167.313 Data: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...
T1974 000:167.322 - 0.712ms returns 32 (0x20)
T1974 000:167.328 JLINK_GetDebugInfo(0x102 = JLINKARM_DEBUG_INFO_MTB_ADDR_INDEX)
T1974 000:167.332 Value=0x00000000
T1974 000:167.337 - 0.010ms returns 0
T1974 000:167.341 JLINK_GetDebugInfo(0x103 = JLINKARM_DEBUG_INFO_TPIU_ADDR_INDEX)
T1974 000:167.344 Value=0xE0040000
T1974 000:167.349 - 0.009ms returns 0
T1974 000:167.353 JLINK_GetDebugInfo(0x104 = JLINKARM_DEBUG_INFO_ITM_ADDR_INDEX)
T1974 000:167.356 Value=0xE0000000
T1974 000:167.361 - 0.009ms returns 0
T1974 000:167.365 JLINK_GetDebugInfo(0x105 = JLINKARM_DEBUG_INFO_DWT_ADDR_INDEX)
T1974 000:167.368 Value=0xE0001000
T1974 000:167.373 - 0.009ms returns 0
T1974 000:167.377 JLINK_GetDebugInfo(0x106 = JLINKARM_DEBUG_INFO_FPB_ADDR_INDEX)
T1974 000:167.380 Value=0xE0002000
T1974 000:167.384 - 0.009ms returns 0
T1974 000:167.388 JLINK_GetDebugInfo(0x107 = JLINKARM_DEBUG_INFO_NVIC_ADDR_INDEX)
T1974 000:167.392 Value=0xE000E000
T1974 000:167.396 - 0.009ms returns 0
T1974 000:167.400 JLINK_GetDebugInfo(0x10C = JLINKARM_DEBUG_INFO_DBG_ADDR_INDEX)
T1974 000:167.404 Value=0xE000EDF0
T1974 000:167.408 - 0.009ms returns 0
T1974 000:167.412 JLINK_GetDebugInfo(0x01 = Unknown)
T1974 000:167.415 Value=0x00000001
T1974 000:167.420 - 0.009ms returns 0
T1974 000:167.424 JLINK_ReadMemU32(0xE000ED00, 0x1 Items)
T1974 000:167.431 CPU_ReadMem(4 bytes @ 0xE000ED00)
T1974 000:167.892 Data: 41 C2 0F 41
T1974 000:167.902 Debug reg: CPUID
T1974 000:167.907 - 0.484ms returns 1 (0x1)
T1974 000:167.912 JLINK_GetDebugInfo(0x10F = JLINKARM_DEBUG_INFO_HAS_CORTEX_M_SECURITY_EXT_INDEX)
T1974 000:167.916 Value=0x00000000
T1974 000:167.921 - 0.010ms returns 0
T1974 000:167.925 JLINK_HasError()
T1974 000:167.930 JLINK_SetResetType(JLINKARM_CM3_RESET_TYPE_NORMAL)
T1974 000:167.934 - 0.005ms returns JLINKARM_CM3_RESET_TYPE_NORMAL
T1974 000:167.938 JLINK_Reset()
T1974 000:167.949 CPU is running
T1974 000:167.955 CPU_WriteMem(4 bytes @ 0xE000EDF0)
T1974 000:168.523 CPU is running
T1974 000:168.533 CPU_WriteMem(4 bytes @ 0xE000EDFC)
T1974 000:169.158 Reset: Halt core after reset via DEMCR.VC_CORERESET.
T1974 000:170.076 Reset: Reset device via AIRCR.SYSRESETREQ.
T1974 000:170.087 CPU is running
T1974 000:170.093 CPU_WriteMem(4
ads1110驱动代码在stm32hal库的应用
需积分: 0 57 浏览量
更新于2023-11-07
1
收藏 11.04MB ZIP 举报
标题 "ads1110驱动代码在stm32hal库的应用" 暗示了本文将探讨如何在基于STM32微控制器的项目中使用HAL库来操作ADS1110模数转换器(ADC)。ADS1110是一款高精度、低功耗的12位ADC,适用于各种工业和物联网应用。STM32 HAL库是STMicroelectronics提供的高级抽象层,旨在简化STM32系列MCU的软件开发。
描述中提到的内容表明我们将深入理解如何将ADS1110的驱动代码集成到基于STM32的系统中,利用HAL库的优势进行快速、可靠的通信。这通常包括配置I²C或SPI接口,初始化ADC,读取转换结果,以及可能的中断处理。
我们要了解STM32 HAL库的基础。HAL库提供了一组预定义的函数,用于与STM32的外设进行交互,如GPIO、定时器、串行通信接口等。它使开发者能够以更少的代码量和更高的可移植性来实现功能。
接着,我们将关注ADS1110。这款ADC支持I²C和SPI通信协议。在STM32HAL库中,你需要设置相应的通信接口。例如,如果你选择I²C,你需要初始化I2C_HandleTypeDef结构体,配置时钟频率、GPIO引脚和中断,然后调用HAL_I2C_Init()初始化接口。
在配置完I²C或SPI后,你需要创建一个驱动结构体,定义ADS1110的地址和其他参数。接下来,编写读写函数,如`HAL_I2C_Master_Transmit()`和`HAL_I2C_Master_Receive()`,以执行寄存器配置和数据读取。
`Src`和`Inc`目录可能包含项目的源代码和头文件。在`Src`目录下,你可能会找到`ads1110.c`和`ads1110.h`文件,分别包含了驱动的实现和接口定义。在`ads1110.c`中,你可能看到函数如`ads1110_init()`、`ads1110_read()`等,它们实现了与ADS1110的通信。
`Drivers`目录可能包含HAL库的外设驱动,如`stm32f4xx_hal_i2c.c/h`或`stm32f4xx_hal_spi.c/h`,这些驱动负责与硬件的底层交互。
`.gitignore`文件列出了一些在版本控制中不需要跟踪的文件类型,例如编译产生的中间文件。
`.mxproject`可能是Keil μVision的项目文件,它定义了工程的编译设置、目标设备、包含的源文件等。
`MDK-ARM`可能是一个子目录,包含使用MDK-ARM(RealView Microcontroller Development Kit)IDE的项目文件。
总结来说,这个主题涵盖了STM32HAL库的使用,特别是针对ADS1110的驱动代码实现,涉及I²C或SPI通信协议的配置、ADC读取,以及如何在STM32项目中组织和管理代码。通过理解这些知识点,开发者可以有效地在STM32平台上集成和使用ADS1110,实现高精度的模拟信号数字化。

lh^2
- 粉丝: 1
最新资源
- 深度学习面试问题及对应《深度学习》中文版页码汇总
- TouchSocket-C#资源
- Ingenious 工作流引擎-PHP资源
- AirPower-Transformer-JavaScript资源
- com-计算机二级资源
- 毕业设计-毕业设计资源
- 人工智能ChatGPT-5:新一代语言模型的技术革新与广泛应用:性能飞跃、多模态能力及社会影响综述
- olympic_predict-美赛资源
- 2025年c语言代码-蓝桥杯资源
- assembly_learning-汇编语言资源
- 深度学习之图像分类数据集:动植物图像分类数据集(10分类)
- 小熊猫C++-C++资源
- eova-Java资源
- CnOCR-Python资源
- swift-Swift资源
- matlab学习-Matlab资源