 |
Electronic Components Datasheet Search |
|
|
Electronic Components Datasheet Search |
|
NORAB100 Datasheet(PDF) 10 Page - List of Unclassifed Manufacturers |
|
|
|||||||||||||||||||||||||||||
NORAB100 Datasheet(HTML) 10 Page - List of Unclassifed Manufacturers |
|
|
10 / 46 page  NORA-B1 series - Data sheet UBX-20027119 - R10 Functional description Page 10 of 46 C1 – Public 1.6 Software options 1.6.1 Open CPU The open-CPU architecture of NORA-B1 series modules allows integrators to develop and run their own applications on the built-in Arm® Cortex®-M33 cores. u-blox recommends the Nordic Semiconductor nRF Connect SDK [5] for development. The nRF Connect SDK integrates the Zephyr Real Time Operating System (RTOS), MCUboot secure bootloader, and Nordic Semiconductor’s nrfxlib device drivers for the nRF52 and nRF53 peripherals. 1.7 Bluetooth device address NORA-B1 modules are programmed from the factory with a unique, public Bluetooth device address stored in the OTP[0] and OTP[1] registers of the User Information Configuration Registers (UICR) of the application core and duplicated in the CUSTOMER[0] and CUSTOMER[1] registers of the User Information Configuration Registers (UICR) of the network core. The Bluetooth device address consists of the IEEE Organizationally Unique Identifier (OUI) combined with the hexadecimal digits that are printed within a 2D data matrix. See also Labeling and ordering information. The Bluetooth device address is stored in little-endian format. The two most significant bytes of the OTP[1] and CUSTOMER[1] registers are unused and assigned the value 0xFF to complete the 32-bit register. UICR Register in application core Address Description Remarks OTP[0] 0x00FF8100 0xAA = Bluetooth_addr [5] IEEE OUI1 OTP[0] 0x00FF8101 0xBB = Bluetooth_addr [4] IEEE OUI1 OTP[0] 0x00FF8102 0xCC = Bluetooth_addr [3] IEEE OUI1 OTP[0] 0x00FF8103 0xDD = Bluetooth_addr [2] Example - actual value printed on label OTP[1] 0x00FF8104 0xEE = Bluetooth_addr [1] Example - actual value printed on label OTP[1] 0x00FF8105 0xFF = Bluetooth_addr [0] Example - actual value printed on label OTP[1] 0x00FF8106 0xFF Unused OTP[1] 0x00FF8107 0xFF Unused Table 2: Bluetooth device address in application core UICR Register in network core Address Description Remarks CUSTOMER[0] 0x01FF8300 0xAA = Bluetooth_addr [5] IEEE OUI1 CUSTOMER[0] 0x01FF8301 0xBB = Bluetooth_addr [4] IEEE OUI1 CUSTOMER[0] 0x01FF8302 0xCC = Bluetooth_addr [3] IEEE OUI1 CUSTOMER[0] 0x01FF8303 0xDD = Bluetooth_addr [2] Example - actual value printed on label CUSTOMER[1] 0x01FF8304 0xEE = Bluetooth_addr [1] Example - actual value printed on label CUSTOMER[1] 0x01FF8305 0xFF = Bluetooth_addr [0] Example - actual value printed on label CUSTOMER[1] 0x01FF8306 0xFF Unused CUSTOMER[1] 0x01FF8307 0xFF Unused Table 3: Bluetooth device address in network core ☞ For instructions describing how to read and re-program the Bluetooth device address if the UICR of either the application or network core need erased, see the NORA-B1 system integration manual [1]. 1 Example value shown. The full Bluetooth device address is encoded in the label data matrix and stored in the UICR for each core. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |
English ▼
English
Chinese
German
Japanese
Russian
Korean
Spanish
French
Italian
Portuguese
Polish
Vietnamese
Indian
Mexican
British
New Zealand
