tag 标签: config

相关博文
  • 热度 6
    2014-6-24 11:44
    824 次阅读|
    0 个评论
    In Part 1 , I left off by discussing the industry shift to proactively managing tester configurations. I'm sure my story triggered memories of a similar season at your company when a more global assessment of your test configurations and capacity became essential to your survival. If so, how did you first start tracking your configurations back then? Maybe your experience and tool set was like mine described below.   Much like the case today, the test systems in the mid-1990s produced an electronic configuration file or "config file" that contained a rich set of detail on the hardware options in the system. The problem was that config files were readable by only a select few in the test community.   As a Field Product Specialist at Teradyne, I was trained to be one of those few. I spent a great deal of time manually checking and translating those files to not only ensure accurate alignment to system orders and device requirements, but to create readable summaries for sales, purchasing, and management. I also had to make sure important information not included in the config file made it into the orders, summaries, and the like. This work was performed using a variety of familiar formats like text files, spreadsheets, and presentation slides, but many of the details in the original config file were inevitably lost in translation.   While many loathed the config file, I embraced it. I considered it part of what allowed me to have "Specialist" in my title. More importantly, working with config files always provided an opportunity for geek humor by making the proverbial, but likely overused, "secret decoder ring" reference ( figure ). I just did it again.   Config files, often written with text editors or spreadsheets, contain information on how ATE systems will be set up for a particular test.   Not everything was, however, done in a text editor. The most innovative related endeavor at the time was the internal development of a customer tester configuration manager in HTML, to be viewed on what was then a nascent Netscape browser. A clever solution for sure, but one that drove perhaps five page views per month, and really had just two unique visitors: I was one, with the other another test engineer in the office with a similar thing for configurations.   When I look back on those times, I don't really see much that has changed in the area of test capacity management tools and methodologies. The system config files are still esoteric and are complicated even further by the addition of floating feature licensing schemes. The tools used to document tester configurations have changed versions but are also largely the same. Unfortunately, there remains a loss of information and efficiency in the translation and communication process. Perhaps now is the time to bring back that web-based configuration manager!   Dan Hamling is CTO at Team A.T.E.
  • 热度 6
    2013-4-27 12:29
    817 次阅读|
    0 个评论
    Sometimes it is good to keep our development tools and utilities up-to-date, since updates may have the bugs fixed and have more functions. I just replaced my MDK4.6 with MDK4.7a (verson Mar 2013). Fig.1 MDK updated to 4.7a   Surprisingly, I was unable to download the firmware (to a STM32 MCU) with my ULINK2 anymore... The IDE went out of response during program download... Fig.2 A ULINK2 to download program   Fig.3 The IDE went out of response... download program failed On the other hand, the 'COM' LED keeped on... No further response for a long time... Fig.4 The COM LED seemed to be on forever To solve this problem, many people on the Internet could think of downloading older firmware versions to the ULINK2 through the UART port by opening the casing. Fig.5 Pins soldered for UART firmware download   I did not download the old firmware successfully, the LPC2000 flash utility was not working stably after trying for several times, using CP2102 as the USB to TTL interface. Probably the CP2102 had baud rate timing problems... I don't know...   At the end, I found that increasing the 'Max Clock' in the configuration would totally solve the problem!! The default "Max Clock" was 1MHz, if we plug the ULINK2 into the USB, then we can choose "10MHz" as the clock.   Fig.6 Choosing "Max Clock" to be 10MHz, after plugging in the ULINK2   Everything was working fine since then... however, old projects still have to be re-configured before downloading them again to MCUs...
相关资源
  • 所需E币: 0
    时间: 2021-4-13 18:45
    大小: 5.93MB
    上传者: wxlai1998
    树莓派7寸电容屏config文件,已经配置好分辨率ipscan22_局域网IP扫描.rar
  • 所需E币: 0
    时间: 2021-4-13 18:45
    大小: 5.6MB
    上传者: wxlai1998
    强制输出HDMI接口的config配置文件FileZilla-3.7.0.1_SFTP传输工具.rar
  • 所需E币: 0
    时间: 2021-4-13 18:47
    大小: 1008.88KB
    上传者: wxlai1998
    树莓派5寸config文件,已经配置好分辨率putty英文版.rar
  • 所需E币: 0
    时间: 2021-4-13 18:48
    大小: 240.75KB
    上传者: wxlai1998
    树莓派7寸电容屏config文件,已经配置好分辨率SDFormatter_存储卡彻底格式化
  • 所需E币: 0
    时间: 2021-4-13 18:52
    大小: 2.32KB
    上传者: wxlai1998
    树莓派RPI疑难解答Config显示设置项详细说明.rar
  • 所需E币: 1
    时间: 2020-12-10 23:02
    大小: 509.8KB
    上传者: sense1999
    浅谈内核的Makefile、Kconfig和.config文件
  • 所需E币: 0
    时间: 2020-3-2 13:35
    大小: 405.5KB
    上传者: rdg1993
    Config學習关于配置文件选项为配置文件输入所需的设置,可以预设环境选项和其它全局设置。要设置配置文件选项,使用“选项”对话框(“实用工具”>“选项”)。本帮助模块含有一个按字母顺序显示每一选项或相关选项组的配置选项列表:·配置选项名称。·相关变量或值。选项的缺省值显示为斜体。·简单说明。accuracy_lower_bound数值(在1.0e-6和1.0e-4之间)输入一个精确值来覆盖缺省下限0.0001。上限固定为0.01add_java_class_path此选项涉及到有关JAVA环境变量CLASSPATH的选项值,它用于查找J-Link程序中使用的类。可在同一行上指定多个搜索路径,在UNIX中用“:”隔开,在WindowsNT中用“;”隔开。设定此选项后,启动第一个J-Link应用程序时才会生效add_weld_mpyes,noyes-系统在计算质量属性时,包括焊接。no-系统在计算质量属性时,排除焊缝。allow_anatomic_featuresyes,no将此配置文件现象设置为yes,使得下列选项可用:“扭曲”菜单中:“局部拉伸”、“半径圆顶”、“截面圆盖”、“耳”、“唇”。“实体”菜单中:“开槽”、“轴肩”、“凸缘”、“退刀槽”。“基准”菜单中:“计算”。allow_cycle_optimizeyes,no在18.0以前的版本中,有一个孔加工序列参数,允许用户优化孔加工序列CL-数据的循环输出。自版本18.0以来,该参数不再有效。yes-使该参数在序列中可见no-该参数在序列中不可见allow_move_attach_in_dtl_moveyes,no确定……
广告