I am using OpenBoard-AM335x from Phytec india and have installed WIN EC7.
My problem is, i can not create a KITL connection between platform builder and my device.
To create a KITL connection i have followed steps as below:
Device side setup:-
started device, opened EBOOT configuration at boot time
selected option '4' for Network settings in EBOOT main menu
set static-ip=192.168.0.182 subnet-mask=255.255.255.0 and router-ip=192.168.0.1(our router ip address, device is connected with LAN cable)
selected Boot from Internal EMAC from boot device menu
PC side setup:-
set ip of PC to 192.168.0.102, subnet-mask=255.255.255.0 and default gateway=192.168.0.1 (pc is connected with wi-fi router)
disabled firewall and anti-virus software
opened Target->Connectivity options in Visual studio 2008
Added device with target device name "AM335X" and Associated OS design with "Windows CE" in Add device menu
set Target device to "AM335X", Kernel Download to "Ethernet", Kernel Transport "Ethernet", Kernel Debugger to "KdStub" in Kernel Service Map menu
opened "settings" of Kernel Download
Now platform builder is waiting for active devices
Next, started device to boot with above described settings, the device starts to send messages "sent BOOTME to 255.255.255.255" to serial console. But, nothing detected by platform builder.
Device's serial log is as follows:
--------------------------------------------------------------------------------
Main Menu
--------------------------------------------------------------------------------
[1] Show Current Settings
[2] Select Boot Device
[3] Select KITL (Debug) Device
[4] Network Settings
[5] SDCard Settings
[6] Set Device ID
[7] Save Settings
[8] Flash Management
[9] Enable/Disable OAL Retail Messages
[a] Select Display Resolution
[b] Select OPP Mode
[0] Exit and Continue
Selection: 1
Main:
Boot device: Internal EMAC
Debug device: Internal EMAC
Retail Msgs: disabled
Device ID: 0
Display Res: 7in LCD_017 (800x480#60Hz)
Flashing NK.bin: disabled
OPP Mode: MPU[720Mhz # 1.26V]
SDCard:
Filename: "nk.bin"
Network:
KITL state: enabled
KITL type: active
KITL mode: interrupt
DHCP: disabled
IP address: 192.168.0.182
IP mask: 255.255.255.0
IP router: 192.168.0.1
Eth MAC Addr : 00:18:31:8d:c6:92 (Boot settings)
Eth MAC Addr 1: 00:18:31:8d:c6:93 (Boot settings)
VMINI: enabled
Note: USBFN RNDIS MAC Addr cannot be changed.
--------------------------------------------------------------------------------
Main Menu
--------------------------------------------------------------------------------
[1] Show Current Settings
[2] Select Boot Device
[3] Select KITL (Debug) Device
[4] Network Settings
[5] SDCard Settings
[6] Set Device ID
[7] Save Settings
[8] Flash Management
[9] Enable/Disable OAL Retail Messages
[a] Select Display Resolution
[b] Select OPP Mode
[0] Exit and Continue
Selection: 0
ShowSDLogo
Init HW: controller RST
SDCARD: requested speed 1000000, actual speed 1000000
SDCARD: requested speed 25000000, actual speed 19200000
BLSDCardReadLogo: cannot open Logo.bmp
+Cpsw3gInit(0x4a100000, 0x00000001, 0x8fefff6c) v0.3
Auto negotitation failed
Phy_init: Auto negotitation completed
Cpsw3gInit, wait link up on mac port:1.
Cpsw3gInit, LINK down on port:1.
INFO: Boot device uses MAC 00:18:31:8d:c6:92
INFO: *** Device Name AM335X-50834 ***
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Any suggestions/comments ?
Thanks in advance.
Check that you don't have any firewall installed on your machine preventing platform builder from receiving packets from your device. If both machines are on the same IP subnet you should be able to receive broadcast packets. Usually if you have the Windows firewall enabled you will get a message reporting that platform builder is opening a port on your PC and if you don't allow the operation it will not be able to connect.
Related
I'm trying to get MAC address of devices connected in my subnet.
For that, I send a ping request and read ARP table in the NIC (under Windows : arp -a)
I'm trying to mimic this behavior in a ESP32-POE module from Olimex with LAN8720 NIC.
I can do the trick on a W5500 NIC with : W5500.readSnDHAR(i,destMac);
How can I achieve that on ESP32-POE/LAN8720 ? (Arduino or ESP-IDF)
I want to share a WireGuard VPN connection over WiFi in Raspberry pi 3 B+.
I connect my RPI with LAN port to internet (Huawei 4G modem router),
and I create a WireGuard connection that is already connected (tested ping and traceroute, everything is ok)
But now, I want to share my WireGuard VPN connection over WiFi AP.
I already created a WiFi AP (with internal RPI WiFi) and shared the internet, but the internet is already shared from the LAN connection (same bridge).
And I have another problem: the IP address assigned to the WiFi client gets it IP from the Huawei 4G modem route (192.168.8.X), and its default gateway is set to 192.168.8.1 (Huawei 4G modem route IP address).
What can I do?
I’m using Golang to try to send packets through UDP to an IP address and port provided by STUN. The goal is to communicate between two devices without having to open a port in the firewall, as both devices are located in a different network.
The program runs on both devices in the following manner:
Device 1 waits for device 2 to send the IP address and port found by STUN. This goes through an open port in the firewall of device 1. (Only for device 1 an open port is possible)
The problem is that device 2 does not receive any packets through the port found by STUN.
I think the problem consists of the router not knowing the connection to device 2. Device 2 is connected with the router, but the router doesn’t know what to do with the packets.
Do you have any idea how to solve this problem?
Thanks!
I am doing some bluetooth development where I have a device running a SPP service. However i cannot set up a virtual comport where with the device. Windows discovers the device in the general bluetooth tab but when looking in the browse window in: More bluetooth options -> COM ports -> Add... -> Outgoing -> Browse, I cannot find the device.
Remote device info:
Name: BP
Alias: BP
Paired: yes
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: RFCOMM (00000003-0000-1000-8000-00805f9b34fb)
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
RSSI: -43
TxPower: 8
What services are required to be able to establish a virtual comport connection with my device? Are there any special requirments on characteristics?
SPP should be supported according to https://support.microsoft.com/en-us/help/10568/windows-10-supported-bluetooth-profiles
I have a REST service running on Mac OS X, which im currently accessing using "localhost:8888" and "10.0.2.2:8888"
I want to access the same service from another computer which is in the same network.
I disabled the firewall also and I typed
nc -v 192.168.1.3 8888
and got the result as
nc: connectx to 192.168.1.3 port 8888 (tcp) failed: Connection refused
currently i use localhost (to access using java application) and 10.0.2.2 (to access using android application runs in the simulator) which both runs on the same machine which the server runs too.
I want to put the android application to my phone and give the machine ip addess ( because if i connect to internet via wifi, it'll be in the same local area network) i should be able to access my service runs on my machine.
can some one please tell me what im doing wrong here? Thank you
You can't access localhost from your front end code. It needs to refer to the server's name or address.
The localhost address should be 127.0.0.1, which is in the loopback range of addresses. Any address in the 127.0.0.0/8 block can never appear anywhere on any network, nor can any address in that block be used as a source or destination address outside a host. It is not possible for one host to access anything in that address range on another host.
The goes back at least as far as RFC 990, ASSIGNED NUMBERS:
The class A network number 127 is assigned the "loopback" function,
that is, a datagram sent by a higher level protocol to a network 127
address should loop back inside the host. No datagram "sent" to a
network 127 address should ever appear on any network anywhere.
RFC 1122, Requirements for Internet Hosts -- Communication Layers:
(g) { 127, }
Internal host loopback address. Addresses of this form MUST NOT
appear outside a host.
Also RFC 3330, Special-Use IPv4 Addresses:
127.0.0.0/8 - This block is assigned for use as the Internet host loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block should loop back inside the host.
This is ordinarily implemented using only 127.0.0.1/32 for loopback,
but no addresses within this block should ever appear on any network
anywhere [RFC1700, page 5].