1 Reply Latest reply on Sep 8, 2017 7:33 AM by Intel Corporation

    DRAM PUFS

    Indra_mary

      Good morning sir,

      Yes, still i am suffering from that issue.

      This is my Masters Project and this README has given by my professor which is upload by YALE University online.

      This is my result during rebooting the Galelio board.

       

       

      (1)

         GNU GRUB  version 0.97  (604K lower / 244540K upper memory)

       

      +-------------------------------------------------------------------------+

      | ---- No "boot/grub/grub.conf" file found on 1st USB or SD device ----   | 

      | Quark X1000 kernel-SPI initrd-SPI IMR-On IO-APIC/HPET NoEMU             |

      | Quark X1000 kernel-SPI initrd-MassStorage big-rootfs IMR-On IO-APIC/H>  |

      | Quark X1000 kernel-MassStorage initrd-MassStorage small-rootfs IMR-On>  |

      | Quark X1000 kernel-MassStorage initrd-MassStorage big-rootfs IMR-On I>  |

      | Quark X1000 kernel-MassStorage initrd-MassStorage big-rootfs IMR-On I>  |

      |                                                                         |

      |                                                                         |

      |                                                                         |

      |                                                                         |

      |                                                                         |

      |                                                                         | 

      +-------------------------------------------------------------------------+

            Use the ^ and v keys to select which entry is highlighted.

            Press enter to boot the selected OS, 'e' to edit the

            commands before booting, 'a' to modify the kernel arguments

            before booting, or 'c' for a command-line.

       

      (2) after some times (7second) the process is continue and I got this result:

       

      [   13.766839] hub 2-0:1.0: USB hub found

      [   13.771174] hub 2-0:1.0: 2 ports detected

      [   13.821451] pch_udc 0000:00:14.2: enabling device (0000 -> 0002)

      [   13.865663] g_serial: Vendor 0x8086 Product 0xbabe

      [   13.870938] g_serial gadget: Gadget Serial v2.4

      [   13.875546] g_serial gadget: g_serial ready

      [   13.926479] PPP generic driver version 2.4.2

      [   13.935576] NET: Registered protocol family 24

      [   14.037567] sdhci: Secure Digital Host Controller Interface driver

      [   14.043866] sdhci: Copyright(c) Pierre Ossman

      [   14.052456] sdhci-pci 0000:00:14.0: SDHCI controller found [8086:08a7] (rev 10)

      [   14.110220] mmc0: SDHCI controller on PCI [0000:00:14.0] using ADMA

      [   14.181452] mmc0: new high speed SDHC card at address 0001

      [   14.190997] ce4100_spi 0000:00:15.0: enabling device (0000 -> 0002)

      [   14.198988] ce4100_spi 0000:00:15.1: enabling device (0000 -> 0002)

      [   14.239438] g_serial gadget: high-speed config #1: CDC ACM config

      [   14.255559] spi_master spi0: will run message pump with realtime priority

      [   14.263959] spi_master spi1: will run message pump with realtime priority

      [   14.352040] stmmaceth 0000:00:14.6: enabling device (0000 -> 0002)

      [   14.358712] stmmac MSI mode enabled

      [   14.362323] Vendor 0x8086 Device 0x0937

      [   14.366546] stmmac - user ID: 0x10, Synopsys ID: 0x37

      [   14.371714]  DMA HW capability register supported

      [   14.376281]  Enhanced/Alternate descriptors

      [   14.380742]  RX Checksum Offload Engine supported (type 2)

      [   14.386264]  TX Checksum insertion supported

      [   14.390617]  Enable RX Mitigation via HW Watchdog Timer

      [   14.454300] libphy: stmmac: probed

      [   14.457759] eth0: PHY ID 20005c90 at 1 IRQ 0 (stmmac-1:01) active

      [   14.514038] Initializing USB Mass Storage driver...

      [   14.520206] usbcore: registered new interface driver usb-storage

      [   14.526259] USB Mass Storage support registered.

      [   14.573699] usbcore: registered new interface driver usbhid

      [   14.579318] usbhid: USB HID core driver

      Starting Bootlog daemon: bootlogd.

      kernel.hotplug = /sbin/mdev

      sh: %4Y%2m%2d%2H%2M: bad number

      INIT: Entering runlevel: 5

      Configuring network interfaces... [   16.193984] eth0: device MAC address 98:4f:ee:05:8f:bb

      udhcpc (v1.22.1) started

      Sending discover...

      Sending discover...

      Sending discover...

      No lease, failing

      Starting syslogd/klogd: done

      [   25.466107] intel_qrk_gip 0000:00:15.2: enabling device (0000 -> 0002)

      [   25.502157] intel_qrk_gpio_restrict_probe: i2c adapter not ready yet. Deferring..

      [   25.509733] platform qrk-gpio-restrict-sc.0: Driver qrk-gpio-restrict-sc requests probe deferral

      [   25.563186] intel_qrk_gpio_probe UIO addr 0x90006000 internal_addr 0xd269e000 size 4096 memtype 1

      [   25.595522] intel_qrk_gip 0000:00:15.2: i2c speed set to 400kHz

      [   25.681180] at24 0-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write

      [   25.992170] i2c /dev entries driver

      Starting galileod

      Stopping Bootlog daemon: bootlogd.

       

      iot-devkit (Intel IoT Development Kit) 1.1 quark /dev/ttyS1

       

      quark login:

       

       

      I want to know the whole process where and when will I do this:

      2.3) Connect the board using , and reboot the board, you are now using the new firmware with DRAM PUF enabled.

        e.g. By pressing ‘3’-‘1’-‘0’-‘1’, you will take one measurement of 96KB PUF initialized with all 0’s with 120s decay.

       

      Please guide me .

      What am I doing mistake and what is the solution?

       

      Thank you sir.

        • 1. Re: DRAM PUFS
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hi Indra_mary,

          If I understood you well, you are following a process to modify the Yocto image of Galileo, and the instructions (the README file) you are following were done by your professor for an academic purpose. 

          The help we can provide is limited since you are modifying the default Yocto image. Unfortunately, we only support the default Yocto image and any kind of modifications like the one you are mentioning goes beyond of our support scope.

          My recommendation would be to contact your professor since he was the one who made the README file with the instructions to enable DRAM PUF.

          Regards,
          Diego