Freescale OSBDM JM60仿真器

OSBDM-JM60 - 9S08JM60 Based OSBDM — It includes interfaces and
firmware applied to all the targets supported by the previous open source
BDMs.

It includes new features and JTAG operations. It provides interface to
9S08, 9RS08, Coldfire V1, V2, V3 and V4 target devices.

It also includes JTAG connections for DSP56800E.

OSBDM-JM60 Features

The open source BDM is implemented with the following features:

? USB 2.0 compliant communication port with standard B or mini B type
connector

? The target power is determined by the MCU when OSBDM is
included on a target board. Target power option of 5V or 3.3V
output.
   Power
limited to USB requirements. Adjustable voltage
output optional. Embedded OSBDM does not have the
target power option

? Coldfire V2, V3, and V4 interface with port options

? BGND interface
with options to support 9S08, 9RS08, and Coldfire V1 targets

? JTAG
interface to support DSC targets and JTAG option operation on Coldfire V2,V3, V4
targets

? +12Vpp generation provided for 9RS08 target

? Status and
Target Power Indicators

? Boot load option to update firmware using USB
connection

? Debug port for the JM60 BDM controller

? Low cost
design, easy to embed on target boards requiring only one interface
type

? Optional USB serial port application to pass target serial data to
host Personal Computer (PC) with USB connection

OSBDM Development Port Interfaces

This section describes the individual development ports. Note that only one
port type is applied to a target at any time.


BGND
Interface

The BGND interface provides the standard 6 pin connection for the single
wire BGND signal type development port.

Target types that apply this development port are the 9S08, RS08, and
Coldfire V1.

+V_TRG, TBGND, TRG_RST*, and Ground are applied by this port type.

The BGND interface applies U4 as the signal transceiver.

U4 is a 74LVC1T45 logic gate with voltage level shifting features.

Operation on the target side (+V_TRG) is 1.8V to 5.5V.

The JM60 side is always +5V from the +5V_SW signal.

JM60 signals TBGND_EN, TBGND_IN, and TBGND_OUT provide the communication
and control for this interface.

All these signals are associated with JM60 timer channels for precise
timing capability to a 41.67ns time step period.

For more information on the input and output ports, refer to the Signal
Chart section.

TBGND_ EN
provides directional control for transmit or receive operations.

The signal is logic high for transmit output and logic low to receive
input.

JM60 timer 2 channel 1 provides the primary signal direction control
during the communication with the target.

The idle condition is low so that the interface is not driven unless the
communication is intended.

During the communication, the direction is fixed to output the command to
the target.

During the reception, the signal is timed in edge aligned PWM mode to provide
the BGND start pulse prior to the target reply input.

TBGND_OUT
provides the transmit signal output from the JM60 to the target.

Timer 2 channel 0 controls this signal in edge aligned PWM mode.

For data transmission, the timer channel will output an active low
signal with a time period that represents a logic one bit value or logic 0
bit value.

In receive mode, the timer channel will provide a low output for the
start bit on the BGND signal and then provide timing internally for the reply
signal input time window.

TBGND_IN
provides receive signal input from the target to the JM60.

Timer 1 channel 3 is applied to measure the input signal duration in capture
mode (25Mhz BDC clock maximum).

This operation provides the timing to determine a logic 1 or 0 bit value
input from the target.

RS08 type targets apply a lower speed communication technique
that inputs the JM60 port value (sample mode) instead of using the timer
capture.

This is due to the RS08 will not provide a stable input signal after the
start bit generation and creates false timer capture edges.

Other undefined target types may exhibit the same issue and may apply
sample mode, if required (10MHz BDC clock maximum).

NOTE The TBGND_OUT and TBGND_IN
signals are connected with resistor R1. R1 provides isolation between the 2
timer channels.

Freescale OSBDM JM60仿真器,码迷,mamicode.com

时间: 2024-10-13 23:47:52

Freescale OSBDM JM60仿真器的相关文章

监听turtlesim仿真器,发送数据到实际的机器人--20

摘要: 原创博客:转载请表明出处:http://www.cnblogs.com/zxouxuewei/ 1.0.本教程教你写实际的ros程序,控制自己的机器人.采用的是PC端的ubuntu+ros.终端为了能够使用低成本的里程计 ,陀螺仪 ,加速度计,超声波等传感器,采用STM32控制器.两者通过串口通信,交互数据.所有代码都有认真学习的必要.前提是你以经在ros.wiki或者书本上了解了ros 下的 话题,消息,节点等名词. 2.0.由于ros官方采用tuitlesim仿真器,我们再次也按照这

在SDK中使用Ubuntu仿真器

Ubuntu仿真器是开发过程中非常有用,尤其是在没有任何Ubuntu设备时.在将仿真器附加到SDK后,你便可以在上面运行程序,安装点击数据包,等等,类似在物理设备上的操作一样. 在这里,您可以了解如何从Ubuntu SDK使用Ubuntu仿真器,包括: 创建仿真器 启动仿真器 将仿真器附加到SDK 打开连接到仿真器的根shell 注意:Ubuntu仿真器正在进行快速开发,包括其在SDK中的支持.因此保持敏捷,时刻关注新信息,以及时刻注意最新变化! 提示:为获得一流的Ubuntu仿真器和SDK体验

JLINK仿真器与ST-LINK仿真器的安装与配置.pdf

工欲善其事,......stm32的开发环境搭建 观看地址  说到仿真器,首先要了解一下JTAG. JTAG协议 JTAG(Joint Test Action Group,联合测试行动小组)是一种国际标准测试协议(IEEE 1149.1兼容),主要用于芯片内部测试.现在多数的高级器件都支持JTAG协议,如ARM.DSP.FPGA器件等.标准的JTAG接口是4线:TMS. TCK.TDI.TDO,分别为模式选择.时钟.数据输入和数据输出线. 相关JTAG引脚的定义为: TMS:测试模式选择,TMS

如何使用SDK在Ubuntu设备(包括仿真器和桌面)上运用应用程序

简介 有三种运行通过SDK创建的应用程序的方式:在桌面上,在联网的Ubuntu设备上,以及在仿真器中.这些方式为互补性方式,因为各有优缺点.您首先将了解如何管理SDK的设备类型,以及哪一个类型用于测试应用程序的不同方面. 设置设备工具包 设备工具包是SDK的一个重要概念:它们使您能够为数个设备和架构生成应用程序,无论您的开发环境如何.如果您还未添加任何设备工具包也不必担心,在您启动新项目时,您始终可以创建新工具包. 请查看工具包上的文件详细了解这些类型,或只需遵循后续步骤. 在首次创建项目时,S

CCS v5 无法启动解决办法及Launchpad仿真器电脑无法识别解决方法

安装ccs_setup_5.1.1.00028.exe后(无论是自己装eclipse还是在原来的基础上安装eclipse的插件),ccs5的应用无法打开,错误为:An error has occurred.See the log file .\workspace\.metadata\.log. 本现象可以通过重装Microsoft VC redistributable package解决.安装包在下面的路径: (你的CCS V5安装文件)\baserepo\里重新安装 vcredist_x86_

HoloLens模拟器仿真器与文档现已向开发者们开放

HoloLens仿真器与文档现已向开发者们开放 直接上链接吧:http://mt.sohu.com/20160301/n438961462.shtml

火速提升Android仿真器的运行速度 ——仿真器Genymotion

一.问题概述 Android开发中会使用仿真器测试应用,但不管你使用Eclispe ADT还是Android Studio仿真器都是基于arm架构的,运行起来都很慢,光启动就要花费很多时间,都不知道它在加载个啥.今天就向大家推荐一个新的基于Oracle VM VirtualBox的仿真器——Genymotion,它是目前最火的仿真神器,运行速度甚至比真机还快. Genymotion提供两种版本个人版和商业版,个人版是免费的,商业版支持很多特性,当然是收费的,不过个人版已经满足了测试应用的需要,反

TMS320F28335项目开发记录2_CCS与JTAG仿真器连接问题汇总

CCS与仿真器连接问题 实际使用过程中.仿真器和CCS连接可能出现这样或那样的问题,或许你的连接非常成功,没碰到过什么问题.但我的问题的确不少,可能与电脑配置有关吧,也可能与人品有关吧. 以下的自己的一些错误和解决方法总结.不一定对,但也算是一种解决方法.分享给大家: 问题: 1. jtag连接不上,报错: The controller has detected a dead JTAG clock. The user must turn-on or connect the JTAG clock

在freescale mx6q平台上添加spi资源

1:配置管脚为SPI功能 在board-mx6q_sabresd.h的最后添加,复制被重定义 (以添加SPI2为例) [cpp] view plaincopy <span style="font-size:18px;">        MX6Q_PAD_EIM_CS0__ECSPI2_SCLK, MX6Q_PAD_EIM_CS1__ECSPI2_MOSI, MX6Q_PAD_EIM_OE__ECSPI2_MISO, MX6Q_PAD_CSI0_DAT11__ECSPI2_S