This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

displaying data through sensor

Hello, 
i'am trying to display data on my sensor Bme280 aka (temp, humidity and pression
but the build is successful and the jlink is well connected 
the wiring is like below :

P1.02->SDI

p1.03->SCK

GND->DSO

GND->GND

VDDNRF->VIN
i'm using i2c-1 to visualize data but i'm not getting nothing back from the card
i used west build and flash it was successfully done but no response from the sensor 
i'm attaching the project belowbme_280.zip
i'm getting this output which says that it's successful

can someone help me please 

Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Users/rzaafouri/ncs/v1.7.0/toolchain/segger_embedded_studio/bin/JLink_x64.dll
Firmware Version: J-Link OB-K22-NordicSemi compiled Apr 29 2021 15:10:52
DLL Version: 7.52b
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF5340_XXAA_APP" selected.
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: AHB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FE000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FE000
ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[1][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
ROMTbl[1][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BBD21 Cortex-M33
Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: ARMv8M core with Security Extension enabled detected.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘zephyr.elf’ to J-Link
Programming 35.0 KB of addresses 00000000 — 00008c5b
Programming 0.4 KB of addresses 00008c5c — 00008dfb
J-Link: Flash download: Bank 1 @ 0x00000000: 1 range affected (32768 bytes)
J-Link: Flash download: Total: 1.195s (Prepare: 0.087s, Compare: 0.037s, Erase: 0.694s, Program & Verify: 0.342s, Restore: 0.033s)
J-Link: Flash download: Program & Verify speed: 93 KiB/s
Download successful
Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Users/rzaafouri/ncs/v1.7.0/toolchain/segger_embedded_studio/bin/JLink_x64.dll
Firmware Version: J-Link OB-K22-NordicSemi compiled Apr 29 2021 15:10:52
DLL Version: 7.52b
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF5340_XXAA_APP" selected.
ConfigTargetSettings() start
ConfigTargetSettings() end
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x6BA02477
DPIDR: 0x6BA02477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: AHB-AP (IDR: Not set)
AP[2]: MEM-AP (IDR: Not set)
AP[3]: MEM-AP (IDR: Not set)
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FE000
CPUID register: 0x410FD214. Implementer code: 0x41 (ARM)
Found Cortex-M33 r0p4, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
Security extension: implemented
Secure debug: enabled
CoreSight components:
ROMTbl[0] @ E00FE000
ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table
ROMTbl[1] @ E00FF000
ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33
ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT
ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB
ROMTbl[1][3]: E0000000, CID: B105900D, PID: 000BBD21 ITM
ROMTbl[1][5]: E0041000, CID: B105900D, PID: 002BBD21 ETM
ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI
ROMTbl[0][1]: E0040000, CID: B105900D, PID: 000BBD21 Cortex-M33
Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: ARMv8M core with Security Extension enabled detected.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘zephyr.elf’ to J-Link
Programming 35.0 KB of addresses 00000000 — 00008c5b
Programming 0.4 KB of addresses 00008c5c — 00008dfb
J-Link: Flash download: Bank 1 @ 0x00000000: Skipped. Contents already match
Download successful

i will be very grateful
thank u n advance

Parents
  • Based on your earlier cases, it seems like you're using SES and looking at the log window at the bottom. SES uses RTT logging, which needs to be enabled in your application.

    I was able to get RTT log to work with your sample by adding these in prj.conf:

    CONFIG_UART_CONSOLE=n
    CONFIG_RTT_CONSOLE=y
    CONFIG_USE_SEGGER_RTT=y

    Best regards,

    Simon

Reply
  • Based on your earlier cases, it seems like you're using SES and looking at the log window at the bottom. SES uses RTT logging, which needs to be enabled in your application.

    I was able to get RTT log to work with your sample by adding these in prj.conf:

    CONFIG_UART_CONSOLE=n
    CONFIG_RTT_CONSOLE=y
    CONFIG_USE_SEGGER_RTT=y

    Best regards,

    Simon

Children
No Data
Related