<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Vybrid ProcessorsのトピックMAC-ENET doesn't send data in TX</title>
    <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427097#M4745</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are currently trying to get Linux running on our custom Board.&lt;/P&gt;&lt;P&gt;At this point i'm realy exhausted because of the MAC_ENET.&lt;/P&gt;&lt;P&gt;The Kernel Source we are using is intended for the Vybrid and we are just modifing it&lt;/P&gt;&lt;P&gt;to fit our needs. The Bootloader which is loading the Kernel and preparing the clock settings, is our&lt;/P&gt;&lt;P&gt;own source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On boot the PHY controller is found and the corresponding driver is loaded. Additionaly&lt;/P&gt;&lt;P&gt;i get informed if the ethernet-cable is pluged in. I assume this information are transfered via MDIO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But at the point where "sending discover..." is issued by BusyBox i cant see any action on the&lt;/P&gt;&lt;P&gt;TXEN Pin(Oscilloscope used).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is now, what could be the Problem assuming, that the Kernel code is correct.&lt;/P&gt;&lt;P&gt;//Kernelcode works with the corresponding example board. Based on the fact, that the action i want to see is pure vybrid and not depending on the architekture/board below. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Apr 2015 09:09:52 GMT</pubDate>
    <dc:creator>torbenlüdeking</dc:creator>
    <dc:date>2015-04-21T09:09:52Z</dc:date>
    <item>
      <title>MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427097#M4745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are currently trying to get Linux running on our custom Board.&lt;/P&gt;&lt;P&gt;At this point i'm realy exhausted because of the MAC_ENET.&lt;/P&gt;&lt;P&gt;The Kernel Source we are using is intended for the Vybrid and we are just modifing it&lt;/P&gt;&lt;P&gt;to fit our needs. The Bootloader which is loading the Kernel and preparing the clock settings, is our&lt;/P&gt;&lt;P&gt;own source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On boot the PHY controller is found and the corresponding driver is loaded. Additionaly&lt;/P&gt;&lt;P&gt;i get informed if the ethernet-cable is pluged in. I assume this information are transfered via MDIO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But at the point where "sending discover..." is issued by BusyBox i cant see any action on the&lt;/P&gt;&lt;P&gt;TXEN Pin(Oscilloscope used).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is now, what could be the Problem assuming, that the Kernel code is correct.&lt;/P&gt;&lt;P&gt;//Kernelcode works with the corresponding example board. Based on the fact, that the action i want to see is pure vybrid and not depending on the architekture/board below. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Apr 2015 09:09:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427097#M4745</guid>
      <dc:creator>torbenlüdeking</dc:creator>
      <dc:date>2015-04-21T09:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427098#M4746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/timesyssupport"&gt;timesyssupport&lt;/A&gt; can you help with this case?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Apr 2015 16:52:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427098#M4746</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2015-04-22T16:52:22Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427099#M4747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Torben,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you provide details on U-boot version (or is this a completely custom bootloader?), Linux kernel version, and what reference hardware your design is based on?&lt;/P&gt;&lt;P&gt;Can you also provide a boot log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Timesys Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Apr 2015 16:58:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427099#M4747</guid>
      <dc:creator>timesyssupport</dc:creator>
      <dc:date>2015-04-22T16:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427100#M4748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Timesys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Bootloader is a completely custom Bootloader. We are running Linux Kernel Version 3.0.15 based on the kernel sources for the the armstoneA5 produced by F+S Net.&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;Linux Kernel wrote:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Linux version 3.0.15 (torben@Torben) (gcc version 4.7.2 (crosstool-NG 1.18.0) ) #230 Wed Apr 22 16:25:23 CEST 2015&lt;/P&gt;
&lt;P&gt;CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c53c7d&lt;/P&gt;
&lt;P&gt;CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache&lt;/P&gt;
&lt;P&gt;Memory policy: ECC disabled, Data cache writeback&lt;/P&gt;
&lt;P&gt;On node 0 totalpages: 128000&lt;/P&gt;
&lt;P&gt;free_area_init_node: node 0, pgdat 804890f0, node_mem_map 8b800000&lt;/P&gt;
&lt;P&gt;&amp;nbsp; DMA zone: 368 pages used for memmap&lt;/P&gt;
&lt;P&gt;&amp;nbsp; DMA zone: 0 pages reserved&lt;/P&gt;
&lt;P&gt;&amp;nbsp; DMA zone: 46736 pages, LIFO batch:15&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Normal zone: 632 pages used for memmap&lt;/P&gt;
&lt;P&gt;&amp;nbsp; Normal zone: 80264 pages, LIFO batch:15&lt;/P&gt;
&lt;P&gt;pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768&lt;/P&gt;
&lt;P&gt;pcpu-alloc: [0] 0&lt;/P&gt;
&lt;P&gt;Built 1 zonelists in Zone order, mobility grouping on.&amp;nbsp; Total pages: 127000&lt;/P&gt;
&lt;P&gt;Kernel command line: root=/dev/mmcblk0p1 rw rootfstype=ext2 console=ttymxc0,115200 mem=500M debug init=/sbin/init&lt;/P&gt;
&lt;P&gt;PID hash table entries: 2048 (order: 1, 8192 bytes)&lt;/P&gt;
&lt;P&gt;Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)&lt;/P&gt;
&lt;P&gt;Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)&lt;/P&gt;
&lt;P&gt;Memory: 500MB = 500MB total&lt;/P&gt;
&lt;P&gt;Memory: 502556k/502556k available, 9444k reserved, 0K highmem&lt;/P&gt;
&lt;P&gt;Virtual kernel memory layout:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; vector&amp;nbsp; : 0xffff0000 - 0xffff1000&amp;nbsp;&amp;nbsp; (&amp;nbsp;&amp;nbsp; 4 kB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; fixmap&amp;nbsp; : 0xfff00000 - 0xfffe0000&amp;nbsp;&amp;nbsp; ( 896 kB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DMA&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 0xf4600000 - 0xffe00000&amp;nbsp;&amp;nbsp; ( 184 MB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; vmalloc : 0x9f800000 - 0xf2000000&amp;nbsp;&amp;nbsp; (1320 MB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; lowmem&amp;nbsp; : 0x80000000 - 0x9f400000&amp;nbsp;&amp;nbsp; ( 500 MB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; modules : 0x7f000000 - 0x80000000&amp;nbsp;&amp;nbsp; (&amp;nbsp; 16 MB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .init : 0x80008000 - 0x8002d000&amp;nbsp;&amp;nbsp; ( 148 kB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .text : 0x8002d000 - 0x80459000&amp;nbsp;&amp;nbsp; (4272 kB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .data : 0x8045a000 - 0x80489d20&amp;nbsp;&amp;nbsp; ( 192 kB)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; .bss : 0x80489d44 - 0x804ca7b8&amp;nbsp;&amp;nbsp; ( 259 kB)&lt;/P&gt;
&lt;P&gt;SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1&lt;/P&gt;
&lt;P&gt;NR_IRQS:432&lt;/P&gt;
&lt;P&gt;MVF GPIO hardware&lt;/P&gt;
&lt;P&gt;sched_clock: 32 bits at 93MHz, resolution 10ns, wraps every 45820ms&lt;/P&gt;
&lt;P&gt;Console: colour dummy device 80x30&lt;/P&gt;
&lt;P&gt;Calibrating delay loop... 124.31 BogoMIPS (lpj=621568)&lt;/P&gt;
&lt;P&gt;pid_max: default: 32768 minimum: 301&lt;/P&gt;
&lt;P&gt;Mount-cache hash table entries: 512&lt;/P&gt;
&lt;P&gt;CPU: Testing write buffer coherency: ok&lt;/P&gt;
&lt;P&gt;NET: Registered protocol family 16&lt;/P&gt;
&lt;P&gt;mcf_edma: Initialized successfully&lt;/P&gt;
&lt;P&gt;Using UART1 for UART port A (TXD/RXD/RTS/CTS)&lt;/P&gt;
&lt;P&gt;Using UART2 for UART port B (TXD/RXD)&lt;/P&gt;
&lt;P&gt;Using UART3 for UART port C (TXD/RXD)&lt;/P&gt;
&lt;P&gt;Booting on CPU #0 CA5 r0p1 on port #2, 2 CPU(s)&lt;/P&gt;
&lt;P&gt;Level 1 cache: I: 32768 Bytes/2 ways, D: 32768 Bytes/4 ways&lt;/P&gt;
&lt;P&gt;Level 2 cache: 524288 bytes/8 ways&lt;/P&gt;
&lt;P&gt;L310 cache controller enabled&lt;/P&gt;
&lt;P&gt;l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02060000, Cache size: 524288 B&lt;/P&gt;
&lt;P&gt;IMX usb wakeupx probe. id=0&lt;/P&gt;
&lt;P&gt;the wakeup pdata is 0x9e0b8040&lt;/P&gt;
&lt;P&gt;IMX usb wakeupx probe. id=1&lt;/P&gt;
&lt;P&gt;the wakeup pdata is 0x9e0b8180&lt;/P&gt;
&lt;P&gt;bio: create slab &amp;lt;bio-0&amp;gt; at 0&lt;/P&gt;
&lt;P&gt;SCSI subsystem initialized&lt;/P&gt;
&lt;P&gt;usbcore: registered new interface driver usbfs&lt;/P&gt;
&lt;P&gt;usbcore: registered new interface driver hub&lt;/P&gt;
&lt;P&gt;usbcore: registered new device driver usb&lt;/P&gt;
&lt;P&gt;Advanced Linux Sound Architecture Driver Version 1.0.24.&lt;/P&gt;
&lt;P&gt;Switching to clocksource pit&lt;/P&gt;
&lt;P&gt;NET: Registered protocol family 2&lt;/P&gt;
&lt;P&gt;IP route cache hash table entries: 4096 (order: 2, 16384 bytes)&lt;/P&gt;
&lt;P&gt;TCP established hash table entries: 16384 (order: 5, 131072 bytes)&lt;/P&gt;
&lt;P&gt;TCP bind hash table entries: 16384 (order: 4, 65536 bytes)&lt;/P&gt;
&lt;P&gt;TCP: Hash tables configured (established 16384 bind 16384)&lt;/P&gt;
&lt;P&gt;TCP reno registered&lt;/P&gt;
&lt;P&gt;UDP hash table entries: 256 (order: 0, 4096 bytes)&lt;/P&gt;
&lt;P&gt;UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)&lt;/P&gt;
&lt;P&gt;NET: Registered protocol family 1&lt;/P&gt;
&lt;P&gt;RPC: Registered named UNIX socket transport module.&lt;/P&gt;
&lt;P&gt;RPC: Registered udp transport module.&lt;/P&gt;
&lt;P&gt;RPC: Registered tcp transport module.&lt;/P&gt;
&lt;P&gt;RPC: Registered tcp NFSv4.1 backchannel transport module.&lt;/P&gt;
&lt;P&gt;Static Power Management for Freescale Vybrid&lt;/P&gt;
&lt;P&gt;cpaddr = 9f880000 suspend_iram_base=9f810000 iram_paddr 3f000000&lt;/P&gt;
&lt;P&gt;PM driver module loaded&lt;/P&gt;
&lt;P&gt;JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.&lt;/P&gt;
&lt;P&gt;msgmni has been set to 981&lt;/P&gt;
&lt;P&gt;alg: No test for stdrng (krng)&lt;/P&gt;
&lt;P&gt;NET: Registered protocol family 38&lt;/P&gt;
&lt;P&gt;cryptodev: driver loaded.&lt;/P&gt;
&lt;P&gt;io scheduler noop registered&lt;/P&gt;
&lt;P&gt;io scheduler deadline registered&lt;/P&gt;
&lt;P&gt;io scheduler cfq registered (default)&lt;/P&gt;
&lt;P&gt;Console: switching to colour frame buffer device 100x30&lt;/P&gt;
&lt;P&gt;fb0: Layer0 fb device registered successfully.&lt;/P&gt;
&lt;P&gt;fb1:&amp;nbsp; fb device registered successfully.&lt;/P&gt;
&lt;P&gt;fb2:&amp;nbsp; fb device registered successfully.&lt;/P&gt;
&lt;P&gt;fb3:&amp;nbsp; fb device registered successfully.&lt;/P&gt;
&lt;P&gt;Serial: MVF driver&lt;/P&gt;
&lt;P&gt;IMX UART RTS/CTS enabled&lt;/P&gt;
&lt;P&gt;IMX UART FIFO enabled&lt;/P&gt;
&lt;P&gt;imx-uart.0: ttymxc0 at MMIO 0x40027000 (irq = 93) is a IMX&lt;/P&gt;
&lt;P&gt;console [ttymxc0] enabled&lt;/P&gt;
&lt;P&gt;IMX UART FIFO enabled&lt;/P&gt;
&lt;P&gt;imx-uart.2: ttymxc2 at MMIO 0x40029000 (irq = 95) is a IMX&lt;/P&gt;
&lt;P&gt;IMX UART FIFO enabled&lt;/P&gt;
&lt;P&gt;imx-uart.3: ttymxc3 at MMIO 0x4002a000 (irq = 96) is a IMX&lt;/P&gt;
&lt;P&gt;brd: module loaded&lt;/P&gt;
&lt;P&gt;mvf-adc mvf-adc.0: attached adc driver&lt;/P&gt;
&lt;P&gt;mvf-adc mvf-adc.1: attached adc driver&lt;/P&gt;
&lt;P&gt;FEC Ethernet Driver&lt;/P&gt;
&lt;P&gt;fec_enet_mii_bus: probedx&lt;/P&gt;
&lt;P&gt;fec_enet_mii_bus: probedx&lt;/P&gt;
&lt;P&gt;ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver&lt;/P&gt;
&lt;P&gt;add wake up source irq 107&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.0: irq 107, io base 0x40034000&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00&lt;/P&gt;
&lt;P&gt;hub 1-0:1.0: USB hub found&lt;/P&gt;
&lt;P&gt;hub 1-0:1.0: 1 port detected&lt;/P&gt;
&lt;P&gt;add wake up source irq 108&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.1: irq 108, io base 0x400b4000&lt;/P&gt;
&lt;P&gt;fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00&lt;/P&gt;
&lt;P&gt;hub 2-0:1.0: USB hub found&lt;/P&gt;
&lt;P&gt;hub 2-0:1.0: 1 port detected&lt;/P&gt;
&lt;P&gt;Initializing USB Mass Storage driver...&lt;/P&gt;
&lt;P&gt;usbcore: registered new interface driver usb-storage&lt;/P&gt;
&lt;P&gt;USB Mass Storage support registered.&lt;/P&gt;
&lt;P&gt;ARC USBOTG Device Controller driver (1 August 2005)&lt;/P&gt;
&lt;P&gt;mousedev: PS/2 mouse device common for all mice&lt;/P&gt;
&lt;P&gt;snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0&lt;/P&gt;
&lt;P&gt;i2c /dev entries driver&lt;/P&gt;
&lt;P&gt;sdhci: Secure Digital Host Controller Interface driver&lt;/P&gt;
&lt;P&gt;sdhci: Copyright(c) Pierre Ossman&lt;/P&gt;
&lt;P&gt;sdhci sdhci-esdhc-imx.1: no write-protect pin available!&lt;/P&gt;
&lt;P&gt;mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA&lt;/P&gt;
&lt;P&gt;MVF ASRC registered&lt;/P&gt;
&lt;P&gt;mmc0: host does not support reading read-only switch. assuming write-enable.&lt;/P&gt;
&lt;P&gt;mmc0: new SDHC card at address aaaa&lt;/P&gt;
&lt;P&gt;mmcblk0: mmc0:aaaa SU04G 3.69 GiB&lt;/P&gt;
&lt;P&gt;caam caam.0: device ID = 0x0a18010000000000&lt;/P&gt;
&lt;P&gt;caam caam.0: job rings = 2, qi = 0&lt;/P&gt;
&lt;P&gt; mmcblk0: p1&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(md5),cbc(aes)) (authenc-hmac-md5-cbc-aes-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-md5-cbc-aes-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha1),cbc(aes)) (authenc-hmac-sha1-cbc-aes-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha1-cbc-aes-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha224),cbc(aes)) (authenc-hmac-sha224-cbc-aes-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha224-cbc-aes-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha256),cbc(aes)) (authenc-hmac-sha256-cbc-aes-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha256-cbc-aes-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(md5),cbc(des3_ede)) (authenc-hmac-md5-cbc-des3_ede-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-md5-cbc-des3_ede-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha1),cbc(des3_ede)) (authenc-hmac-sha1-cbc-des3_ede-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha1-cbc-des3_ede-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha224),cbc(des3_ede)) (authenc-hmac-sha224-cbc-des3_ede-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha224-cbc-des3_ede-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha256),cbc(des3_ede)) (authenc-hmac-sha256-cbc-des3_ede-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha256-cbc-des3_ede-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(md5),cbc(des)) (authenc-hmac-md5-cbc-des-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-md5-cbc-des-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha1),cbc(des)) (authenc-hmac-sha1-cbc-des-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha1-cbc-des-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha224),cbc(des)) (authenc-hmac-sha224-cbc-des-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha224-cbc-des-caam&lt;/P&gt;
&lt;P&gt;alg: No test for authenc(hmac(sha256),cbc(des)) (authenc-hmac-sha256-cbc-des-caam)&lt;/P&gt;
&lt;P&gt;caam caam.0: authenc-hmac-sha256-cbc-des-caam&lt;/P&gt;
&lt;P&gt;caam caam.0: cbc-aes-caam&lt;/P&gt;
&lt;P&gt;caam caam.0: cbc-3des-caam&lt;/P&gt;
&lt;P&gt;caam caam.0: cbc-des-caam&lt;/P&gt;
&lt;P&gt;platform caam_jr.0: registering rng-caam&lt;/P&gt;
&lt;P&gt;platform caam_sm.0: caam_sm_test: 8-byte key test match OK&lt;/P&gt;
&lt;P&gt;platform caam_sm.0: caam_sm_test: 16-byte key test match OK&lt;/P&gt;
&lt;P&gt;platform caam_sm.0: caam_sm_test: 32-byte key test match OK&lt;/P&gt;
&lt;P&gt;platform caam_secvio.0: security violation service handlers armed&lt;/P&gt;
&lt;P&gt;ALSA device list:&lt;/P&gt;
&lt;P&gt;&amp;nbsp; No soundcards found.&lt;/P&gt;
&lt;P&gt;TCP cubic registered&lt;/P&gt;
&lt;P&gt;NET: Registered protocol family 17&lt;/P&gt;
&lt;P&gt;VFP support v0.3: implementor 41 architecture 2 part 30 variant 5 rev 1&lt;/P&gt;
&lt;P&gt;snvs_rtc snvs_rtc.0: hctosys: 1970-01-01 not accepted as valid date&lt;/P&gt;
&lt;P&gt;EXT2-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended&lt;/P&gt;
&lt;P&gt;VFS: Mounted root (ext2 filesystem) on device 179:1.&lt;/P&gt;
&lt;P&gt;Freeing init memory: 148K&lt;/P&gt;
&lt;P&gt;Bad inittab entry at line 22&lt;/P&gt;
&lt;P&gt;Bad inittab entry at line 36&lt;/P&gt;
&lt;P&gt;Starting logging: OK&lt;/P&gt;
&lt;P&gt;Initializing random number generator... EXT2-fs (mmcblk0p1): error: ext2_lookup: deleted inode referenced: 24215&lt;/P&gt;
&lt;P&gt;EXT2-fs (mmcblk0p1): error: ext2_lookup: deleted inode referenced: 24215&lt;/P&gt;
&lt;P&gt;read-only file system detected...done&lt;/P&gt;
&lt;P&gt;Starting system message bus: done&lt;/P&gt;
&lt;P&gt;Starting network...&lt;/P&gt;
&lt;P&gt;eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, irq=-1)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;PHY: 1:00 - Link is Up - 10/Half&lt;/P&gt;
&lt;P&gt;Sending discover...&lt;/P&gt;
&lt;P&gt;Sending discover...&lt;/P&gt;
&lt;P&gt;No lease, failing&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;eth1: Freescale FEC PHY driver [Davicom DM9161B] (mii_bus:phy_addr=2:00, irq=-1)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;PHY: 2:00 - Link is Up - 100/Full&lt;/P&gt;
&lt;P&gt;Sending discover...&lt;/P&gt;
&lt;P&gt;Sending discover...&lt;/P&gt;
&lt;P&gt;No lease, failing&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Welcome to Buildroot&lt;/P&gt;
&lt;P&gt;buildroot login: root&lt;/P&gt;
&lt;P&gt;Password:&lt;/P&gt;
&lt;P&gt;#&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;EM&gt;I know there is still a lot of stuff to do ;-)&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you can see the PHY Chip is correct found and the driver loaded. Attached with my Oscilloscope i can see activity on the MDIO-Pins and also on the RX Pins (PHY to MAC_ENET). But not on the TX Pins as i would expect it when "sending discover".&amp;nbsp; &lt;BR /&gt;What i did next i navigated to the xmit function where as far as i can see it, the virtual adress used is correct, based on the previous call of ioremap.&lt;/P&gt;&lt;P&gt;But when triggered (Write to TDAR) no activity on the pin.&lt;/P&gt;&lt;P&gt;Now i'm wondering if i maybe missed some dependencies on the clock settings or something like this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards Torben&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Apr 2015 15:26:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427100#M4748</guid>
      <dc:creator>torbenlüdeking</dc:creator>
      <dc:date>2015-04-23T15:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427101#M4749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/timesyssupport"&gt;timesyssupport&lt;/A&gt; please continue with the follow up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Apr 2015 16:45:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427101#M4749</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2015-04-27T16:45:23Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427102#M4750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Torben,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are not in possession of ArmstoneA5 hardware,&amp;nbsp; it is a Vybrid variant we are not currently supporting in our own Vybrid efforts. Given that you are using a completely custom bootloader, this issue could be the result of improper initialization of the hardware there. Is this issue booting your custom bootloader, or the reference U-boot provided by F&amp;amp;S? As we are not supporting this hardware currently, perhaps an F&amp;amp;S engineer can assist &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/karinavalencia"&gt;karinavalencia&lt;/A&gt;?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Timesys Support&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Apr 2015 16:27:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427102#M4750</guid>
      <dc:creator>timesyssupport</dc:creator>
      <dc:date>2015-04-28T16:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427103#M4751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/rendy"&gt;rendy&lt;/A&gt; can you help here?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Apr 2015 16:29:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427103#M4751</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2015-04-28T16:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427104#M4752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;reminder&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" data-containerid="-1" data-containertype="-1" data-content-finding="Community" data-objectid="207914" data-objecttype="3" href="https://community.nxp.com/people/rendy" style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #266fc8;"&gt;rendy&lt;/A&gt;&lt;SPAN style="color: #000000; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt; can you help here?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 May 2015 21:57:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427104#M4752</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2015-05-08T21:57:01Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427105#M4753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/rendy"&gt;rendy&lt;/A&gt;​ any update?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 May 2015 17:10:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427105#M4753</guid>
      <dc:creator>karina_valencia</dc:creator>
      <dc:date>2015-05-11T17:10:10Z</dc:date>
    </item>
    <item>
      <title>Re: MAC-ENET doesn't send data in TX</title>
      <link>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427106#M4754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, have you tried to enable the internal MAC loopback to find out whether the issue is in MAC or in PHY?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Rene&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jun 2015 09:46:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Vybrid-Processors/MAC-ENET-doesn-t-send-data-in-TX/m-p/427106#M4754</guid>
      <dc:creator>rendy</dc:creator>
      <dc:date>2015-06-01T09:46:15Z</dc:date>
    </item>
  </channel>
</rss>

