• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Firmware vs Software Revision Strings in BLE?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Firmware vs Software Revision Strings in BLE?


  • Subject: Re: Firmware vs Software Revision Strings in BLE?
  • From: Rick Mann <email@hidden>
  • Date: Wed, 10 Jul 2013 15:18:03 -0700

Thanks. I read that, but it's pretty wide-open to interpretation. We ended up settling on our own demarcation between software and firmware, but it's a silly distinction; there are multiple smaller processors on the peripheral that have their own code, and then there's the main host processor that runs linux (that one's pretty clearly "software"), but which one of the little processors' versions do we choose for "firmware?"

Anyway, I've decided it's not that critical.

On Jul 10, 2013, at 15:04 , Etan Kissling <email@hidden> wrote:

> Rick,
>
> see the description of the "Device Information Service" for the "Firmware" and "Software Revision String" values:
>
> http://developer.bluetooth.org/TechnologyOverview/Pages/DIS.aspx
>
> 	• Firmware Revision String - shall represent the firmware revision for the firmware within the device.
> 	• Software Revision String - shall represent the software revision for the software within the device.
>
> Etan
>
>
> On 10.07.2013, at 00:28, Rick Mann <email@hidden> wrote:
>
>> I'm using a BLE112 module within our peripheral. There are two mandatory fields, firmware revision and software revision. What is the intent of these fields? For example, is firmware the version of the software running on the BLE112 module, and software the version of the software running on our peripheral? It seems this is not appropriate (as it highlights the distinction between our peripheral and the BLE112 module within it).
>>
>> Thanks,
>>
>> --
>> Rick
>>
>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Bluetooth-dev mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Bluetooth-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden


--
Rick




 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Firmware vs Software Revision Strings in BLE?
      • From: Etan Kissling <email@hidden>
References: 
 >Firmware vs Software Revision Strings in BLE? (From: Rick Mann <email@hidden>)
 >Re: Firmware vs Software Revision Strings in BLE? (From: Etan Kissling <email@hidden>)

  • Prev by Date: Re: Firmware vs Software Revision Strings in BLE?
  • Next by Date: Re: Firmware vs Software Revision Strings in BLE?
  • Previous by thread: Re: Firmware vs Software Revision Strings in BLE?
  • Next by thread: Re: Firmware vs Software Revision Strings in BLE?
  • Index(es):
    • Date
    • Thread