Skip to content

Zephyr-shell app used to test implemented drivers

Notifications You must be signed in to change notification settings

iotbzh/zephyr-shell

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

zephyr-shell

This demo has been prepared in order to test all available features for Renesas R-Car Gen3 boards.

The current version supports features that may only be available in Iot.bzh Renesas 2.6 BSP.

Knowing that it is not possible to access secondary UART on the Ebisu board, this demo is mainly provided for H3ULCB board.

Build

Building for H3ULCB:

west build -b rcar_h3ulcb_cr7

How to use

Once your zephyr-shell app is flashed on a H3ULCB board, here are the useful commands:

Note : copy paste may brake zephyr-shell interpreter

List device

List available devices to test:

device list

Should answer something like:

devices:

clock-controller@e6150000 (READY)
gpio@e6055400 (READY)
requires: clock-controller@e6150000
serial@e6e68000 (READY)
requires: clock-controller@e6150000
i2c@e66d8000 (READY)
requires: clock-controller@e6150000
i2c@e6510000 (READY)
requires: clock-controller@e6150000
pwm@e6e30000 (READY)
requires: clock-controller@e6150000
can@e6c30000 (READY)
requires: clock-controller@e6150000

GPIO

Physical specs:

  • GPIO6 (gpio@e6055400) Pin 12 -> H3 LED5

Available commands:

gpio set gpio@e6055400 12 1  #Turn LED5 on
gpio set gpio@e6055400 12 0  #Turn LED5 off
gpio get gpio@e6055400 12    #Get LED5 status

I2C

Physical specs:

  • Bus i2c2 (i2c@e6510000) & i2c4 (i2c@e66d8000)
  • TCA9539 I/O expander on 0x74 and 0x75 (i2c2)
  • Register 0x02 is output port 0 (default value = 0xFF)

Commands:

i2c read_byte  i2c@e6510000 0x74 0x02        #Get "output 0" current value for 0x74 addressed TCA9539
i2c write_byte i2c@e6510000 0x74 0x02 0x00   #Set output 0 to 0x00 for 0x74 addressed TCA9539
i2c write_byte i2c@e6510000 0x74 0x02 0xff   #Set output 0 to 0xff for 0x74 addressed TCA9539

CAN

Physical specs:

  • Bus CAN0 (can@e6c30000) -> CN17 connector on KingFisher
  • Pinout : 1 CAN0H, 2 CAN0L, 3 GND

Commands:

can start can@e6c30000                                   #Start CAN controller
can stop can@e6c30000                                    #Stop CAN controller
can show can@e6c30000                                    #Show CAN controller information
can send can@e6c30000 0x123 0xDE 0xAD 0xBE 0xEF          #Send DEADBEEF with ID=0x123 on can0
can send can@e6c30000 -e 0x12345678 0xDE 0xAD 0xBE 0xEF  #Send DEADBEEF with extID=0x12345678 on can0
can filter add can@e6c30000 0x001                        #Listen for messages with ID=0x001 on can0 (Return Filter ID)
can filter add can@e6c30000 -e 0x12345678                #Listen for messages with ID=0x12345678 on can0 (Return Filter ID)
can filter remove can@e6c30000 0                         #Stop listening for Filter 0
can bitrate can@e6c30000 250000                          #Set can0 bitrate at 250000 kbit/s

PWM

Physical specs:

  • Bus PWM0 (pwm@e6e30000) available on CP8 pin test on ULCB boards

Commands:

pwm usec pwm@e6e30000 0 10000 5000
pwm nsec pwm@e6e30000 0 5000000 2500000

About

Zephyr-shell app used to test implemented drivers

Resources

Stars

Watchers

Forks

Packages

No packages published