Implementing MOSTCO's Roadmap: Page 4 of 8

August 25, 2016 //By Johann Stelzer, Microchip
Implementing MOSTCO's Roadmap
Despite the media hype about Ethernet in the car, the MOST technology is still far more established in the infotainment domain than any other networking technology. The current roadmap, introduced at this year’s MOST Forum has been enhanced; additional waypoints and goals have been added to the roadmap. This article addresses the most significant aspects of these goals, the status and the outlook from Microchip’s perspective.
new feature that has been added to the MOST specification. It allows the reduction of the software stack, which typically demands the use of microcontrollers and memory in peripheral nodes such as cameras, displays, amplifiers and microphones. For example, the remote control feature supports a control port that implements an I2C bus master. The I2C bus master manages, reads and writes to the microphone. The I2C reads and writes are remotely handled through the MOST control channel. Also, GPIOs are remotely handled through the MOST control channel. GPIO events are automatically reported over the MOST network. Existing processing power in the main ECU is used to run the controlling software for all remote controlled nodes. Centralizing all controlling software in the main ECU simplifies the development process considerably, as only one software instance needs to be developed and deployed. Therefore, only the software stack in the central node requires knowledge of MOST; no other MOST node requires this knowledge. The developer is not required to know as much in order to create a MOST network; the developer only has to configure the system descriptor. This kind of device architecture helps to optimize system partitioning, board space and even power dissipation in the remote device. Therefore, memory and an additional microcontroller are not required to run the application. In comparison to Ethernet, this is a major benefit. Microphones and amplifiers demonstrate this very well. UNICENS is not intended to replace MOST NetServices, but is an option enabling customers to develop devices and design a networked system much faster. MOST NetServices continues to coexist with UNICENS. In 2015, the UNICENS approach was validated, developing a proof-of-concept infotainment system in about three months for an European car maker in close collaboration with two tier1s and Microchip.

Fig. 3: Centralized Network Management

 

Simplification of MOST system development was introduced in previous MOST Forums and at Interconnectivity Asia Conference, such as the MOST ToGo

Design category: 

Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.