• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 2011 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Z-stack costumization for matching a non CCxxxx platform

Nasri Yassin
Prodigy 30 points
Other Parts Discussed in Thread: Z-STACK, CC2538

Hi all,

I'm interested in creating a small scale WSN with two boards based on the ARM cortex M3 and not including the TI CCxx. it's mentioned that the TI Z-Stack can be costumised  to meet specificitions of different hardware platforms. i searched a while through net and it's seems that Z-Stack run under the Coontiki OS so i've been confused a bit about which tools are necessary to do so. does it requires only the IAR or the contiki environment also ? 

Could anyone know how can i resolve my problem and if there any tutorial or guideline, i'll be grateful to see it. 

Thanks in advance for your help !

  • 0
    Guru 31280 points

    From what I know, Z-stack is not related to Contiki. You can search for Coontiki in this forum

    and get several interesting threads.

    If you want the ARM M3 cortex + zigBee radio you may want to wait a little for CC2538

  • 0 in reply to Igor Sherer
    Prodigy 30 points

    Thx Igor for replying,

    in fact, i downloaded Z-Stack but i found out that it's implementation include two major layers : HAL (Hardware Abstraction layer) and OSAL (Operating system abstraction layer).  the first serves to the hardware description and so if, Contiki is not related to Z-Stack, what do that OSAL stand for ? even declarations and voids seems related to an OS ! 

    Have you an idea about this layer, 'cause i have to do just a light application not a very advanced one, but in the 4 weeks that last in my summer training !? 

  • 0 in reply to Nasri Yassin
    Guru 31280 points

    HAL - is the interface between the actual IC hardware and modules that uses this hardware,

    so HAL is different for every device, however HAL API doesn't change with different IC.

    OSAL - as you mention it, OSAL is Operating System Abstraction Layer, you can read the OSAL API for a bit more info.

    OSAL is a tiny non preemptive like OS.

    Z-stack is built around this OS (simplicitTI and BLE stacks use the same OSAL services)

    Contiki is also an embedded OS (as I understand it), however it's not related to Z-stack.

    I think that Contiky OS offers much more services than the Z-stack OSAL (I'm not sure coz

    I haven't investigated the Conticky OS, it was used for something called 6LowPAN i think).

    Of course you can try to adopt OSAL for another IC (non TI), however I think there are too

    many models to work with and it may take you longer than 4 weeks to do it.

    Just out of curiosity, what HW you have? You know, there are several other options you can use.

  • 0 in reply to Igor Sherer
    Prodigy 30 points

    Hi,

    So if i understood you, OSAL is just a layer in the stack architecture and the implementation of Z-Stack dosen't require the Contiki OS environment? (that will be a pretty good news for tonight !! )

    Concerning my HW platform, I'm working on the new ADI product : "ADUCRF101 eval board" and as there's not a ready stack for this platform and it will take time to ADI to develop their own stack, i'm trying to adapt an existing one. if  you have any suggestions, i'll appreciate that !

    Best Regards 

    Yassin

  • 0 in reply to Nasri Yassin
    Guru 31280 points

    Nasri Yassin said:
    So if i understood you, OSAL is just a layer in the stack architecture and the implementation of Z-Stack dosen't require the Contiki OS environment? (that will be a pretty good news for tonight !! )

    You are correct

    Nasri Yassin said:
    Concerning my HW platform, I'm working on the new ADI product : "ADUCRF101 eval board" and as there's not a ready stack for this platform and it will take time to ADI to develop their own stack, i'm trying to adapt an existing one. if  you have any suggestions, i'll appreciate that !

    Have no Idea, but I think choosing Contiky is the right way.