Search Results

Hi Hendrik, you could use gethostbyname() or if you already have the host as an IP use the IP directly. There is a utility function to help you with that - IP_IPV4_ParseIPv4Addr()

You are correct, we are almost Berkeley compatible but not up to 100%. You can use IP_IGMP_JoinGroup()/IP_IGMP_LeaveGroup() as a replacement for IP_ADD_MEMBERSHIP and IP_DROP_MEMBERSHIP. At the moment there is no alternative for IP_MULTICAST_IF, we are currently working on a new feature which would allow SO_BINDTODEVICE, which in turn would allow you to do something similar to IP_MULTICAST_IF, you can force a specific socket to use a specific interface. For IP_MULTICAST_LOOP there is no alternat…

I assume you are using the Dialog SDK, which includes our stack in library form? A library can not be easily extended with a new class. In case of doubt please contact Dialog.

Quote from ddbug: “But may I ask, is the demo version of the usb host library crippled in any way, such as error handling disabled? -- dd ” No, it is not crippled in any way. Are you using the debug version? The terminal output is disabled in the release version. Furthermore, is was USBH_ConfigSupportExternalHubs called inside USBH_X_Config with the parameter set to 1?

The connector on the second one looks like regular mini-b, so it probably can not be used as a host. With the first board you can use a regular micro OTG adapter.

STM32F446 should be similar to the other STM32F4xx MCUs. emUSB-Host always requires an RTOS, that is correct.

In that project the RCC settings are done inside the SystemInit() function in the system_stm32f7xx.c file. The RCC settings for the USB controllers are done in the function _InitUSBHw() of the respective config file (USBH_Config_STM32F7xxFS_ST_STM32F746G_Discovery.c or USBH_Config_STM32F7xxHS_ST_STM32F746G_Discovery.c). BTW: I have read your russian guide on creating a first project with ES on the LPC1768, it is very good. Thank you, great job.

We do not have a package for LPC1768 readily available. Please check the NXP SEGGER Eval Software page segger.com/evaluate-our-software/nxp/ maybe you can download a package for a different MCU which is also available to you.

The device does not seem to enumerate. Could you please set a breakpoint in the USB ISR routine and see if you arrive there when you connect the cable to your PC? I see that you have used an emPower project as a base, it will not work on the LPC1768 out of the box as it is a completely different MCU...

MByte/s is correct, but it is for a different MCU (LPC43 with the EHCI driver (we will add more info to the website on that)). On the SAMV7 we do not use DMA as the performance can not be improved by using DMA. Out most recent performance measurements on the Atmel ATSAMV7 XPlainedUltra are as follows: Read bench (target measurement): 28008 KByte/sec Read bench (host measurement): 28054 KByte/sec Write bench (target measurement): 40992 KByte/sec Write bench (host measurement): 41025 KByte/sec

Whether DMA is used or not depends on the driver (some USB controllers do not even have DMA). Which driver are you using?

Hi Santhosh, the Eval version is not designed to run on the EK board. Furthermore - mice & keyboards are usually not CDC devices.

Hi, unfortunately this is not possible, check out our FAQ in the wiki: wiki.segger.com/EmUSB-Device

As discussed via mail - please update to the newest version.

See here .

Sorry about that, it will be re-added in the next version of the SEGGER Eval Software. For now you can download the missing files here: http://download.segger.com/Yan/USBBULK_Libs_180419.zip

In the meantime you can check out our SEGGER Eval Software which has emUSB-Device / emUSB-Host for several STM32 and Atmel MCUs: segger.com/evaluate-our-software/st-microelectronics/ segger.com/evaluate-our-software/atmel/

Sorry about that, but this is not available right at this moment. In the future the product ES Pro ( segger.com/products/developmen…io/editions/pro-cortex-m/ ) will be available for free for non-commercial use (without the hardware components). The ES Pro package contains all our middleware in object code. There will be a news article regarding this short term. Please check our news ticker to stay up to date.

Uhhh, this is ancient. Please update to the newest.

Yes, with the define DEBUG=1 you can use C Source Code (23 lines) The USB_X_Log/USB_X_Warn are located in the USB_ConfigIO.c file, if possible you should use RTT as it influences the timing the least of all possible I/O methods.