nrf51822 pwm

Recently worried about how to download nRF51822 and STM32F405RGT6 in the Xubuntu system, today finally downloaded successfully, recorded the process of resolution.After entering the virtual box VM Bitcraze shared, go to the following directory:Cd/home/bitcraze/projects/crazyflie2-nrf-firmware/We will find the makefile file,#Put your personal build config in config.mk and does not COMMIT it!-include config.mkcload_script? =. /crazyflie-clients-python/b

1, Timers_init (); static void Timers_init (void ) {uint32_t err_ Code // Initialize timer module app_ Timer_init (App_timer_prescaler, App_timer_max_timers, app_timer_op_queue_size, False ); // Create timers Err_code = App_ Timer_create (m_battery_timer_id, App_timer_mode_repeat ED, battery_level_meas_timeout_handler ); App_error_check (err_code); Err_code = App_timer_start (m_battery_timer_id, battery_level_meas_interval, NULL);App_error_check (Err_code); App

128bit UUID Service Set in Nrf51822Uint32_tble_dajia_add_service (ble_dajia_t *p_wechat){uint32_t Err_code;ble_uuid_t Ble_wechat_uuid;Const BLE_UUID128_TBASE_UUID128 ={{0x23, 0xD1, 0xBC, 0xEA, 0x5f, 0x78,0x23, 0x15,0xDE, 0xEF, 0x12, 0x12, 0x00, 0x00,0x00, 0x00}};Ble_wechat_uuid.uuid =0x1122;Ble_uuid_ble_assign (Ble_wechat_uuid,ble_uuid_dajia_service),//?? UuidErr_code =sd_ble_uuid_vs_add (base_uuid128, (Ble_wechat_uuid.type));if (err_code! = nrf_success){return err_code;}Err_code =sd_ble_gatts_

values are-40, -30, -20, -16, -12,-8, -4, 0, and 4 dBm/* * @brief Set the radio ' s transmit power.** @param [in] tx_power radio transmit power in dBm (accepted values are-40, 3 0, -20, -16, -12,-8, -4, 0, and 4 dbm). * * @note -40 dbm would not actually give-40 DBm, but would instead be remapped to- dbm.** @return @ref nrf_success successfully changed the transmit power.* @return @ref Nrf_error_invalid_param INVALID Parameter (s) supplied.* @return @ref nrf_error_busy The stack is BUSY, proces

Connection events after sending a connection request. This could is caused a number of reasons. Here is a few possibilities: The RF performance on one or both devices are not good, so the slave either never receives the connection request, or the M Aster never receives any packets from the slave during the first 6 connection events. The RF performance could is bad due to a failed CRC, collision or maybe the devices is just out of range. There could is a timing issue in either device

(nus_base_uuid, p_nus->uuid_type); if (err_code! = nrf_success) {return err_code; }//Add Service Ble_uuid.type = p_nus->uuid_type; Ble_uuid.uuid = Ble_uuid_nus_service; Err_code = Sd_ble_gatts_service_add (Ble_gatts_srvc_type_primary, ble_uuid, p_nus->service_handle); if (err_code! = nrf_success) {return err_code; }...char_add:ble_uuid.type = p_nus->uuid_type; Ble_uuid.uuid = ble_uuid_nus_rx_characteristic; ... return Sd_ble_gat

BLE-NRF51822 tutorial 9-dynamic password (pairing code) NordicBLE technology exchange group 498676838This tutorial also describes how to modify the dynamic password (actually a pair code) based on the uart example in the sdk. The Uart example is in the following directory: XXX \ Keil_v5 \ ARM \ Pack \ nordicsemicondu\ nRF_Examples \ 9.0.0 \ ble_peripheral \ ble_app_uart Some theoretical knowledge about pairing is introduced in the static password tut

BLE-NRF51822 tutorial 5-static password settings NordicBLE Contact Group 498676838This lecture introduces some related theoretical knowledge about pairing and describes how to set a "static password ". The program is a uart demo Based on sdk9.0 In addition, the mobile app used for testing is lightblue in IOS. The correct statement here should be a pair code, not a password. Enter this pair code as an optional part of the pairing process. Before intr

Ug-request, current mode:thread xpsr:0xc1000000 pc:0x000006d0 Msp:0x000007c0auto erase Enabledwarn:unknown device (H WID 0x00000058) wrote 45056 bytes From File Cf2_nrf.hex in 282.951080s (0.156 kib/s) target State:haltedtarget halted due to breakpoint, current Mode:thre Ad xpsr:0x61000000 pc:0x2000002e msp:0x000007c0verified 44944 bytes in 0.579762s (75.705 kib/s) shutdown command invokedIn fact, at the end of the makefile, we can see:Factory_reset:make Mass_eraseifeq ($ ($ (strip $ (S110)),

The previous article analyzed the code of the first 10 basic experiments, starting from here to analyze the next 10 ~First, the PPI principle:PPI (Programmable peripheral interconnect), Chinese translation is a programmable peripheral interconnect.The PPI approach is set up inside nRF51822, allowing interconnection between different peripherals through tasks and events, without the need for CPU involvement.The PPI allows tasks and events to be connect