<div dir="ltr">Hi Akshay,<div><br></div><div>Somewhat related, but I have been working on EFM32 support for RIOT-OS in the past year. You can find my work (in progress) at [1]. A PR for one specific board (Thunderboard Sense) is at [2].</div><div><br></div><div>Chances are that [3] relies on the use of 'emlib'. In that case, I would strongly suggest to look at my work to not reinvent the wheel. I have implemented most peripherals (on top of emlib) for all EFM32 MCU's available (>400).</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div>Kind regards,</div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Bas Stottelaar</span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">[1] </span><a href="https://github.com/basilfx/EFM2RIOT">https://github.com/basilfx/EFM2RIOT</a></div><div><span style="font-size:12.8px">[2] <a href="https://github.com/RIOT-OS/RIOT/pull/5652">https://github.com/RIOT-OS/RIOT/pull/5652</a> </span></div><div><span style="font-size:12.8px">[3] </span><a href="https://siliconlabs.github.io">https://siliconlabs.github.io</a><wbr>/Gecko_SDK_Doc/ezr32lg/html/ez<wbr>radio__comm_8c_source.html</div><div><br></div></div></div></div></div>
<br><div class="gmail_quote">2016-12-08 10:54 GMT+01:00 Hauke Petersen <span dir="ltr"><<a href="mailto:hauke.petersen@fu-berlin.de" target="_blank">hauke.petersen@fu-berlin.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF">
    Hi Akshay,<br>
    <br>
    if I understand it correctly, you use the ezr32lg? So I would
    suggest you start by porting that CPU first:<br>
    - create the `ezr32lg` cpu<br>
    - create a `ezr32_common` folder<br>
    - move everything from the `ezr32wg` to the common folder that can
    be re-used (I would suppose this includes all periph drivers + most
    of the arch code)<br>
    <br>
    Next than you can implement the radio driver, as a rough guideline
    have a look at the (early) device driver implementation guideline
    [1]. <br>
    <br>
    Cheers,<br>
    Hauke<br>
    <br>
    [1]
<a class="gmail-m_4432958375150543784moz-txt-link-freetext" href="https://github.com/RIOT-OS/RIOT/wiki/Guide:-Writing-a-device-driver-in-RIOT" target="_blank">https://github.com/RIOT-OS/<wbr>RIOT/wiki/Guide:-Writing-a-<wbr>device-driver-in-RIOT</a><div><div class="gmail-h5"><br>
    <br>
    <br>
    <div class="gmail-m_4432958375150543784moz-cite-prefix">On 08.12.2016 10:28, Akshay Mishra
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Thanks Martine,
        <div>It is possible that there is no RF support (I thought so
          but was not sure.). I can look at porting it if there can be
          pointers.
          <div><br>
          </div>
          <div>The example used was gnrc_networking on the latest git
            clone. </div>
          <div><br>
          </div>
          <div>One confession, :-|, is that the EZR32WG is supported and
            I worked on the basic examples only modifying the WG to LG
            which changes it from Cortex-M4 to Cortex-M3. </div>
          <div class="gmail_extra"><br clear="all">
            <div>
              <div class="gmail-m_4432958375150543784m_6466643958524027547gmail_signature">
                <div dir="ltr">
                  <div>
                    <div dir="ltr">
                      <div dir="ltr">
                        <div dir="ltr">
                          <div dir="ltr">
                            <div><b style="font-size:13px;color:rgb(34,34,34);font-family:arial,sans-serif;background-color:rgb(255,255,255)"><font color="#073763">Akshay Mishra</font></b></div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
            <br>
            <div class="gmail_quote">On 8 December 2016 at 14:31,
              Martine Lenders <span dir="ltr"><<a href="mailto:mail@martine-lenders.eu" target="_blank"></a><a class="gmail-m_4432958375150543784moz-txt-link-abbreviated" href="mailto:mail@martine-lenders.eu" target="_blank">mail@martine-lenders.eu</a>></span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
                Akshay,<br>
                I fear you have to be a bit more specific than that.
                What application<br>
                are you using e.g., which network stack? Also, I might
                be mistaking<br>
                but it seems like there is no RF support for the EZR32LG
                in master<br>
                yet. Maybe that is the problem?<br>
                <br>
                Cheers,<br>
                Martine<br>
                <div>
                  <div class="gmail-m_4432958375150543784m_6466643958524027547h5"><br>
                    2016-12-08 8:34 GMT+01:00 Akshay Mishra <<a href="mailto:akshay@dspworks.in" target="_blank"></a><a class="gmail-m_4432958375150543784moz-txt-link-abbreviated" href="mailto:akshay@dspworks.in" target="_blank">akshay@dspworks.in</a>>:<br>
                    > Hello,<br>
                    >         I tried it on the SLWSTK6220a with the
                    EZR32LG. While I was able to<br>
                    > get riot-os working on it, the ipv6 address
                    does not get assigned.<br>
                    ><br>
                    > How does the interface get enabled ? I did not
                    enable any tap on the host.<br>
                    ><br>
                    > Thanks,<br>
                    > Akshay<br>
                    ><br>
                    ><br>
                  </div>
                </div>
                > ______________________________<wbr>_________________<br>
                > devel mailing list<br>
                > <a href="mailto:devel@riot-os.org" target="_blank">devel@riot-os.org</a><br>
                > <a href="https://lists.riot-os.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.riot-os.org/mail<wbr>man/listinfo/devel</a><br>
                ><br>
                ______________________________<wbr>_________________<br>
                devel mailing list<br>
                <a href="mailto:devel@riot-os.org" target="_blank">devel@riot-os.org</a><br>
                <a href="https://lists.riot-os.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.riot-os.org/mail<wbr>man/listinfo/devel</a><br>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="gmail-m_4432958375150543784mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
devel mailing list
<a class="gmail-m_4432958375150543784moz-txt-link-abbreviated" href="mailto:devel@riot-os.org" target="_blank">devel@riot-os.org</a>
<a class="gmail-m_4432958375150543784moz-txt-link-freetext" href="https://lists.riot-os.org/mailman/listinfo/devel" target="_blank">https://lists.riot-os.org/<wbr>mailman/listinfo/devel</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

<br>______________________________<wbr>_________________<br>
devel mailing list<br>
<a href="mailto:devel@riot-os.org">devel@riot-os.org</a><br>
<a href="https://lists.riot-os.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.riot-os.org/<wbr>mailman/listinfo/devel</a><br>
<br></blockquote></div><br></div></div>