fprintf won't go to slog.

Sent from my BlackBerry 10 smartphone on the Rogers network.
  Original Message
From: William Hoey
Sent: Wednesday, February 18, 2015 3:22 PM
To: drivers-networking
Reply To: drivers-networking@community.qnx.com
Subject: Re: Buffer handling within an io-pkt transmit routine


Many thanks for the reply

So the following works

{
   uint8_t  test[] = {0x45,0x00,0x00,0x2e,0x7b,0x3a,0x00,0x00,0x3f,0x11,0x7b,0xb3,0xc0,0xa8,0x01,0x82,0xc0,0xa8,0x01,
0xff,0x1d,0x76,0x1d,0x76,0x00,0x1a,0xee,0x6c,0x20,0x8f,0x61,0x00,0x20,0x00,0x00,0xa5,0x07,0xb0,0xe0,0x00,0x00,0x00,0x00,
0x00,0x00,0x00};
   memcpy(register_configuration->transmit_buffer, test, sizeof(test));
   *(register_configuration->transmit_length_register) = sizeof(test);
   *(register_configuration->transmit_control_register) = TRANSMITTER_START;
}

What I was trying was

{
   uint8_t ethernet_media_access_control_address[] = {0x57, 0x20, 0x48, 0x4F, 0x45, 0x59, 0x57, 0x20, 0x48, 0x5F, 0x55, 
0x69, 0x08, 0x00};
   m_copydata(m, sizeof(ethernet_media_access_control_address), ((m->m_pkthdr.len)-
(sizeof(ethernet_media_access_control_address))), register_configuration->transmit_buffer);
   *(register_configuration->transmit_length_register) = ((m->m_pkthdr.len)-
(sizeof(ethernet_media_access_control_address)));
   *(register_configuration->transmit_control_register) = TRANSMITTER_START;
}

I am currently trying to print the packet in some nicely formatted way, for some reason any printf call with formatting 
arguments appear to end up in the slog.



_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post113331
To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

A dump of the packet sent when I set the IP address with ifconfig gives the following:

ff ff ff ff ff ff 57 20 48 4f 45 59 08 06 00 01 
08 00 06 04 00 01 57 20 48 4f 45 59 c0 a8 01 82 
00 00 00 00

Which I think is a correctly formatted ARP packet.

Armed with Sean's advice with regards to using fprint I think I have a better handle on what is going on.

I suspect that the transmit routine is working correctly, the first packet is ARP packet which is not forwarded by the 
router on the other end of the SLIP interface. 

Could the issue be related to how the device is registered with io-pkt?

The IP stack on the other RTOS only supports ethernet, so the drivers registers as an ethernet driver and sets the 
following flags during initialisation:

xxxFlagSet(&network_device_configuration->end, IFF_POINTOPOINT | IFF_NOARP | IFF_SIMPLEX | IFF_BROADCAST | IFF_UP | IFF_RUNNING);

Under QNX in the attach routine I set the following flags:

ifp->if_flags = IFF_POINTOPOINT | IFF_NOARP | IFF_SIMPLEX | IFF_BROADCAST;

I then set the IFF_RUNNING runnnig in the initialisation routine.

I suspect I need to do a little bit more under io-pkt as ifconfig gives the following:

Other RTOS:

lo0     Link type:Local loopback  Queue:none
        inet 127.0.0.1  mask 255.255.255.255
        UP RUNNING LOOPBACK MULTICAST NOARP ALLMULTI
        MTU:1500  metric:1  VR:0  ifindex:1
        RX packets:203 mcast:0 errors:0 dropped:0
        TX packets:203 mcast:0 errors:0
        collisions:0 unsupported proto:0
        RX bytes:217k  TX bytes:217k

fr0     Link type:1  HWaddr 57:20:48:4f:45:59  Queue:none
        inet 192.168.1.130  mask 255.255.255.0  broadcast 192.168.1.255
        UP RUNNING SIMPLEX BROADCAST NOARP
        MTU:1500  metric:1  VR:0  ifindex:2
        RX packets:376 mcast:0 errors:0 dropped:0
        TX packets:158 mcast:0 errors:0
        collisions:0 unsupported proto:0
        RX bytes:39k  TX bytes:137k

QNX

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
fr0: flags=88d3<UP,BROADCAST, RUNNING,NOARP,SIMPLEX > mtu 1500
        address: 57:20:48:4f:45:59
        media: Ethernet none
        inet 192.168.1.130 -> 192.168.1.255 netmask 0xffffff00 broadcast 192.168.1.255

On this piece of hardware the link is always available and there is no phy or link management required, is it possible 
under io-pkt to simply hard code the link to be 10BaseT Full Duplex always UP? or can io-pkt support a SLIP interface 
(as this would avoid the need for the network driver to add and remove the Ethernet Header)?

Many Thanks Again.