Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Emtrion SBC

  • 24 V power adapter

  • USB Serial converter

  • Network cables

  • a ARM (arm-none-eabi) gcc compiler (e.g. version 9.2.1 20191025)

  • optionally the Emtrion SBC SDK: https://cloud.emtrion.de/index.php/s/Fd7XWdmjZrBlOhI

  • Emtrion hardware documentation (SBC-RZN1D-Hardware_Manual_v008en.pdf)

  • Emtrion SDK and software documentation (sbc-rzn1d-yocto-manual_v005en.pdf)

  • updated device tree

  • updated uboot

  • cm3 firmware

  • port application sdk

  • Industrial Communication Explorer

Device setup

Entering the boot loader

You will need a USB serial converter connected to the device (header J5). UART speed is 115200 baud. After bootup of the device you will have the possibility to enter the uboot boot loader. From there the following steps can be executed.

Update of uboot

Please refer to the documentation from emtrion (sbc-rzn1d-yocto-manual_v005en.pdf) on how to update the uboot boot loader (u-boot.img). This is possible using a NFS or a TFTP server. The correct version shown should be “U-Boot 2017.01 sbc-rzn1d v01.0xp (Feb 02 2021 - 11:46:11 +0000)”.

Update of the device tree

Now you need to boot into linux (power cycle or u-boot command "boot"). The device is initially configured to use DHCP. Ethernet ports J1 and J2 are used by the linux system. To login into linux, use the account root with no password (default settings).

Please place the dtb into the /boot folder of the filesystem accessible within linux.

...

Delivery

The port SDK is provided in the form of an zip archive. Beside the sources required for building applications for the protocol stacks and some examples following files are provided:

  • CM3 firmware: projects/2021015/cc/dtb/cm3_fw.bin

    • this is the firmware for the CM3 core containing the protocol stacks

  • DTB: projects/2021015/cc/dtb/sbc-rzn1d.dtb

    • this is the device tree for the A7 (Linux) core required to fully support the CM3 core functionality

Device setup

Entering the boot loader

You will need a USB serial converter connected to the device (header J5). UART speed is 115200 baud. After bootup of the device you will have the possibility to enter the uboot boot loader. From there the following steps can be executed.

Programming of the CM3 firmware

This step is done from the u-boot bootloader. Following commands show the procedure. Update is done using tftp here:

...

Code Block
SBC-RZN1D U-Boot > run update_cm3
Speed: 1000, full duplex
Using dwmac.44002000 device
TFTP from server 192.168.2.1; our IP address is 192.168.2.2
Filename '/private/tftpboot/cm3_fw.bin'.
Load address: 0x80008000
Loading: #############
         3.4 MiB/s
done
Bytes transferred = 180287 (2c03f hex)
SF: Detected s25fl128s_64k with page size 256 Bytes, erase size 64 KiB, total 16 MiB, mapped at 10000000
SF: 196608 bytes @ 0xe0000 Erased: OK
device 0 offset 0xe0000, size 0x2c03f
SF: 180287 bytes @ 0xe0000 Written: OKsize 0x2c03f
SF: 180287 bytes @ 0xe0000 Written: OK

Update of the device tree

Now you need to boot into linux (power cycle or u-boot command "boot"). The device is initially configured to use DHCP. Ethernet ports J1 and J2 are used by the linux system. To login into linux, use the account root with no password (default settings).

Please place the dtb into the /boot folder of the filesystem accessible within linux.

Setup of the port SDK

The port SDK can be be used on any linux machine capable of cross compiling for the arm platform (see compiler requirements). To install the SDK create a folder and unpack the delivered archive (0860_012_SDK_2_23_0__EMTRIONSBC_LINUX_GCC.zip).

...

If you need to specify the cross compiler, you can do so by calling make in the following way:

...

Code Block
make CROSS_COMPILE=/opt/arm-linux-gnuebaihf-gcc/bin/arm-linux-gnueabihf-

The resulting binary is located in the sub folder build/emtrion_sbc_rzn1d_a7. It can be transfered to the device using scp:

...

Code Block
root@sbc-rzn1d:~# ./goal_emtrion_sbc_rzn1d_a7.bin
GOAL Start

mbox: Created device mbox_2.
[AC_I|goal_taskCreate:117] creating task: GOAL Timer
[AC_I|goal_tgtTaskCreate:1210] task stack size: 8388608 byte
[AC_I|goal_tgtTaskCreate:1252] task scheduler priority: 99
[AC_I|goal_taskCreate:160] Created task GOAL Timer with priority 100/100 and stack 0 byte sucessfully.
[AC_I|goal_cmInit:220] Calculated config size of 240 in 3 modules modules
[AC_I|goal_taskCreate:117] creating task: /dev/mbox_2
[AC_I|goal_tgtTaskCreate:1210] task stack size: 8388608 byte
[AC_I|goal_tgtTaskCreate:1252] task scheduler priority: 54
[AC_I|goal_taskCreate:160] Created task /dev/mbox_2 with priority 50/100 and stack 0 byte sucessfully.
[AC_I|goal_miMctcRamReg:148] setting media timeout to 1000:
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 1159, len: 4296
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 1159, len: 4296
[AC_I|goal_snmpInitRpc:103] SNMP Application Core successfully started
[AC_I|goal_taskCreate:117] creating task: GOAL Main
[AC_I|goal_tgtTaskCreate:1210] task stack size: 8388608 byte
[AC_I|goal_tgtTaskCreate:1252] task scheduler priority: 10
[AC_I|goal_taskCreate:160] Created task GOAL Main with priority 0/100 and stack 0 byte sucessfully.
[AC_I|goal_init:181] GOAL initialized
[AC_I|goal_miMctcRpcSyncLoop:1208] RPC state synchronized, running appl_setup
[AC_I|goal_miMctcRpcSyncLoop:1212] configuring timeout values for peer
[AC_I|goal_pnioNewAc:264] auto data mapper for DP is disabled
[AC_I|goal_pnioNewAc:265] auto data mapper for APDU is disabled
[AC_I|goal_pnioNewAc:339] PROFINET Application Core successfully started
[AC_I|appl_setup:239] Initializing device structure
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 0, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 0, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 1, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 1, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 2, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 2, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 3, len: 2
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 3, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 5, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 4, len: 2
[AC_I|goal_miDmPartRegInt:275] part added to 'Write to CC', pos: 6, len: 1
[AC_I|goal_miDmPartRegInt:275] part added to 'Read from CC', pos: 6, len: 1
[AC_I|appl_setup:456] PROFINET ready
[AC_I|appl_setup:458] Configuring DD
[AC_I|appl_setup:482] DD ready
[AC_I|appl_httpSetup:100] setup web server
[AC_I|goal_httpNewAc:954] HTTP Application Core successfully started
[AC_I|appl_httpSetup:178] web server setup done
[AC_I|appl_setup:504] CCM version : 2ab72cd22
[AC_I|appl_setup:505] CCM device : 1
[AC_I|appl_setup:507] CCM Serial : 01:00:00:00:8c:e2
[AC_I|goal_miMctcRpcSyncLoop:1253] local setup done
[AC_I|goal_memInitDone:152] fixed memory usage: 109916/262144 bytes bytes
[AC_I|goal_memInitDone:157] fixed memory usage: (42%)

Automatic start of the firmware

There is an init script /etc/init.d/goal_app.sh provided, which if a binary under /home/root/goal_emtrion_sbc_rzn1d_a7.bin is available, this is started at boot time.

Installation of the port Industrial Communication Explorer

...