home.social

#openocd — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openocd, aggregated by home.social.

  1. First foray into OpenOCD has not gone well. 😅 I seem to be able to communicate with the SAMD21, but I can't flash the bootloader. First issue seems to be "no flash bank found for address 0x00040000". Now I just have to figure out what the f✖✖k that means.

    #diy #maker #openocd #pcb #pcbdesign

  2. First foray into OpenOCD has not gone well. 😅 I seem to be able to communicate with the SAMD21, but I can't flash the bootloader. First issue seems to be "no flash bank found for address 0x00040000". Now I just have to figure out what the f✖✖k that means.

    #diy #maker #openocd #pcb #pcbdesign

  3. First foray into OpenOCD has not gone well. 😅 I seem to be able to communicate with the SAMD21, but I can't flash the bootloader. First issue seems to be "no flash bank found for address 0x00040000". Now I just have to figure out what the f✖✖k that means.

    #diy #maker #openocd #pcb #pcbdesign

  4. First foray into OpenOCD has not gone well. 😅 I seem to be able to communicate with the SAMD21, but I can't flash the bootloader. First issue seems to be "no flash bank found for address 0x00040000". Now I just have to figure out what the f✖✖k that means.

    #diy #maker #openocd #pcb #pcbdesign

  5. First foray into OpenOCD has not gone well. 😅 I seem to be able to communicate with the SAMD21, but I can't flash the bootloader. First issue seems to be "no flash bank found for address 0x00040000". Now I just have to figure out what the f✖✖k that means.

    #diy #maker #openocd #pcb #pcbdesign

  6. Heureca! I finally got around to compile my first true Baremetal program for #arm .
    From a previous project, I had enough parts and PCB to quickly assemble a SAMD21G15 based test circuit.

    I finally fully understood, how linkers work too and how my bootup sequence first has to load the .data segment from flash into sram and zero out the .bss section.

    codeberg.org/dj-bauer/baremeta

    #electronics #openocd

  7. Heureca! I finally got around to compile my first true Baremetal program for #arm .
    From a previous project, I had enough parts and PCB to quickly assemble a SAMD21G15 based test circuit.

    I finally fully understood, how linkers work too and how my bootup sequence first has to load the .data segment from flash into sram and zero out the .bss section.

    codeberg.org/dj-bauer/baremeta

    #electronics #openocd

  8. Обзор инструментов отладки встроенного ПО

    Обзор инструментов отладки встроенного ПО: программаторы (JLink, STLink, CMSIS-DAP, BlackMagic), GDB-клиенты и серверы, формат ELF/DWARF. Разбирается цепочка взаимодействия между IDE, GDB, OpenOCD и физическим программатором — от общих принципов до конкретных решений.

    habr.com/ru/articles/1006064/

    #BlackMagic_Probe #GDB #OpenOCD #JLink #STLink #CMSISDAP #armnoneeabigdb #ELF #встроенное_ПО

  9. Обзор инструментов отладки встроенного ПО

    Обзор инструментов отладки встроенного ПО: программаторы (JLink, STLink, CMSIS-DAP, BlackMagic), GDB-клиенты и серверы, формат ELF/DWARF. Разбирается цепочка взаимодействия между IDE, GDB, OpenOCD и физическим программатором — от общих принципов до конкретных решений.

    habr.com/ru/articles/1006064/

    #BlackMagic_Probe #GDB #OpenOCD #JLink #STLink #CMSISDAP #armnoneeabigdb #ELF #встроенное_ПО

  10. Обзор инструментов отладки встроенного ПО

    Обзор инструментов отладки встроенного ПО: программаторы (JLink, STLink, CMSIS-DAP, BlackMagic), GDB-клиенты и серверы, формат ELF/DWARF. Разбирается цепочка взаимодействия между IDE, GDB, OpenOCD и физическим программатором — от общих принципов до конкретных решений.

    habr.com/ru/articles/1006064/

    #BlackMagic_Probe #GDB #OpenOCD #JLink #STLink #CMSISDAP #armnoneeabigdb #ELF #встроенное_ПО

  11. Обзор инструментов отладки встроенного ПО

    Обзор инструментов отладки встроенного ПО: программаторы (JLink, STLink, CMSIS-DAP, BlackMagic), GDB-клиенты и серверы, формат ELF/DWARF. Разбирается цепочка взаимодействия между IDE, GDB, OpenOCD и физическим программатором — от общих принципов до конкретных решений.

    habr.com/ru/articles/1006064/

    #BlackMagic_Probe #GDB #OpenOCD #JLink #STLink #CMSISDAP #armnoneeabigdb #ELF #встроенное_ПО

  12. We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):

    We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.

    We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.

    Let me know if you're interested!

    EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).

    We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.

    EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!

    EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!

    #GetFediHired

  13. We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):

    We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.

    We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.

    Let me know if you're interested!

    EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).

    We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.

    EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!

    EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!

    #GetFediHired

  14. We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):

    We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.

    We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.

    Let me know if you're interested!

    EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).

    We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.

    EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!

    EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!

    #GetFediHired

  15. We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):

    We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.

    We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.

    Let me know if you're interested!

    EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).

    We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.

    EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!

    EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!

    #GetFediHired

  16. We (SCI Semiconductor) are about to hire some folks in the next couple of months (probably starting in January, since we're about to hit Christmas):

    We're aiming to hire 1-3 FAEs, who can build out the open-source bits of the #CHERIoT software stack (including drivers / various communication stacks), build demos, and work with customers on use-case bringup.

    We also want to hire someone else on the toolchain side. Primarily #LLDB + #OpenOCD, but also working with our #LLVM (and #RustC) folks.

    Let me know if you're interested!

    EDIT: We are a full-remote company. It's easiest for us to hire people in the UK (and one of our investors would really like us to hire more people in Sheffield), but elsewhere is possible (though might, for tax purposes, require you to be officially a contractor for a while).

    We're also going to be hiring people for our hardware verification and RTL teams soon (more on the verification side than design at the moment, I think). I'm not responsible for them, but I can find out more details if anyone is interested. Our first CHERIoT chip is nearly finished, we're starting to work on the second.

    EDIT 2: Thanks to all of the people who have expressed interest (in public and private posts). I'll try to get back to you all next week!

    EDIT 3: I hope I've replied to everyone now! If I missed you (there were more replies than I expected!) please let me know. I think we'll aim to do another hiring round over the summer next year, so if the current timeline doesn't work out for you, please still let me know and I'll keep you in mind next time!

    #GetFediHired

  17. nRF52833 + nRF5 SDK +
    VSCode + OpenOCD + DAPLink(IN11)
    조합으로 세팅하는 방법

    #IN11 #DAPLink
    #OpenOCD

    chatgpt.com/s/t_68c287e92fa481

  18. nRF52833 + nRF5 SDK +
    VSCode + OpenOCD + DAPLink(IN11)
    조합으로 세팅하는 방법

    #IN11 #DAPLink
    #OpenOCD

    chatgpt.com/s/t_68c287e92fa481

  19. Grr. ok with openocd I can probe the NAND over jtag, and see the info....

    > nand probe 0
    NAND flash device 'NAND 256MiB 3.3V 8-bit (Hynix)' found

    > nand info 0 0 1
    #0: NAND 256MiB 3.3V 8-bit (Hynix) pagesize: 2048, buswidth: 8, erasesize: 131072
    #0: 0x00000000 (128kB) erase state unknown (block condition unknown)
    #1: 0x00020000 (128kB) erase state unknown (block condition unknown)

    but I can't read/dump. ☹️
    > nand dump 0 test.dump 0x20000 0x800
    reading NAND flash page failed

    Not sure what could be wrong/need changing. 😡 This is driving me mad, although I'm not an openocd expert to know why the info would work but read not.

    #openocd #debugging #hacking #jtag

  20. Grr. ok with openocd I can probe the NAND over jtag, and see the info....

    > nand probe 0
    NAND flash device 'NAND 256MiB 3.3V 8-bit (Hynix)' found

    > nand info 0 0 1
    #0: NAND 256MiB 3.3V 8-bit (Hynix) pagesize: 2048, buswidth: 8, erasesize: 131072
    #0: 0x00000000 (128kB) erase state unknown (block condition unknown)
    #1: 0x00020000 (128kB) erase state unknown (block condition unknown)

    but I can't read/dump. ☹️
    > nand dump 0 test.dump 0x20000 0x800
    reading NAND flash page failed

    Not sure what could be wrong/need changing. 😡 This is driving me mad, although I'm not an openocd expert to know why the info would work but read not.

    #openocd #debugging #hacking #jtag

  21. Grr. ok with openocd I can probe the NAND over jtag, and see the info....

    > nand probe 0
    NAND flash device 'NAND 256MiB 3.3V 8-bit (Hynix)' found

    > nand info 0 0 1
    #0: NAND 256MiB 3.3V 8-bit (Hynix) pagesize: 2048, buswidth: 8, erasesize: 131072
    #0: 0x00000000 (128kB) erase state unknown (block condition unknown)
    #1: 0x00020000 (128kB) erase state unknown (block condition unknown)

    but I can't read/dump. ☹️
    > nand dump 0 test.dump 0x20000 0x800
    reading NAND flash page failed

    Not sure what could be wrong/need changing. 😡 This is driving me mad, although I'm not an openocd expert to know why the info would work but read not.

    #openocd #debugging #hacking #jtag

  22. Grr. ok with openocd I can probe the NAND over jtag, and see the info....

    > nand probe 0
    NAND flash device 'NAND 256MiB 3.3V 8-bit (Hynix)' found

    > nand info 0 0 1
    #0: NAND 256MiB 3.3V 8-bit (Hynix) pagesize: 2048, buswidth: 8, erasesize: 131072
    #0: 0x00000000 (128kB) erase state unknown (block condition unknown)
    #1: 0x00020000 (128kB) erase state unknown (block condition unknown)

    but I can't read/dump. ☹️
    > nand dump 0 test.dump 0x20000 0x800
    reading NAND flash page failed

    Not sure what could be wrong/need changing. 😡 This is driving me mad, although I'm not an openocd expert to know why the info would work but read not.

    #openocd #debugging #hacking #jtag

  23. Grr. ok with openocd I can probe the NAND over jtag, and see the info....

    > nand probe 0
    NAND flash device 'NAND 256MiB 3.3V 8-bit (Hynix)' found

    > nand info 0 0 1
    #0: NAND 256MiB 3.3V 8-bit (Hynix) pagesize: 2048, buswidth: 8, erasesize: 131072
    #0: 0x00000000 (128kB) erase state unknown (block condition unknown)
    #1: 0x00020000 (128kB) erase state unknown (block condition unknown)

    but I can't read/dump. ☹️
    > nand dump 0 test.dump 0x20000 0x800
    reading NAND flash page failed

    Not sure what could be wrong/need changing. 😡 This is driving me mad, although I'm not an openocd expert to know why the info would work but read not.

    #openocd #debugging #hacking #jtag

  24. Прошивка К1921ВГ015 без IDE и JTAG программатора

    Итак, передо мной лежала полностью собранная плата и время стремилось к вечеру. Руки чесались хотя бы помигать светодиодом, а руководство было вскользь прочитано уже несколько раз, но тут меня осенило - у меня нет подходящего программатора!

    habr.com/ru/articles/933670/

    #к1921вг015 #нииэт #jtag #bluepill #stm32f103 #openocd

  25. Прошивка К1921ВГ015 без IDE и JTAG программатора

    Итак, передо мной лежала полностью собранная плата и время стремилось к вечеру. Руки чесались хотя бы помигать светодиодом, а руководство было вскользь прочитано уже несколько раз, но тут меня осенило - у меня нет подходящего программатора!

    habr.com/ru/articles/933670/

    #к1921вг015 #нииэт #jtag #bluepill #stm32f103 #openocd

  26. Прошивка К1921ВГ015 без IDE и JTAG программатора

    Итак, передо мной лежала полностью собранная плата и время стремилось к вечеру. Руки чесались хотя бы помигать светодиодом, а руководство было вскользь прочитано уже несколько раз, но тут меня осенило - у меня нет подходящего программатора!

    habr.com/ru/articles/933670/

    #к1921вг015 #нииэт #jtag #bluepill #stm32f103 #openocd

  27. Прошивка К1921ВГ015 без IDE и JTAG программатора

    Итак, передо мной лежала полностью собранная плата и время стремилось к вечеру. Руки чесались хотя бы помигать светодиодом, а руководство было вскользь прочитано уже несколько раз, но тут меня осенило - у меня нет подходящего программатора!

    habr.com/ru/articles/933670/

    #к1921вг015 #нииэт #jtag #bluepill #stm32f103 #openocd

  28. And there we have it! Pins connected to a #BusPirate, #openocd, and contact! Direct memory access. 👌 bootloader from the capsure dumped.
    #hacking

  29. And there we have it! Pins connected to a #BusPirate, #openocd, and contact! Direct memory access. 👌 bootloader from the capsure dumped.
    #hacking

  30. And there we have it! Pins connected to a #BusPirate, #openocd, and contact! Direct memory access. 👌 bootloader from the capsure dumped.
    #hacking

  31. And there we have it! Pins connected to a #BusPirate, #openocd, and contact! Direct memory access. 👌 bootloader from the capsure dumped.
    #hacking

  32. And there we have it! Pins connected to a #BusPirate, #openocd, and contact! Direct memory access. 👌 bootloader from the capsure dumped.
    #hacking

  33. Настройка ToolChain-а Cборки Прошивок для MIK32 (MIK32 + C+ GCC + GNU Make + OpenOCD)

    В этом тексте я написал про то, как настроить рабочее окружение для разработки для российского микроконтроллера MIK32 ( K1948BK018 ).

    habr.com/ru/articles/854050/

    #MIK32 #K1948BK018 #STARTMIK32V1 #CH552T #АМУР #mikron #openocd #RV32IMC #SCR1 #eclipse

  34. Настройка ToolChain-а Cборки Прошивок для MIK32 (MIK32 + C+ GCC + GNU Make + OpenOCD)

    В этом тексте я написал про то, как настроить рабочее окружение для разработки для российского микроконтроллера MIK32 ( K1948BK018 ).

    habr.com/ru/articles/854050/

    #MIK32 #K1948BK018 #STARTMIK32V1 #CH552T #АМУР #mikron #openocd #RV32IMC #SCR1 #eclipse

  35. Настройка ToolChain-а Cборки Прошивок для MIK32 (MIK32 + C+ GCC + GNU Make + OpenOCD)

    В этом тексте я написал про то, как настроить рабочее окружение для разработки для российского микроконтроллера MIK32 ( K1948BK018 ).

    habr.com/ru/articles/854050/

    #MIK32 #K1948BK018 #STARTMIK32V1 #CH552T #АМУР #mikron #openocd #RV32IMC #SCR1 #eclipse