• State Verified Answer
  • Replies 3 replies
  • Subscribers 69 subscribers
  • Views 1942 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 218328
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Emulator for nrf51

Burgers

Hi all,

I know this question has been asked before, but a long time ago.

Is there any emulator for the nrf51 that I could make use of? I've tried using QEMU, but I'm not able to make it run properly (I'm not sure if the nrf51 for QEMU is a work in progress). I wanted to know if since last post (last year I think), some has been able to emulate the nrf51.

Thanks!

Parents
  • 0

    We've got quite a full nRF52 emulator working in https://jumper.io

    Feel free to contact us as we can do the nRF51 too.

  • 0 in reply to Jonathan

    Greetings,
    my name is Emanuele Virgillito and I'm a computer engineering student at Politecnico di Torino. I'm developing a gdb-based c++ client to interact with jumper, but i found myself stucked in the following problem:

    even though breakpoints, run and step work, whenever i try to modify registers with my application, jumper responds "OK", but if i try to read the same register - even after a step command - the result i get is its value before the write.

    I'm using gdb rsp protocol in order to communicate to jumper and i also tried with original arm-none-eabi-gdb debugger but it behaves the same. I also tried to communicate with qemu and it works fine.
    I would be glad to hear your suggestions over this problem; you can find capture taken by wireshark on arm-none-eabi-gdb communication attached below.


    Regards
    EV
    PS. I know this isn't the right place to post this problem; I tried to reach you at [email protected] but cannot forward any mail.

    Wireshark Capture on writing register $r1 with value 0x4:

    GdbClnt: $P1=04000000#42

    Jumper: $OK#9a

    GdbClnt:$g#67

    Jumper: $0000000060080000000000207000002000000000000000000000000000000000000000000000000000000000000000000000000000000120ffffffffe6020000#09

    GdbClnt:$m2e6,4#9a

    Jumper: $9b1a03dd#58

    GdbClnt: $p19#da

    Jumper: $00000000#80

    GdbClnt:$m0,4#fd

    Jumper: $00000120#83

    Note: i also tried to perform step command in order to see if something would have changed after an istruction, but Jumper returns always $r1's value before write operation.

Reply
  • 0 in reply to Jonathan

    Greetings,
    my name is Emanuele Virgillito and I'm a computer engineering student at Politecnico di Torino. I'm developing a gdb-based c++ client to interact with jumper, but i found myself stucked in the following problem:

    even though breakpoints, run and step work, whenever i try to modify registers with my application, jumper responds "OK", but if i try to read the same register - even after a step command - the result i get is its value before the write.

    I'm using gdb rsp protocol in order to communicate to jumper and i also tried with original arm-none-eabi-gdb debugger but it behaves the same. I also tried to communicate with qemu and it works fine.
    I would be glad to hear your suggestions over this problem; you can find capture taken by wireshark on arm-none-eabi-gdb communication attached below.


    Regards
    EV
    PS. I know this isn't the right place to post this problem; I tried to reach you at [email protected] but cannot forward any mail.

    Wireshark Capture on writing register $r1 with value 0x4:

    GdbClnt: $P1=04000000#42

    Jumper: $OK#9a

    GdbClnt:$g#67

    Jumper: $0000000060080000000000207000002000000000000000000000000000000000000000000000000000000000000000000000000000000120ffffffffe6020000#09

    GdbClnt:$m2e6,4#9a

    Jumper: $9b1a03dd#58

    GdbClnt: $p19#da

    Jumper: $00000000#80

    GdbClnt:$m0,4#fd

    Jumper: $00000120#83

    Note: i also tried to perform step command in order to see if something would have changed after an istruction, but Jumper returns always $r1's value before write operation.

Children
No Data
Related