I'm trying to flash the nRF52 chip but I'm having a hard time. I'm new to all this, es

You need to install this <a href="https://developer.arm.com/-/media/Files/download

I downloaded it but I still get the same error <a class="user-mention notranslate" dat

I still get the same error <a class="user-mention notranslate" data-hovercard-type="us

Sorry I missed the latest / <div class="snippet-clipboard-content notranslate posi

jaekim24 commented on June 27, 2024 2

I think that worked, so with the new binary that's been created I use that to flash on to the compiled directory ?

from openhaystack-firmware.

acalatrava commented on June 27, 2024

You need to fetch the submodule. Go to the root directory and issue

git submodule init
git submodule update

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

that fixed it !!

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

now when I enter "make build" I get this error at the bottom about "make: arm-none-eabi-gcc: No such file or directory"

from openhaystack-firmware.

acalatrava commented on June 27, 2024

You need to install this
https://developer.arm.com/-/media/Files/downloads/gnu-rm/10-2020q4/gcc-arm-none-eabi-10-2020-q4-major-mac.pkg?revision=96309e24-064b-4aaf-81fc-9a4f2f15417e&la=en&hash=FB3A659BD38CEFCE2CF4EA78CBD95DA44ACE8AD9

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

I downloaded it but I still get the same error @acalatrava

from openhaystack-firmware.

acalatrava commented on June 27, 2024

I think you need to add it to your path. Try this ``` TOOLCHAIN_PATH=/Applications/ARM/bin make build ```

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

I still get the same error @acalatrava

from openhaystack-firmware.

acalatrava commented on June 27, 2024

Sorry I missed the latest /

TOOLCHAIN_PATH=/Applications/ARM/bin/ make build

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

new error after I typed TOOLCHAIN_PATH=/Applications/ARM/bin/ make build :

from openhaystack-firmware.

mowtschan commented on June 27, 2024

brew install binutils

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

I still get the same error even after installing binutils

from openhaystack-firmware.

mowtschan commented on June 27, 2024

@jaekim24 can you post the output of the command which objcopy ?

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

"objcopy not found" @mowtschan

from openhaystack-firmware.

acalatrava commented on June 27, 2024

What about `which gobjcopy` El El vie, 14 may 2021 a las 16:55, jaekim24 ***@***.***> escribió:

…

"objcopy not found" @mowtschan <https://github.com/mowtschan> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACA3W4LMHHPT4D52GFOW2VTTNU2WBANCNFSM443DGTYA> .

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

"gobjcopy not found"

from openhaystack-firmware.

mowtschan commented on June 27, 2024

@jaekim24 looks like it is missing in your PATH, can you run export PATH="/usr/local/opt/binutils/bin:$PATH" and try again?

p.s.: I assume that you have binutils installed on /usr/local/opt/binutils/bin

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

what's the next step I need to do to get the nrf52 chip to work w the find my network? @acalatrava

from openhaystack-firmware.

acalatrava commented on June 27, 2024

If you have a JLink you can just issue a make flash

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

what about the public advertisement key, Do I have to get that from the open haystack app?

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

im having this error where the "Target connection not established yet but required for command."

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

and It also says cannot connect to target

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

when I tried a new chip it did this:
michaelhunt@nicolaskerr openhaystack-alternative % TOOLCHAIN_PATH=/Applications/ARM/bin/ make flash
BUILD OPTIONS:
SoftDevice s132
SDK 11
nRF nrf52832
RAM 64 kB
FLASH 512 kB
Board BOARD_SIMPLE

mkdir -p _build/
printf "r\n" > _build/flash.jlink
printf "loadfile _build/openhaystack-alternative_s132.hex \nr\ng\nexit\n" >> _build/flash.jlink
mkdir -p _build/
printf "r\nsavebin _build/downloaded_test.bin 0x1000 0x10\nexit\n" > _build/test-softdevice.jlink
mkdir -p _build/
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

J-Link Command File read successfully.
Processing script file...

J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04
Hardware version: V7.00
S/N: 20090928
License(s): RDI,FlashDL,FlashBP,JFlash,GDBFull
VTref=3.300V
Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
Unknown DP version. Assuming DPv0
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.

Opening binary file for writing... [_build/downloaded_test.bin]
Reading 16 bytes from addr 0x00001000 into file...O.K.

Script processing completed.

16+0 records in
16+0 records out
16 bytes transferred in 0.000131 secs (122016 bytes/sec)
Files _build/downloaded_test.bin and _build/softdevice_test.bin differ
BUILD OPTIONS:
SoftDevice s132
SDK 11
nRF nrf52832
RAM 64 kB
FLASH 512 kB
Board BOARD_SIMPLE

Write to NVMC to enable erase, do erase all, wait for completion. reset

mkdir -p _build/
printf "w4 4001e504 2\nw4 4001e50c 1\nsleep 100\nr\nexit\n" > _build/erase-all.jlink
mkdir -p _build/
JLinkExe -device nrf52 -if swd -speed 1000 _build/erase-all.jlink
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

J-Link Command File read successfully.
Processing script file...

J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04
Hardware version: V7.00
S/N: 20090928
License(s): RDI,FlashDL,FlashBP,JFlash,GDBFull
VTref=3.300V
Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
Unknown DP version. Assuming DPv0
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
Writing 00000002 -> 4001E504

Writing 00000001 -> 4001E50C

Sleep(100)

Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.

Script processing completed.

Write to NVMC to enable write. Write mainpart, write UICR. Assumes device is erased.

mkdir -p _build/
printf "w4 4001e504 1\nloadbin "_build/s132_nrf52_2.0.0_softdevice.bin" 0\nr\ng\nexit\n" > _build/flash-softdevice.jlink
mkdir -p _build/
/Applications/ARM/bin/arm-none-eabi-objcopy -Iihex -Obinary ../../nrf5x-base/make/../sdk/nrf51_sdk_11.0.0//components/softdevice/s132/hex/s132_nrf52_2.0.0_softdevice.hex _build/s132_nrf52_2.0.0_softdevice.bin
JLinkExe -device nrf52 -if swd -speed 1000 _build/flash-softdevice.jlink
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

J-Link Command File read successfully.
Processing script file...

J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04
Hardware version: V7.00
S/N: 20090928
License(s): RDI,FlashDL,FlashBP,JFlash,GDBFull
VTref=3.300V
Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
Unknown DP version. Assuming DPv0
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
Writing 00000001 -> 4001E504

Downloading file [_build/s132_nrf52_2.0.0_softdevice.bin]...
J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (114688 bytes)
J-Link: Flash download: Total: 4.888s (Prepare: 0.902s, Compare: 0.076s, Erase: 0.000s, Program & Verify: 3.893s, Restore: 0.015s)
J-Link: Flash download: Program & Verify speed: 28 KB/s
O.K.

Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.

Script processing completed.

JLinkExe -device nrf52 -if swd -speed 1000 _build/flash.jlink
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

J-Link Command File read successfully.
Processing script file...

J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04
Hardware version: V7.00
S/N: 20090928
License(s): RDI,FlashDL,FlashBP,JFlash,GDBFull
VTref=3.300V
Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
Cannot connect to target.

Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
Cannot connect to target.

Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
Cannot connect to target.

Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
Cannot connect to target.

Script processing completed.

michaelhunt@nicolaskerr openhaystack-alternative %

from openhaystack-firmware.

jaekim24 commented on June 27, 2024

when I try flashing the new chip again this shows up and does this mean it worked? Also how do I get this chip to communicate with the openhaystack app, like do I have to add the public advertisement key somewhere:

michaelhunt@nicolaskerr openhaystack-alternative % TOOLCHAIN_PATH=/Applications/ARM/bin/ make flash
BUILD OPTIONS:
SoftDevice s132
SDK 11
nRF nrf52832
RAM 64 kB
FLASH 512 kB
Board BOARD_SIMPLE

mkdir -p _build/
printf "r\n" > _build/flash.jlink
printf "loadfile _build/openhaystack-alternative_s132.hex \nr\ng\nexit\n" >> _build/flash.jlink
mkdir -p _build/
printf "r\nsavebin _build/downloaded_test.bin 0x1000 0x10\nexit\n" > _build/test-softdevice.jlink
mkdir -p _build/
SEGGER J-Link Commander V6.88a (Compiled Nov 18 2020 15:09:53)
DLL version V6.88a, compiled Nov 18 2020 15:09:35

J-Link Command File read successfully.
Processing script file...

J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04
Hardware version: V7.00
S/N: 20090928
License(s): RDI,FlashDL,FlashBP,JFlash,GDBFull
VTref=3.300V
Target connection not established yet but required for command.
Device "NRF52" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
Unknown DP version. Assuming DPv0
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: 00000000, PID: 00000000 ???
ROMTbl[0][1]: E0001000, CID: 00000000, PID: 00000000 ???
Cortex-M4 identified.
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: SYSRESETREQ has confused core.
Failed to power up DAP
Reset: Using fallback: VECTRESET.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.VECTRESET.
Reset: VECTRESET has confused core.
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Failed to power up DAP
CPU could not be halted
Reset: Core did not halt after reset, trying to disable WDT.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Failed to power up DAP
CPU could not be halted
Reset: Failed. Toggling reset pin and trying reset strategy again.
Failed to power up DAP
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: SYSRESETREQ has confused core.
Failed to power up DAP
Reset: Using fallback: VECTRESET.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.VECTRESET.
Reset: VECTRESET has confused core.
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Failed to power up DAP
CPU could not be halted
Reset: Core did not halt after reset, trying to disable WDT.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Reset: VC_CORERESET did not halt CPU. (Debug logic also reset by reset pin?).
Reset: Reconnecting and manually halting CPU.
Failed to power up DAP
CPU could not be halted
CPU could not be halted

****** Error: Failed to halt CPU.

Opening binary file for writing... [_build/downloaded_test.bin]
Reading 16 bytes from addr 0x00001000 into file...Could not read memory.

Script processing completed.

16+0 records in
16+0 records out
16 bytes transferred in 0.000128 secs (124970 bytes/sec)
Files _build/downloaded_test.bin and _build/softdevice_test.bin differ
BUILD OPTIONS:
SoftDevice s132
SDK 11
nRF nrf52832
RAM 64 kB
FLASH 512 kB
Board BOARD_SIMPLE