Summary: Flexible debug resource working with global and local engineering teams to resolve system
2017-06-06 17:50
product teams on ARM based embedded SoC products. Responsibilities include: 1. Build, grow
2010-04-17 08:48
Demonstrate strong leadership and work well with cross-functional teams 7. Good listening, writing
2017-06-06 17:46
an external LPO. We would need to consult L3 HW/FW teams if you try to move forward with a design where
2018-11-22 17:12
手上有一块Nucleo-L031K6拇指板，烧了几个例程进去后想恢复出厂状态但是在STM32Cube_FW_L0固件包里没有找到相关例程请问ST官方是否有提供出厂程序的源代码或者二进制文件？如果有，请问在哪里能找到？谢谢各位-------------------------------------更新：应该是GPIO_IOToggle_VariableFreq这个工程具体见6#
2019-01-11 09:08
我们又在一起了，因为我以前的讨论是没有最终答案的封闭。有任何关于（Flash）的数据保留在焊接5lp PSoC？更多信息见这个帖子：（回流）的预编程PSoCs焊接最好的问候，戴维注：不幸的是，我的讨论是封闭和柏树标志着“正确答案/有帮助”，没有回答实际问题…以上来自于百度翻译 以下为原文Here we go again, since my previous discussion was closed without a final answer. Is there any information regarding (flash) data retention during soldering for PSoC 5LP? For more information see this thread: (Reflow) Soldering of pre-programmed PSoCs Best regards,David p.s.: it's unfortunate that my discussion was closed and Cypress marked answers has "correct/helpful" that didn't answer the actual question...
2018-08-18 03:41
用STM32f407discovery 的st link为其他单片机下载程序，可能是连接错误，导致stlink无法给discovery板上的单片机下载程序了，用stm32 stlink uility下载.bin但是无法连接到stlink。请问有人遇到这样问题么，有没有大虾可以解决？
2018-09-19 09:25
我看到所有评估和免费许可证都是节点锁定许可证。是否有任何FlexLM类型的许可证可用作临时使用许可证？以上来自于谷歌翻译以下为原文I see that all of the evaluation and no-charge licenses are node-locked licenses.Are there any FlexLM type licenses available as temporary use licenses?
2018-12-19 11:09
嗨，大家好，在一些帖子中，当省略32千赫时钟时，会出现问题。这个问题显然取决于该版本的SDK和FX3。今天你可以推荐安全地省略32 kHz时钟时，无需在待机模式下一个看门狗吗？当做格恩特 以上来自于百度翻译 以下为原文Hi all, in some postings problems are indicated when omitting the 32 KHz clock. The problems obviously depend on SDK and FX3 silcon revisions. Can you today recommend to safely omit the 32 Khz clock when there is no need for a watchdog in standby mode? Regards Günter
2019-02-20 14:06
我正在尝试从CyPress PSoC 4.1构建BLUE固件映像，但是在BooDoabable文件分配中有问题。以下错误：“组件中的错误：可引导加载”。引用的引导加载程序无效。在引导加载组件中验证Bootloader依赖性是否正确，然后生成项目。无效的引导加载程序HEX文件。无法读取HEX文件（C:\demo\Bootloader）。Cyrj.CaseVe01 \Bootloader。CysN\CordExt0\ARMYGCCS943\Debug \Bootloader。这条道路不存在。”可引导加载的组件必须有一个与之相关的引导加载程序设计。BootloadLable的定制器中的引用必须指向Bootloader设计中的有效*.HEX和*.ELF文件。我试图从命令行构建BLE，但由于BooLoad选择了相对路径，生成过程没有完成。请建议我使用CyPress PSoC4.1从命令行构建BLE固件映像。 以上来自于百度翻译 以下为原文I am trying the Build BLE firmware image from Cypress Psoc 4.1 but having issue in Bootloadable file assignment. Below error: "Error in component: Bootloadable. The referenced Bootloader is invalid. Verify the Bootloader dependency is correct in the Bootloadable Component, then build project. Invalid bootloader hex file. Unable to read the hex file (C:\demo\bootloader.cyprj.Archive01\bootloader.cydsn\CortexM0\ARM_GCC_493\Debug\bootloader.hex). The path does not exist." Bootloadable components must have an associated bootloader design to build with. The reference in the Bootloadable's customizer must point to valid *.hex and *.elf files from a Bootloader design." I am trying to build BLE from command line but since bootloader picking relative path, build process does not go through. Please suggest me alternative option to build BLE firmware image from command line using cypress Psoc 4.1..
2019-07-02 06:42
