Pentachord

W7500

Pentachord — Thu, 3 Jul 2025 09:05:07 +0900

W7500

The IOP4IoT W7500 chip is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform, especially internet of things. The TCP/IP core is a market-proven hardwired TCP/IP stack with an integrated Ethernet MAC. The Hardwired TCP/IP stack supports the TCP, UDP, IPv4, ICMP, ARP, IGMP and PPPoE which has been used in various applications for more than 15 years. W7500 suits users who need Internet connectivity best.

Features

ARM Cortex-M0
- 48MHz maximum frequency
Hardwired TCP/IP Core
- 8 Sockets
- SRAM for socket: 32 KB
- MII (Medium-Independent Interface)
Memories
- Flash: 128 KB
- SRAM: 16 KB
- ROM for boot code: 6 KB
Clock, reset and supply management
- POR (Power-On Reset)
- Internal Voltage Regulator : 3.3V to 1.5V
- 8-to-24MHz external crystal oscillator
- Internal 8MHz RC Oscillator
- PLL for CPU clock
ADC : 12bit, 8ch, 1Mbps
DMA
- 6-channel DMA controller
- Peripheral supported: UARTs, SPIs
GPIO
- 53 I/Os (16 IO x 3ea, 5 IO x 1ea)
Debug mode
- Serial Wire Debug (SWD)
Timer/PWM
- 1 Watchdog (32-bit down-counter)
- 4 Timers (32-bit or 16-bit down-counter)
- 8 PWMs (32-bit counter/timers with programmable 6-bit prescaler)
Communication Interfaces
- 3 UART (2 UARTs with FIFO and Flow Control, 1 simple UART)
- 2 SPI
- 2 I2C (Master/Slave, Fast-mode (400 kbps))
Crypto
- 1 RNG (Random Number Generator): 32-bit random number
Package
- 64 TQFP (7x7 mm)

Details

WIZwiki-W7500 mbed Starter Kit

Pentachord — Thu, 3 Jul 2025 09:03:39 +0900

WIZwiki-W7500 mbed Starter Kit

WIZwiki-W7500 mbed Starter Kit is a product that helps user to learn how to use WIZwiki-W7500 mbed Platform board. WIZwiki-W7500 mbed Starter Kit consists of WIZwiki-W7500 board and other parts for DIY (Do-It-Yourself).

한국어

WIZwiki-W7500 mbed Starter Kit 제품 소개
스타터 킷 튜토리얼 (예제로 따라해보기)

English

WIZwiki-W7500 mbed Starter Kit Introduction
Starter Kit Tutorial

WIZwiki-W7500ECO

Pentachord — Thu, 3 Jul 2025 09:03:04 +0900

WIZwiki-W7500ECO

WIZwiki Platform

WIZnet WIZwiki-W7500ECO is a WIZwiki platform board based on W7500. The IOP4IoT W7500 chip is one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially internet of things. You can develop prototype product more quickly using WIZwiki-W7500ECO and it includes CMSIS-DAP for debuging and ethernet-phy.

Features

WIZnet W7500

ARM Cortex-M0 Core
48MHz, 128KB Flash
16KB RAM
32KB RAM for TCP/IP - Can be extended to system RAM
Hardwired TCP/IP Core
MII Interface
ADC (8)
GPIO (53)
SWD (Serial Wire Debug)
Timer/PWM
UART (3)
SPI (2)

External Ethernet PHY

IC+ IP101GRI
Single Port 10/100 MII/RMII/TP/Fiber Fast Ethernet Transceiver
Auto MDI/MDIX function
Supports MDC and MDIO to communicate with the MAC

CMSIS-DAP

LPC11U35FHI33/501, ARM Cortex-M0 Core, NXP
Drag-n-drop programming
USB Serial Port
Easy to use C/C++ SDK

Connector

Micro USB
Slim Size RJ45(with transformer)
GPIO Header

ETC

Power source - micro USB or external 5V pin
1 RESET SW.
RGB LED for CMSIS-DAP
2 Blue LED for USER
2 2.54mm 1×20 Externel connector

WIZwiki-W7500ECO Blockdiagram

WIZwiki-W7500ECO Callout

WIZwiki-W7500ECO Detail Pinout

WIZwiki-W7500ECO Simple Pinout

Firmware

W7500 Library

W7500 Library PAGE

Getting Started

Make New WIZwiki-W7500ECO Projects

Technical Reference

Datasheet

Schematic

Schematic Version 1.1
WIZwiki-W7500eco V1.1 Schematic (Altium Designer)
WIZwiki-W7500eco V1.1 Schematic (PDF)

Part list

WIZwiki-W7500eco V1.1 BOM (PDF)

Dimension

WIZwiki-W7500ECO V1.1 Dimension

Etc.

Serial Port Driver

ARM mbed Window serial configuration PAGE

W7500 ISP Program

Go to ISP tool manual & Program download

Examples Binary

WIZwiki-W7500ECO Examples Binary

WIZwiki-W7500P

Pentachord — Thu, 3 Jul 2025 09:02:34 +0900

WIZwiki-W7500P

WIZwiki Platform

WIZnet WIZwiki Platform based on WIZnet's MCU. WIZnet WIZwiki-W7500P is a WIZwiki platform board based on W7500P. The IOP4IoT W7500P chip is the one-chip solution which integrates an ARM Cortex-M0, 128KB Flash, hardwired TCP/IP core for various embedded application platform, 10/100 Ethernet MAC and PHY, and especially internet of things. The TCP/IP core is a market-proven hardwired TCP/IP stack and PHY is IC plus IP101G, an IEEE 802.3/802.3u Fast Ethernet Transcevier for 10/100Mbps. The Hardwired TCP/IP stack supports the TCP, UDP, IPv4, ICMP, ARP, IGMP and PPPoE which has been used in various applications for more than 15 years. W7500P suits users who need Internet connectivity best.

Features

WIZnet W7500P

ARM Cortex-M0 Core
PHY (IC+(IP101G))
48MHz, 128KB Flash
16KB RAM
32KB RAM for TCP/IP - Can be extended to system RAM
Hardwired TCP/IP Core
Internal Ethernet PHY
MDI Interface
ADC (8)
GPIO (34)
SWD (Serial Wire Debug)
Timer/PWM
UART (3)
SPI (2)
64 LQFP (7×7 mm)

CMSIS-DAP

LPC11U35FHI33/501, ARM Cortex-M0 Core, NXP
Drag-n-drop programming
USB Serial Port
Easy to use C/C++ SDK

Connector

USB Mini B Type
Slim Size RJ45(with transformer)
Arduino compatible pin headers
Xbee Header

ETC

5V USB Power or 5V header supply
2 system SW - RESET SW, BOOT SW
1 User SW
RGB LED
Micro SD card slot

WIZwiki-W7500P Blockdiagram

WIZwiki-W7500P Callout

WIZwiki-W7500P Pinout

Firmware

W7500P Library

W7500P Library PAGE

Getting Started

Make New WIZwiki-W7500P Projects

Technical Reference

Datasheet

Schematic

If your project uses the W7500P, do not refer to the WIZwiki-W7500P V1.0 schematic.
Refer to the reference schematic of W7500P.
- Reference schematic of W7500P

Schematic Version 1.0
WIZwiki-W7500P V1.0 Schematic (Altium Designer)
WIZwiki-W7500P V1.0 Schematic (PDF)

Part list

WIZwiki-W7500P V1.0 BOM (PDF)

Dimension

WIZwiki-W7500P V1.0 Dimension

Etc.

Serial Port Driver

ARM mbed Window serial configuration PAGE

W7500P ISP Program

Go to ISP tool manual & Program download

Examples Binary

WIZwiki-W7500P Examples Binary

WIZwiki-W7500

Pentachord — Thu, 3 Jul 2025 09:02:06 +0900

WIZwiki-W7500

WIZwiki Platform

WIZnet WIZwiki Platform based on WIZnet's MCU. WIZnet WIZwiki-W7500 is a WIZwiki platform board based on W7500. The IOP4IoT W7500 chip is one-chip solution which integrates an ARM Cortex-M0, 128KB Flash and hardwired TCP/IP core for various embedded application platform especially internet of things. If you use WIZwiki-W7500, you will be able to easily develop a prototype. It is compatible with Arduino Shields. This is using the CMSIS-DAP USB and ISP Header easily available firmware writing.

Features

WIZnet W7500

ARM Cortex-M0 Core
48MHz, 128KB Flash
16KB RAM
32KB RAM for TCP/IP - Can be extended to system RAM
Hardwired TCP/IP Core
MII Interface
ADC (8)
GPIO (53)
SWD (Serial Wire Debug)
Timer/PWM
UART (3)
SPI (2)

External Ethernet PHY

IC+ IP101GA
Single Port 10/100 MII/RMII/TP/Fiber Fast Ethernet Transceiver
Auto MDI/MDIX function
Supports MDC and MDIO to communicate with the MAC

CMSIS-DAP

LPC11U35FHI33/501, ARM Cortex-M0 Core, NXP
Drag-n-drop programming
USB Serial Port
Easy to use C/C++ SDK

Connector

USB Mini B Type
Slim Size RJ45(with transformer)
Arduino compatible pin headers
SWD Header (1.27mm and 2.54mm)
GPIO Header
ISP Header

ETC

5V USB Power or 5V header supply
2 system SW - RESET SW, BOOT SW
RGB LED
Micro SD card slot

WIZwiki-W7500 Blockdiagram

WIZwiki-W7500 Callout

WIZwiki-W7500 Detail Pinout

WIZwiki-W7500 Simple Pinout

Firmware

W7500 Library

W7500 Library PAGE

Getting Started

Make New WIZwiki-W7500 Projects

Technical Reference

Datasheet

Schematic

Schematic Version 1.1
WIZwiki-W7500 V1.1 Schematic (Altium Designer)
WIZwiki-W7500 V1.1 Schematic (PDF)

Schematic Version 1.0
WIZwiki-W7500 V1.0 Schematic (Altium Designer)
WIZwiki-W7500 V1.0 Schematic (PDF)

Part list

WIZwiki-W7500 V1.0 BOM (PDF)

Dimension

WIZwiki-W7500 V1.0 Dimension

Etc.

Serial Port Driver

ARM mbed Window serial configuration PAGE

W7500 ISP Program

Go to ISP tool manual & Program download

Examples Binary

WIZwiki-W7500 Examples Binary

W5500 Ethernet Shield

Pentachord — Thu, 3 Jul 2025 09:00:23 +0900

W5500 Ethernet Shield

Overview

ARM mbed compatible operation
Arduino Pin-compatible
Ethernet (W5500 Hardwired TCP/IP chip)

W5500 Ethernet shield is designed using the WIZnet W5500 chip. Please click the link for the further information about W5500. It supports both 3.3V & 5V. This Ethernet Shield is compatible with Arduino and ARM mbed Platform.

Available Board List

ARM mbed Board
- ARM mbed Platform : ARM mbed platform Site
- FRDM-KL25Z : Freescale
- NXP LPC800-MAX : NXP
Arduino Board
- Arduino board (e.g. the Uno, Mega, Due)
- Arduino Leonardo
Arduino-compatible Board
- Seeeduino v3.0 : Based on Arduino Duemilanove

Getting Started

You need to update Arduino IDE to use W5500 Ethernet shield(Required)
Check the below.
- Getting Started

Language

Feature

Support 3.3V / 5V
High Speed Ethernet controller W5500 chip
SPI interface
Internal 32Kbytes Tx/Rx buffer
10/100 Ethernet PHY embedded
Support Auto Negotiation (Full / Half duplex, 10 / 100-based)
Hardwired TCP/IP Protocols : TCP, UDP, ICMP, IPv4, ARP, IGMP, PPPoE
User Selectable GPIO pin
Support SD-card slot for storage
Support I2C, UART interface

Hardware Configuration

RJ-45 with Transformer : Ethernet Port
W5500 : a Hardwired TCP/IP Ethernet Controller
RESET : Reset Ethernet shield and Arduino when pressed
SD-Slot : support Micro SD card in FAT16 or FAT32 ; (Please read 'Caution' below)
I2C : I2C interface
UART : UART interface

Pins usage on Arduino & ARM mbed

W5500 Ethernet shield has several configurable GPIOs

When you operate it with other modules, you may need to change 'Chip Select' pin to a different one.
W5500 INTn pin is linked to D2 (2,3 Short). So, if you need INTn pin. You soldering to 0R Resistor to Dx pin

Caution) When the user uses 5V Platform, we cannot confirm a stable operation of SD-CARD. Therefore, though 5V Platform is safe to use after going through enough tests, it is highly recommended to mount buffer & 100nF Capacitor for a secure operation.

SPI Operation & Timing Diagram

SPI Operation

There is a W5500 inside W5500 Ethernet shield. Therefore SPI operation & Timing Diagram of Ethernet shield follows one of W5500. For more information about W5500 chip please also refer to the chip's datasheet:

Technical Reference

Block Diagram

Not buffer

Using buffer

Rev 1.0 Schematic

Rev 1.1 Schematic

Rev 1.01_Customize Schematic

Do you want to develop new this product? Please look at the Rev 1.01_Customize circuit
Rev 1.01 removed the buffer ICs from Rev 1.0 circuit
Because, Buffer IC was limited delay speed.
Arduino compatible INT(R25) remove

W5500 Ethernet shield Rev1.01 Schematic

Part list

W5500 Ethernet shield Rev1.0 Part list

Dimension

The board size of the W5500 Ethernet shield Rev1.1 is the same as Rev1.0.
W5500 Ethernet shield Rev1.0/1.1 Dimension

Etc.

Using WIZnet Ethernet Library for ioshield-A

http://wizwiki.net/wiki/doku.php?id=osh:ioshield-a:updatelib

Examples

http://wizwiki.net/wiki/doku.php?id=osh:ioshield-a:testtwitter

Ethernet Library

https://github.com/Wiznet/WIZ_Ethernet_Library

BLE to Ethernet

Pentachord — Thu, 3 Jul 2025 08:59:13 +0900

BLE to Ethernet

Using WIZnet TCP/IP Ethernet chip W5500 and the Nordic BLE SoC nRF52832 implemented the BLE to Ethernet. BLE Central/Peripheral communicate using a UART Nordic Service (NUS) Profile. And BLE Central and W5500 communicate with SPI. W5500 also operates as a TCP Client, TCP Server to communicate with the LAN (through the line). The purpose of this Application Note is to build a low power IoT node environment.

Development Environment

Firmware

https://github.com/Wiznet/WIZBLE510_ETHERNET

Hardware

Product DataSheet Download link

nRF52832	Download
PCA10040	Download
W5500	Download
Schematic	Download
Altium	Download
Gerber	Download

PC Tools

PC Tools Download link

Keil MDK 5.17	Download
nRFgo Studio	Download
Hercules	Download

Base Protocol

The project made use of TCP and BLE NUS Service. Each document is on the link below.

Protocol Document

W5500 TCP	Doc Link
BLE NUS Central	Doc Link
BLE NUS Peripheral	Doc Link

Code configuration

uart_init

UART Initializes for communication with a PC. The pins can be changed freely.

void uart_init(app_uart_event_handler_t event_handler, app_irq_priority_t irq_priority)
{
    uint32_t err_code;
    const app_uart_comm_params_t comm_params =
    {
        .rx_pin_no    = RX_PIN_NUMBER,
        .tx_pin_no    = TX_PIN_NUMBER,
        .rts_pin_no   = 0xFF,
        .cts_pin_no   = 0xFF,
        .flow_control = APP_UART_FLOW_CONTROL_DISABLED,
        .use_parity   = false,
        .baud_rate    = UART_BAUDRATE_BAUDRATE_Baud115200
    };	
    APP_UART_FIFO_INIT(&comm_params,
                        UART_RX_BUF_SIZE,
                        UART_TX_BUF_SIZE,
                        event_handler,
                        irq_priority,
                        err_code);
    APP_ERROR_CHECK(err_code);
}

ble_stack_init

Initialize BLE stack and RTC clock.

void ble_stack_init(void)
{
    uint32_t err_code;    
    nrf_clock_lf_cfg_t clock_lf_cfg = NRF_CLOCK_LFCLKSRC;    
    // Initialize the SoftDevice handler module.
    SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL);   
    ble_enable_params_t ble_enable_params;
    err_code = softdevice_enable_get_default_config(CENTRAL_LINK_COUNT,
                                                    PERIPHERAL_LINK_COUNT,
                                                    &ble_enable_params);
    APP_ERROR_CHECK(err_code);    
    //Check the ram settings against the used number of links
    CHECK_RAM_START_ADDR(CENTRAL_LINK_COUNT,PERIPHERAL_LINK_COUNT);    
    // Enable BLE stack.
    err_code = softdevice_enable(&ble_enable_params);
    APP_ERROR_CHECK(err_code);
    // Register with the SoftDevice handler module for BLE events.
    err_code = softdevice_ble_evt_handler_set(ble_evt_dispatch);
    APP_ERROR_CHECK(err_code);
}

nus_c_init

Initializes function that the NUS central service.

void nus_c_init(ble_nus_c_evt_handler_t evt_handler)
{
    uint32_t         err_code;
    ble_nus_c_init_t nus_c_init_t;
    nus_c_init_t.evt_handler = evt_handler;
    err_code = ble_nus_c_init(&user_m_ble_nus_c.m_ble_nus_c, &nus_c_init_t);
    APP_ERROR_CHECK(err_code);
    err_code = sd_ble_gap_address_get  (&user_m_ble_nus_c.own_addr); 
    APP_ERROR_CHECK(err_code);
}

db_discovery_init

initializes database discovery.

void db_discovery_init(void)
{
    uint32_t err_code = ble_db_discovery_init(db_disc_handler);
    APP_ERROR_CHECK(err_code);
}

spi0_master_init

initialize W5500 and SPI communication function. Pins can be changed freely.

void spi0_master_init()
{
    SPIConfig_t spi_info = {.Config.Fields.BitOrder = SPI_BITORDER_MSB_LSB,
                        .Config.Fields.Mode     = SPI_MODE3,
                        .Frequency              = SPI_FREQ_8MBPS,
                        .Pin_SCK                = SPIM0_SCK_PIN,
                        .Pin_MOSI               = SPIM0_MOSI_PIN,
                        .Pin_MISO               = SPIM0_MISO_PIN,
                        .Pin_CSN                = SPIM0_SS_PIN};	
    spi_master_init(SPI0,&spi_info);
}

user_ethernet_init

Function that initializes the W5500 through SPI.

void user_ethernet_init()
{
    uint8_t tmp;
    uint8_t memsize[2][8] = {{2,2,2,2,2,2,2,2},{2,2,2,2,2,2,2,2}};
    wiz_NetTimeout timeout_info;
    reg_wizchip_cs_cbfunc(wizchip_select, wizchip_deselect);
    reg_wizchip_spi_cbfunc(wizchip_read, wizchip_write);
    /* WIZCHIP SOCKET Buffer initialize */	
    printf("W5500 memory init\r\n");
    if(ctlwizchip(CW_INIT_WIZCHIP,(void*)memsize) == -1)
    {
    	printf("WIZCHIP Initialized fail.\r\n");
       while(1);
    }
    /* PHY link status check */
    printf("W5500 PHY Link Status Check\r\n");
    do
    {
       if(ctlwizchip(CW_GET_PHYLINK, (void*)&tmp) == -1)
    	   printf("Unknown PHY Link stauts.\r\n");
    }while(tmp == PHY_LINK_OFF);
    timeout_info.retry_cnt = 1;
    timeout_info.time_100us = 0x3E8;	// timeout value = 10ms
    wizchip_settimeout(&timeout_info);
    /* Network initialization */
    network_init();
}

user_app_timer_init

App Timer Task registration and period setting.

static void user_app_timer_init(void)
{
    uint32_t err_code;    
    err_code = app_timer_create(&tcp_con_timer_id, APP_TIMER_MODE_REPEATED, tcp_con_timer);
    APP_ERROR_CHECK(err_code);
    err_code = app_timer_create(&ble_to_tcps_timer_id, APP_TIMER_MODE_REPEATED, ble_to_tcps);
    APP_ERROR_CHECK(err_code);	
    err_code = app_timer_create(&tcps_to_ble_timer_id, APP_TIMER_MODE_REPEATED, tcps_to_ble);
    APP_ERROR_CHECK(err_code);
}

user_app_timer_start

App_timer Task Start

static void user_app_timer_start(void)
{
    uint32_t err_code;    
    err_code = app_timer_start(tcp_con_timer_id, TCP_CON_INTERVAL,NULL);
    APP_ERROR_CHECK(err_code);
    err_code = app_timer_start(ble_to_tcps_timer_id, BLE_TO_TCPS_INTERVAL, NULL);
    APP_ERROR_CHECK(err_code);
    err_code = app_timer_start(tcps_to_ble_timer_id, TCPS_TO_BLE_INTERVAL, NULL);
    APP_ERROR_CHECK(err_code);	
}

tcp_con_timer

A connection with the TCP Server and checks periodically connected. It tries to reconnect when disconnected.

void tcp_con_timer(void * p_context)
{
    int32_t ret; // return value for SOCK_ERRORs
   // Port number for TCP client (will be increased)
    uint16_t any_port = 50000;
   // Socket Status Transitions
   // Check the W5500 Socket n status register (Sn_SR, The 'Sn_SR' controlled by Sn_CR command or Packet send/recv status)
    switch(getSn_SR(SOCK_TCPC))
    {
        case SOCK_CLOSE_WAIT :
#ifdef _LOOPBACK_DEBUG_
         //printf("%d:CloseWait\r\n",sn);
#endif
            if((ret=disconnect(SOCK_TCPC)) != SOCK_OK) 
                printf("%d:Socket Closed Fail\r\n", SOCK_TCPC);
#ifdef _LOOPBACK_DEBUG_
            printf("%d:Socket Closed\r\n", SOCK_TCPC);
#endif
            break;
        case SOCK_INIT :
#ifdef _LOOPBACK_DEBUG_
            printf("%d:Try to connect to the %d.%d.%d.%d : %d\r\n", 
                    SOCK_TCPC, targetIP[0], targetIP[1], targetIP[2], targetIP[3],tcp_targetPort);
#endif
            if( (ret = connect(SOCK_TCPC, targetIP, tcp_targetPort)) != SOCK_OK) 
                printf("%d:Socket Connect Fail\r\n", SOCK_TCPC);	
                //Try to TCP connect to the TCP server (destination)
            break;
        case SOCK_CLOSED:
            close(SOCK_TCPC);
    	      if((ret=socket(SOCK_TCPC, Sn_MR_TCP, any_port++, 0x00)) != SOCK_TCPC)
                  printf("%d:Socket Open Fail\r\n", SOCK_TCPC); // TCP socket open with 'any_port' port number
            break;				
        default:
            break;
    }
}

tcps_to_ble

Data from the TCP Server delivers on the BLE Peripheral.

void tcps_to_ble(void * p_context)
{
    uint32_t size, i, k=0;
    int32_t ret;
    char buf[DATA_BUF_SIZE];
 
    if((size = getSn_RX_RSR(SOCK_TCPC)) > 0) // Sn_RX_RSR: Socket n Received Size Register, Receiving data length
    {
        size = MIN(size, DATA_BUF_SIZE); // DATA_BUF_SIZE means user defined buffer size (array)
        ret = recv(SOCK_TCPC, (uint8_t *)buf, size); // Data Receive process (H/W Rx socket buffer -> User's buffer)
        if (ret<0)
        {
            close(SOCK_TCPC); // socket close
        }
        else
        {
            while(size)
            {
                i = MIN(size, BLE_NUS_MAX_DATA_LEN);
                while (ble_nus_c_string_send(&user_m_ble_nus_c.m_ble_nus_c, (uint8_t *)(buf+k), i) != NRF_SUCCESS)
                {
                      // repeat until sent.
                }
                size-=i;
                k+=i;
            }
        }
    }
}

ble_to_tcps

Data from the BLE Peripheral delivers on the TCP Server.

void ble_to_tcps(void * p_context)
{
    int32_t ret;
    char buf[100] ;
 
    if (data_in_flag)
    {
        if (getSn_SR(SOCK_TCPC) == SOCK_ESTABLISHED)
        {
            sprintf(buf, "[From BLE_P] %02x:%02x:%02x:%02x:%02x:%02x ", 
		    user_m_ble_nus_c.peer_addr.addr[0], user_m_ble_nus_c.peer_addr.addr[1], 
                    user_m_ble_nus_c.peer_addr.addr[2], user_m_ble_nus_c.peer_addr.addr[3],
                    user_m_ble_nus_c.peer_addr.addr[4], user_m_ble_nus_c.peer_addr.addr[5]);
                    ret = send(SOCK_TCPC,  (void *)buf, strlen(buf));
                    ret = send(SOCK_TCPC,  (void *)ble_input_data, ble_input_data_len); 
                    if(ret < 0) // Send Error occurred (sent data length < 0)
                        close(SOCK_TCPC); // socket close
	}
	data_in_flag = false;
    }
}

ble_nus_c_evt_handler

Interrupt is occurred by data that comes from BLE Peripheral. Data from BLE Peripheral stores on the ble_input_data buffer.

void nus_c_init(ble_nus_c_evt_handler_t evt_handler)
{
    uint32_t         err_code;
    ble_nus_c_init_t nus_c_init_t;
 
    nus_c_init_t.evt_handler = evt_handler;
    err_code = ble_nus_c_init(&user_m_ble_nus_c.m_ble_nus_c, &nus_c_init_t);
    APP_ERROR_CHECK(err_code);
    err_code = sd_ble_gap_address_get  (&user_m_ble_nus_c.own_addr); 
    APP_ERROR_CHECK(err_code);
}

uart_event_handle

The Interrupt occurs when UART Data Input. And it sends it to UART Input Data in BLE Peripheral.

void uart_event_handle(app_uart_evt_t * p_event)
{
    static uint8_t data_array[BLE_NUS_MAX_DATA_LEN];
    static uint8_t index = 0;
    switch (p_event->evt_type)
    {
        /**@snippet [Handling data from UART] */ 
        case APP_UART_DATA_READY:
            UNUSED_VARIABLE(app_uart_get(&data_array[index]));
            index++;
            if ((data_array[index - 1] == '\n') || (index >= (BLE_NUS_MAX_DATA_LEN)))
            {
                while (ble_nus_c_string_send(&user_m_ble_nus_c.m_ble_nus_c, data_array, index) != NRF_SUCCESS)
                {
                    // repeat until sent.
                }
                index = 0;
            }
            break;
        /**@snippet [Handling data from UART] */ 
        case APP_UART_COMMUNICATION_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_communication);
            break;
        case APP_UART_FIFO_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_code);
            break;
        default:
            break;
    }
}

Testing

H/W Setting

BLE Stack (SoftDevice) Writing

Program the S132_nrf52_2.0.1_softdevice.hex attached to nRF5_SDK_11.0.0_W5500_ble-to-ethernet.zip on two boards. (Ble to Ethernet Board, PCA10040)

Ble to ethernet Board application Writing

Open the nRF5_SDK_11.0.0_W5500_ble-to-ethernet\examples\ble_central\ble_uart_c_to_tcpc\pca10040\s132\arm5_no_packs path of the project. Put the IP Address of the TCP server PC to the 60th line of the variable targetIP main.c, build, and Program a ble to ethernet board.

PCA10040 application Writing

Build the project to open a path nRF5_SDK_11.0.0_89a8197\examples\ble_peripheral\ble_app_uart\pca10040\s132\arm5_no_packs, and Writing in PCA10040 board.

Config HyperTerminal & TCP Server

Three open the Hercules. Two Hercules is set to 115200 baud rate in the Serial Tab and open the Com port. One of the Hercules Port is set to 5000 in the TCP Server tab and click on the listen.

Data Input

Input from the WIZNET PCA10040 Terminal can see that is sent to the TCP Server.

Ethernet Shield using WIZnet module

Pentachord — Thu, 3 Jul 2025 08:57:50 +0900

Botanicalls kits(IM120724002)

Botanicalls Kits let plants reach out for human help! They offer a connection to your leafy pal via online Twitter status updates to your mobile phone. When your plant needs water, it will post to let you know, and send its thanks when you show it love.
This kits is based on the WIZnet WIZ811MJ module.

Ethernet Shield using w5100

Pentachord — Thu, 3 Jul 2025 08:57:13 +0900

Ethernet Board from PARALLAX (Spinneret Web Server)

The Spinneret Web Server is an Ethernet-based development board for the Propeller microcontroller. Web page content, files, and logs can be stored on a microSD card. The serial EEPROM has 32 KB for storing a Propeller program and 32 KB for non-volatile data storage, independent of the microSD card. There is a real-time clock controller for time stamping files and events and a backup capacitor that will keep the clock running through extended power outages. There is a serial programming header and two auxiliary I/O connections, one for level-shifted open collector communications over a three-pin data/power/ground cable, and the other is a 12-pin socket for direct 3.3 volt I/O connections. There are eight status LEDs on the circuit board, plus two that are repeated on the Ethernet jack. One of the status LEDs is user-controllable and shares a line with a button that can be read under user control. A second button resets the Propeller to reload the firmware from the EEPROM.
Wiznet W5100 ethernet chip offloads TCP/IP stack, using minimal Propeller resources.

Freeduino FT811mj

FT811mj network module is based on a network controller W5100, and contains the necessary passive components, RJ-45 connector with integrated transformer and LEDs, and is a complete analog modules WIZ810MJ/WIZ811MJ/WIZ812MJ Addiction Wiznet.

AndyMark Sasquatch Robot Controller (am-2527)

The Sasquatch Robot Controller is an Arduino Mega variant made by 221 Robotic Systems. This board utilizes the RobotOpen Protocol to stream line information from a computer to the robot and is compatible with existing Arduino Libraries. This is an excellent robot controller, utilizing wi-fi based operation for mobile robots. Users can access any newly expanded I/O using the included libraries.
This board comes bundled with RobotOpen Arduino Library and Driver Station App. These software packages allow you to control the Sasquatch board via USB joysticks and gamepads and establish robust two-way communication. The library includes many examples for common tasks and drive code for tank, mecanum and crab drive bases.
A newly updated Driver Station app is web-based and features graphs, charts and data-logging along with graphical mapping of input devices.
This board is based on is based on the Wiznet W5100 Ethernet chip.

Iboard (IM120410001)

Iboard is a unique Arduino platform which features a Wiznet W5100 Ethernet chip, an XBee socket, nRF24L01+ wireless interface and an ATMega328. This board will add wireless XBee / nRF24L01+ control as well as internet connectivity to your projects. It’s great for anything from home automation to robot control.

Iboard EX (IM120905007)

Iboard EX is a unique Arduino platform which features a Wiznet W5100 Ethernet chip, an XBee socket, nRF24L01+ wireless interface and an ATMega32U4. This board will add wireless XBee / nRF24L01+ control as well as internet connectivity to your projects. It’s great for anything from home automation to robot control.

Iboard Pro (IM120724002)

Iboard Pro is a unique Arduino board which features a Wiznet W5100 Ethernet chip with POE, an XBee socket, ITDB02 Serial/Parallel LCD module interface, RTC, nRF24L01+ module interface, Micro SD socket and an ATMega2560. This board will add wireless XBee control as well as internet connectivity to your projects. It’s great for anything from home automation to robot control. The possibilities are endless!

SainSmart W5100 Network Module

This Module Support full hardware TCP / IP protocol: TCP, UDP, ICMP, IPv4 ARP, IGMP, PPPoE, Ethernet. Embedded 10BaseT/100BaseTX Ethernet physical layer. Support auto answer (half / full duplex mode). Support automatic MDI / MDIX. Support ADSL connection (PPPoE protocol support with PAP / CHAP authentication). Supports up to four independent ports. The internal memory of 16K bytes for TX / RX cache. 3.3V operating voltage, I / O port can withstand 5V voltage.
This module is based on the WIZnet W5100 ethernet chip.

Ethernet Shield using w5200

Pentachord — Thu, 3 Jul 2025 08:56:34 +0900

Ethernet Board from PARALLAX (WIZnet Ethernet Board for QuickStart W5200)

The WIZnet W5200 for QuickStart allows your QuickStart board to serve data to an Ethernet network or even the Internet. The WIZnet W5200 chip provides an Ethernet to SPI bridge which is interfaced with Parallax’s 8-core microcontroller, the Propeller P8X32A. The data served to a network can be anything you want – web pages, serial data, email, and more.
Many useful demo programs are available for download from the product page to get you started, including a webserver capable of serving dynamic data from the SD card to your favorite browser. Advanced users can develop firmware that allows the WIZnet W5200 board + QuickStart to respond to or generate any type of network traffic.

2014/04/09 23:34 · Joachim Wuelbeck

W5200 Ethernet Module(Gadgeteer Compatible) from DFRobot

This W5200 Ethernet Module is .NET Gadgeteer compatible, which uses the .NET Micro Framework to make writing code for your device as easy as writing a desktop, Web or Windows Phone application.
This module is composed of a fully TCP/IP stack. The Ethernet application can be easily implemented via a simple socket program. SPI is provided for easy connection to the .NET Gadgeteer main board. Compared to the W5100 it doubles the simultaneous socket connections up to 8. The onboard LED indicates the network state between 10Mb and 100Mb.
You can easily let your Gadgeteer online through this module and then your Gadgeteer main board can easily controlled wherever Internet is available. There are massive applications of it ranging from industry to avionics, telecommunication, and multimedia.

DINo V2 from KMP Electronics

After some time spent on tuning Souliss drivers for WIZnet W5200 Ethernet controller equipped on KMP Electronics DINo v2, we got a full support of new features included in new Alpha 5 with focus on plug&play.
Diving into the examples prepared for DINo you will found no longer need to set Quick Configuration paramters and IP configuration, that's the new inSketch mode included in the last Souliss release. Just load the example on your DINo and connect the boards to the network, they will join and be discovered by your Android smartphone automatically, doesn't matter your IP configuration.

Ethernet Extension from TinkerForge

With this Ethernet Extension you can control Bricks and Bricklets and integrate them into a LAN. 10BaseT/100BaseTX Ethernet is supported and the module is 1000BaseTX compatible. The Extension is available in two variants: The PoE variant features a integrated PoE power supply. It allows to power the connected modules over industry standard IEEE 802.3af, such that a PoE injector as well as PoE switches can be used to power stacks. Additionally a variant without PoE is available.
This module is based on the WIZnet W5200 ethernet chip.

Pentachord

W7500

W7500

Features

Details

WIZwiki-W7500 mbed Starter Kit

WIZwiki-W7500 mbed Starter Kit

한국어

English

WIZwiki-W7500ECO

WIZwiki-W7500ECO

WIZwiki Platform

Features

Firmware

Getting Started

Make New WIZwiki-W7500ECO Projects

Technical Reference

Etc.

See Also

WIZwiki-W7500P

WIZwiki-W7500P

WIZwiki Platform

Features

Firmware

Getting Started

Make New WIZwiki-W7500P Projects

Technical Reference

Etc.

See Also

WIZwiki-W7500

WIZwiki-W7500

WIZwiki Platform

Features

Firmware

Getting Started

Make New WIZwiki-W7500 Projects

Technical Reference

Etc.

See Also

W5500 Ethernet Shield

W5500 Ethernet Shield

Overview

Available Board List

Getting Started

Language

Feature

Hardware Configuration

Pins usage on Arduino & ARM mbed

SPI Operation & Timing Diagram

Technical Reference

Etc.

See Also

BLE to Ethernet

BLE to Ethernet

Development Environment

Firmware

Hardware

PC Tools

Base Protocol

Code configuration

uart_init

ble_stack_init

nus_c_init

db_discovery_init

spi0_master_init

user_ethernet_init

user_app_timer_init

user_app_timer_start

tcp_con_timer

tcps_to_ble

ble_to_tcps

ble_nus_c_evt_handler

uart_event_handle

Testing

H/W Setting

BLE Stack (SoftDevice) Writing

Ble to ethernet Board application Writing

PCA10040 application Writing

Config HyperTerminal & TCP Server

Data Input