Joral Technologies | Software Supplier Company

Subscribe: RSS Feed Entries Feed (RSS) or RSS Feed Comments Feed (RSS).

February 1, 2012

KEIL MDK-ARM v4.23 Available

Cambridge, UK: ARM® announces the immediate release of MDK-ARM v4.23.

The Keil MDK-ARM is a complete C/C++ software development environment for ARM processor-based microcontroller applications. It includes debug and trace capabilities, and middleware components for a wide range of ARM Cortex-M processor-based microcontrollers.

MDK-ARM v4.23 includes the emWin GUI library, allowing the creation of sophisticated graphical user interfaces for embedded devices. This version also introduces middleware support for the Freescale Kinetis K60 device series. Both the GUI library and additional middleware support are available in the MDK-Professional Edition.

MDK-ARM v4.23 extends the device support for the following microcontrollers:

  • Analog Devices ADuC7124 and ADuC7126
  • Fujitsu MB9BF1xxx, MB9BF2xxx, MB9BF3xxx, MB9BF4xxx, MB9BF5xxx, and MB9BF6xxx
  • Nuvoton Mini51LAN, Mini51ZAN, Mini52LAN, Mini52ZAN, Mini54LAN, and Mini54ZAN
  • ST STM32L152VD, STM32L152ZD, STM32L162VD, and STM32L162ZD
  • Toshiba TMPM342FYXBG

November 21, 2011

STMicroelectronics STM32: Cortex™-M4 Lab

Introduction:
The purpose of this lab is to introduce you to the STMicroelectronics Cortex™-M4 processor family using the ARM® Keil™ MDK toolkit featuring the IDE ?Vision®. We will use the Serial Wire Viewer (SWV) and ETM trace on the STM3240G-EVAL evaluation board from STMicroelectroncs. At the end of this tutorial, you will be able to confidently work with STM32 processors and MDK. Keil offers a similar board: MCBSTM32F400™. Examples are provided for both boards.
Keil MDK comes in an evaluation version that limits code and data size to 32 Kbytes. Nearly all Keil examples will compile within this 32K limit. The addition of a license number will turn it into the full, unrestricted version. Contact Keil sales for a temporary full version license if you need to evaluate MDK with programs greater than 32K. MDK includes a full version of Keil RTX™RTOS. No royalty payments are required. RTX source code is now included with all versions of Keil MDK™.

Download PDF Here. STM3240G4_LAB

October 31, 2011

NEW BRAND IAR LPC11U14 KickStart Kit.

IAR KickStart Kit for LPC11U14

Complete starter kit for NXP’s LPC11U14 with evaluation board, tools, IAR J-Link Lite debug probe and example projects. 

 

LPC11U14-SK evaluation board

  • Mounted with NXP Semiconductors’LPC11U14 device
  • Debug and power up the board with J-Link Lite
    - a small debug probe for ARM devices
  • Standard 19-pin JTAG/SWD connector (SWD1)
  • 9-pin Cortex Debug connector (SWD2)
  • Small LCD
  • USB connector
  • USART routed to DB9 connector
  • UXT connector
  • User, Wake-up and Reset buttons
  • 2x User LEDs
  • Power LED
  • Analog trimpot wheel
  • Buzzer
  • Prototyping area
  • Temp sensor
  • RoHS compliant

Part Number: LPC11U14-eval

For a price quote please contact sales@joral.ca or call 1-877-465-6725.  Ask for Robert Campbell

 

October 25, 2011

ASHLING New High Performance Debug and Trace Probe for ARM™ devices

October 2011:

To coincide with the 2011 ARM Technology conference in Santa Clara CA Ashling
Microsystems has launched a new high performance Real Time Debug and Trace Probe for ARM™devices
The new Vitra-XD Debug Probe is the world’s highest performing Debug Probe for Embedded Development
on ARM™ devices. With Trace capture rates up to 400MHz DDR and a massive 504GB on-board Trace
storage memory Vitra-XD allows Extended Trace Capture (users can record time-stamped data for up to
1564 hours) and non-intrusive Software Profiling and Code-Coverage (no code instrumentation required).
Vitra-XD is used in conjunction with PathFinder-XD, Ashling’s Eclipse based C/C++ source-level debugger.
Commenting on the product release, Hugh O’Keeffe, Engineering Director of Ashling Microsystems, said
“The Performance and Trace capacity of Vitra-XD are unprecedented in the Development Tools industry. We
believe Vitra-XD will advance the state of the art for Software Debug and Analysis tools for complex,
performance critical and safety critical applications where software reliability is of the utmost importance and
cannot be compromised.”

The Vitra-XD datasheet : PF-XD-Embedded-Linux-Debugging_PR_DEC10

October 12, 2011

Keil Announces STM32 F2 and STM32 F4 Evaluation Boards

Cambridge, UK: Keil™ introduces the MCBSTM32F200 and MCBSTM32F400 Evaluation Boards for the STMicroelectronics STM32 F2 and STM32 F4 series of microcontrollers.

The MCBSTM32F200 board features an STM32F207IG ARM® Cortex™-M3 processor-based microcontroller which offers 1MB Flash and 128KB RAM on-chip memory. The MCBSTM32F400 features an STM32F407IG Cortex-M4 processor- based microcontroller with 1MB Flash and 192KB RAM on-chip memory.

In addition, both evaluation boards are populated with 8MB NOR Flash, 512MB NAND Flash, 2MB SRAM, and 8KB I2C EEPROM with an NFC interface. They provide a color QVGA LCD and interfaces for SD Card, CAN, 10/100 Ethernet and Full/High speed USB. The boards also feature a 3-axis digital Accelerometer, a 3-axis digital Gyroscope, a digital microphone, and a digital VGA camera.

Datasheet: PA Keil_supports_STM32F200_F400

October 3, 2011

August 2011 FlashRunner Device List

DC10385 FlashRunner Device List August 2011

September 2, 2011

Freescale Kinetis Lab Monday, August 15, 2011

The purpose of this lab is to introduce you to the Freescale Kinetis Cortex-M4-based processor using the Keil MDK-ARM toolkit featuring the µVision IDE. This lab demonstrates the use of Serial Wire Viewer (SWV) and ETM trace on the Kinetis K40 and K60 processor.

DOWNLOAD LAB: kinetis_lab2

August 2, 2011

IAR Embedded Workbench for ARM. Highlights in version 6.20/6.21

  • Support for ARM Cortex-A8 and ARM Cortex-A9
  • Subversion integration
  • Power breakpoints
  • Filtering power consumption data
  • Log power samples to file
  • Fast power sampling
  • Automatic selection of printf/scanf formatter
  • Support for CMSIS-DSP library
  • ST-LINK v2 integration
  • XDS100 integration

For customers that have current support you can find updates for your EWARM development tools
http://supp.iar.com/Updates/?product=EWARM

If you would like to update your IAR EWARM development tools please contact us. sales@joral.ca
or 1-866-465-6725.

July 4, 2011

The SMH Technologies Newsletter

SMHighlights

 

IT 10/0571

  The SMH Technologies Newsletter

July 2011 

 
One of the biggest challenges facing manufacturers in automotive and other industries is how to reduce the costs of production. 

 

One area that is receiving close attention is the programming of microprocessors and memories on PCBs. This is a time-consuming task, as the lines must wait for each programming cycle to finish before moving onto the next one.

A board containing a Freescale MC68HC908LJ24 processor typically takes 14 seconds to programme using a normal in-system programmer (ISP). That is a long time on a production line, and time equals cost.

This problem has been growing over the past decade, particularly in the automotive sector, where more electronics are being used in not just high-end cars, but in the low-end mass market where price is a critical factor. And with an increased focus on using electronics for car safety and infotainment features, the situation is likely to become worse rather than better.

The norm for a production line is to use an in-system programmer, but in the past many of these have been inflexible in their approach by being linked to only a small number of manufacturers of electronics components. They are also typically limited in that they only programme one board at a time.

There is thus a need to carry out parallel programming. This is becoming common in not only production environments, but also in home appliances and other major industrial manufacturing. Many of these still programme a board at a time but if they use panels of boards, the timesavings can be dramatic. Even a small four-board ISP quarters the programming time and reduces the positioning and connection time on top of that. This positioning and connection time is cut even further for eight and 16 panel programmers.

In fact, the latest in-system programmers are not only faster when it comes to programming (and can programme multiple boards in one go), but can also handle devices from multiple manufacturers.

Put into a real application, the financial savings can be large. As mentioned previously, the board containing a Freescale MC68HC908LJ24 processor typically takes 14 seconds to programme, but this is cut to 3.6 seconds using, for example, a FlashRunner ISP from SMH Technologies.

If there are 12,000 boards that need programming at a production cost of about $60 per hour, this can result in a saving of over $2000 for the whole batch.

The speed for each cycle depends on the complexity of the programming protocols. The machine can adjust itself to any programming protocol supported by the device. Typically a cycle can be anything from three seconds for a simple device up to a minute for more complex parts. However, the FlashRunner ISP can achieve the highest speed that can be handled by the device itself and thus there is no other programmer that can do this task more quickly.

For example, it is 7.4 times faster in an erase, programme and verify cycle on a Freescale MCF5211 processor than other products. Likewise, a programme and verify test on an ST Microelectronics ST72F324J6 is 6.1 times faster. On top of that, the recently introduced Quattro model has the ability to programme four boards simultaneously. As some production lines use panels containing eight or 16 boards, Quattro ISPs can handle these in one batch, programming them in blocks of four.

The model that can handle eight boards will run though two programming cycles of four boards each. Likewise, the model that can hold panels of sixteen boards will run through four cycles to complete the job.

Supported devices

Because of the increased use of electronics in automotive and other industries, manufacturers are finding themselves having to source microprocessors from more than one chipmaker.

The growing complexity as well can mean that even a single board can have microprocessors and microcontrollers from multiple manufacturers. This can create a serious bottleneck on a production line, as many in-system programmers are limited in how many different types of microprocessors they can handle.

As such, often a board will have to go through two, three or more different ISPs for all the chips to be properly initialised. Recent developments though have seen ISPs that can handle products from a growing number of chip companies. The FlashRunner programmers, for example, work with all the major silicon producers. About 3000 different microprocessors and other devices are supported. There could even be four microprocessors on a board all from different manufacturers.

FlashRunner is one of the few that can programme all four in one run, although this would be done sequentially because of differences in voltage and other characteristics of each MCU. If the devices are the same, then they are programmed simultaneously.

Making the connection

Most production lines use some form of automatic test equipment (ATE) and a good in-system programmer needs to be able to be controlled by this to streamline the production process. By allowing a programmer to be controlled by general-purpose digital connections from the ATE, the manufacturers can configure the production line so that only one system (the ATE itself) handles the testing and programming. This reduces time by eliminating extra steps, and therefore reduces the chance of errors in manufacturing.

FlashRunner models usually come with both an RS232 and/or Ethernet connection. This allows the programmer to be controlled by a host PC that contains testing software and the specifications for setting up the production line and programmer for a specific job. However, FlashRunner also has a proprietary Control Connector that will link with any system that can write across digital lines. This includes the ATE that controls the programmer through these lines. These lines can be used to start an operation or monitor the status of the programmer, even checking if the last operation passed or failed.

The user can also run script files comprising sequences of commands for programming specific parts. These scripts can be entered through any of the connection methods. With Ethernet and RS232 connections, eventual error codes can also be fed back if failures should happen. And they can be used to transfer files from the PC to the programmer.

The RS232 and Ethernet connection channels feature opto-isolation, so if the ground reference of the system is different to that of the host PC, they can be safely connected without causing any damage. This allows connection to the unit under test (UUT) without damage.

Another challenge that arises from using microprocessors from multiple manufacturers is storing all the files used for programming a specific microprocessor or other device.

A programmer with an SD card connector can solve this problem. An SD card can store up to 2Gbyte and this can contain the licence file for the parts and the serial number of the instrument. An algorithm file would contain all of the specific programming instructions. The card can also store the script file and a log file for monitoring and recording what has been happening during the programming phase. This logging capability may be particularly useful for resolving eventual trouble-shooting issues or to store and track some parameters during the programming.

The FlashRunner programmer communicates with the UUT through a combination of six digital IO lines; two IO lines can be digital or analogue, two programmable output voltage lines can be used to power the UUT, and there is a programmable clock output line. Some models have additional lines for controlling the voltage levels.

Protection of IP is an increasing concern in manufacturing. Protecting IP ensures trade secrets are secured and makes it very difficult for counterfeiters to copy the product. This is becoming increasingly prevalent in some regions of the world and IP protection has become one of the main challenges in many areas of manufacturing. By providing security, a programmer can stop users from accessing or reading the content of the UUT’s firmware during programming unless they have administrators’ rights; thus protecting the IP.

Evolution of FlashRunner

The FlashRunner Quattro is the fourth generation of FlashRunner in-system programmer from SMH, and it shares many features in common with the older members of the family.

Automotive is a major market and a good illustrator of the benefits of using ISPs. For example, the parking sensor of a car comprises of a small board containing a microprocessor. Previously, they used microprocessors pre-programmed with the firmware to control the board. These would then be subject to a lot of manual handling, bringing with it electrostatic discharge problems that could corrupt the data. Also, they were not very flexible for changes to the programming. With SMH’s range of ISPs and test systems, the boards receive a functional test and at the same time the microprocessor is programmed while on the board. Memories too can be programmed on the board in the production line.

The three Quattro models are the FR04-A04, FR04-A08 and FR04-A16, capable of handling four, eight and sixteen boards at once, respectively. Software libraries are available for calling up specific test functions. The programmers are compatible with ATE systems from the likes of Agilent and Teradyne. Each FlashRunner Quattro consists of one carrier board, four programming engines, four de-multiplexing modules, two ISP connectors, Ethernet and RS232 connectivity, and control lines. It is 55mm high on a footprint of 155mm x 165mm.

Manufacturers in automotive and other industries are facing intense competition and pressure to reduce prices. At the same time, designers are using a wider range of programmable products. Additionally, manufacturers have to meet an increasing range of demands from quality to securing IP.

In-system programming is needed to keep many production lines running. Add to this the type of parallel programming mentioned, and the ISP becomes an essential tool in a modern manufacturing line. In fact, the right programmer can significantly increase a manufacturer’s competitiveness.

The image shows an eight panel board: FlashRunner Quattro FR04A08 eight ISP channel system (four parallel channels, each demultiplexed to two channels), panel of eight boards with same device on each. This provides for multiple programming of up to eight devices in two programming cycles.

Single board with multiple devices: FlashRunner Quattro FR04A04 with four ISP channels (four true parallel channels), no ISP demultiplexing. Multiple devices may be programmed, but it is recommended that they are programmed in sequence due to differences in the voltage of each device and other factors.

June 22, 2011

June 22 2011. What’s New in MDK-ARM Version 4.21

  • [New Device Support]
  • [Device Support]
    • Freescale
      • Added: startup code for Freescale K50 series devices, in folder ..\ARM\Startup\Freescale\K50\..
      • Added: system files for Freescale K50 series devices, in folders ..\ARM\Startup\Freescale\K50\ and ..\ARM\INC\Freescale\K50\.
      • Added: device header files for Freescale K50 series devices, in folder ..\ARM\INC\Freescale\K50.
    • Fujitsu
      • Added: startup code for Fujitsu MB9A11x based devices, in folder ..\ARM\Startup\Fujitsu\MB9A110\.
      • Added: system files for Fujitsu MB9A11x based devices, in folders ..\ARM\Startup\Fujitsu\MB9A110\ and ..\ARM\INC\Fujitsu\MB9A110\.
      • Added: device header files for Fujitsu MB9A11x based devices, in folder ..\ARM\INC\Fujitsu\MB9A110\.
      • Added: startup code for Fujitsu MB9A31x based devices, in folder ..\ARM\Startup\Fujitsu\MB9A310\.
      • Added: system files for Fujitsu MB9A31x based devices, in folders ..\ARM\Startup\Fujitsu\MB9A310\ and ..\ARM\INC\Fujitsu\MB9A310\.
      • Added: device header files for Fujitsu MB9A31x based devices, in folder ..\ARM\INC\Fujitsu\MB9A310\.
    • Holtek
      • Added: startup code for Holtek HT32F125x based devices, in folder ..\ARM\Startup\Holtek\HT32F125x\.
      • Added: system files for Holtek HT32F125x based devices, in folders ..\ARM\Startup\Holtek\HT32F125x\ and ..\ARM\INC\Holtek\HT32F125x\.
      • Added: device header files for Holtek HT32F125x based devices, in folder ..\ARM\INC\Holtek\HT32F125x\.
      • Added: flash programming algorithms for Holtek HT32F125x devices, in folder ..\ARM\Flash\.
    • Nuvoton
      • Added: startup code for Nuvoton NUC122 devices, in folder ..\ARM\Startup\Nuvoton\NUC122\.
      • Added: system files for Nuvoton NUC122 devices, in folders ..\ARM\Startup\Nuvoton\NUC122\ and ..\ARM\INC\Nuvoton\NUC122\.
      • Added: device header files for Nuvoton NUC122 devices, in folder ..\ARM\INC\Nuvoton\NUC122\.
      • Updated: startup code for Nuvoton M051 based devices, in folder ..\ARM\Startup\Nuvoton\M051Series\.
      • Updated: system files for Nuvoton M051 based devices, in folders ..\ARM\Startup\Nuvoton\M051Series\ and ..\ARM\INC\Nuvoton\M051Series\.
      • Updated: device header files for Nuvoton M051 based devices, in folder ..\ARM\INC\Nuvoton\M051Series\.
      • Updated: flash programming algorithms for Nuvoton M051 based devices, in folder ..\ARM\Flash\NU_M05x\.
      • Updated: flash programming algorithms for Nuvoton NUC1xx based devices, in folder ..\ARM\Flash\NUC1xx\.
    • NXP
      • Added: startup code for NXP LPC11Uxx devices, in folder ..\ARM\Startup\NXP\LPC11Uxx\.
      • Added: system files for NXP LPC11Uxx devices, in folders ..\ARM\Startup\NXP\LPC11Uxx\ and ..\ARM\INC\NXP\LPC11Uxx\.
      • Added: device header files for NXP LPC11Uxx devices, in folder ..\ARM\INC\NXP\LPC11Uxx\.
      • Updated: startup code for NXP LPC13xx devices, in folder ..\ARM\Startup\NXP\LPC13xx\.
      • Updated: system files for NXP LPC13xx devices, in folders ..\ARM\Startup\NXP\LPC13xx\ and ..\ARM\INC\NXP\LPC13xx\.
      • Updated: device header files for NXP LPC13xx devices, in folder ..\ARM\INC\NXP\LPC13xx\.
  • [Device Simulation]
    • NXP
      • Updated: UART simulation and peripheral dialogs for NXP LPC176x and LPC175x based devices. Removed the FIFOVL regrister functionality which does not exist for these devices.
  • [Board Support]
    • Freescale
      • Added: Blinky, RTX_Blinky, ProgOnce_Cfg, and FlexMem_Cfg examples for Freescale KWIKSTIK board, based on Freescale MK40X256VMD100 device, in folder ..\ARM\Boards\Freescale\KWIKSTIK\.
    • Holtek
      • Added: Blinky and RTX_Blinky examples for Holtek HT32F125x_DVB board, based on Holtek HT32F1253 device, in folder ..\ARM\Boards\Holtek\HT32F12x_DVB\.
    • NXP
      • Added: Blinky and RTX_Blinky examples for Keil MCB11U10 board, based on NXP LPC11U14/201 device, in folder ..\ARM\Boards\Keil\MCB1000\MCB11U10\.
    • Toshiba
      • Added: Blinky and RTX_Blinky examples for Toshiba M374-STK board, based on Toshiba TMPM374FWUG device, in folder ..\ARM\Boards\Toshiba\M374-STK\.
  • [System Viewer Support]
    • Holtek
      • Added: support for HT32F125x based devices in folder ..\ARM\SFD\Holtek\HT32F125x\.
    • NXP
      • Added: support for LPC11Uxx based devices in folder ..\ARM\SFD\NXP\LPC11Uxx\.
  • [RL-ARM Middleware]
    • Added: support for Actel Cortex-M3 SmartFusion devices (Cortex-M3 devices without exclusive access instructions LDREX/STREX/CLREX).
    • Added: support for interrupt priority grouping in Cortex-M3 and Cortex-M4 library.
  • [Flash File System - Enhancements]
    • Added: File update mode (r+, w+, a+) support for FAT
    • Added: FAT File System Journal to protect file system from power failure
    • Added: SDIO and NAND driver for STM32F2xx devices.
    • Added: SD_File and NAND_File examples for ST STM3220-EVAL evaluation board. Examples can be found in ..\ARM\Boards\ST\STM3220F-EVAL\RL\FlashFS folder.
  • [Flash File System - Problems Solved]
    • Corrected: a file modification time in file append mode is now updated to current time.
  • [TCP Networking Suite - Enhancements]
    • Added: BSD socket application programming interface.
    • Added: BSD_server and BSD_client demo examples for various evaluation boards.
    • Added: new file types/extensions in Web server [MIME types]:
      • txt [text/plain]
      • svg [image/svg+xml]
      • svgz [image/svg+xml], encoding gzip
      • jar [application/java-archive]
      • jz [application/x-javascript], encoding gzip
      • js.gz [application/x-javascript], encoding gzip
    • Added: big endian TCPnet libraries for Cortex-M0, Cortex-M1, Cortex-M3, ARM7 and ARM9.
    • Added: Ethernet driver for STM32F2xx devices.
    • Added: TCPnet examples for ST STM3220-EVAL evaluation board. The examples can be found in ..\ARM\Boards\ST\STM3220F-EVAL\RL\TCPnet folder.
  • [TCP Networking Suite - Problems Solved]
    • Corrected: parameter locport checking in tcp_connect() function. If TCP socket type is TCP_TYPE_CLIENT_SERVER, and socket is listening, the tcp_connect() function accepts only 0 or listening port number as locport parameter.
    • Corrected: potential DMA receive lock up in ETH_STM32x.c ethernet driver caused by IP packet flooding attacks.
  • [USB - Enhancements]
    • Enhanced: USB Host core support for High-speed Mass Storage Devices.
    • Added: USB Host HID_Kbd and MSD_File examples for ST STM3220F-EVAL evaluation board in ..\ARM\Boards\ST\STM3220F-EVAL\RL\USB\Host\ folder.
    • Added: USB Device HID, Memory and Memory_FlashFS examples for ST STM3220F-EVAL evaluation board in ..\ARM\Boards\ST\STM3220F-EVAL\RL\USB\Device\ folder.
    • Added: USB Device HID example for Keil MCB1000(MCB11U10) evaluation board in ..\ARM\Boards\Keil\MCB1000\MCB11U10\RL\USB\Device\ folder.
  • [ULINKpro]
    • Added: support for Instruction Trace on Freescale Kinetis devices.
    • Extended: reset recovery timeout (3s) for Atmel AT91SAM7S/X devices.
  • [ULINK]
    • Extended: reset recovery timeout (3s) for Atmel AT91SAM7S/X devices.
  • [Target Debugging]
    • Updated: support for NULink debugger from Nuvoton. The Nu_Link.dll driver dll in folder ..\ARM\NULInk\ has been updated to version 1.1.5.0.
    • Updated: Segger J-Link driver for ARM devices to version 4.28.
    • Updated: support for ST-Link USB-JTAG debugger. The driver dll STLinkUSBDriver.dll in folder ..\ARM\STLink\ has been updated to version 4.2.2.0.
      The ST-Link_V2_USBdriver.exe driver in folder ..\ARM\STLink\ has been updated to version 16.0.0.435.
  • [µVision]
    • This MDK release comes with µVision V4.21.00.

If you require any further support or if you have any questions please contact Robert.Campbell@JORAL.ca 1-866-477-6668

Older Posts »

Subscribe: RSS Feed Entries Feed (RSS) or RSS Feed Comments Feed (RSS).