- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我可以使用以下命令将编译后的代码上传到 TI cc2650:
make TARGET=srf06-cc26xx BOARD=launchpad/cc2650 savetarget
sudo make PORT=/dev/ttyACM0 BOARD=launchpad/cc2650 hello-world.upload
并能够使用以下命令在终端上查看其输出:
sudo make login PORT=/dev/ttyACM0
但是当我在进行一些编辑后尝试重新上传编译的代码时,会显示以下错误:
using saved target 'srf06-cc26xx'
CC ../../../cpu/cc26xx-cc13xx/lib/cc26xxware/startup_files/ccfg.c
CC ../../../cpu/cc26xx-cc13xx/./ieee-addr.c
AR contiki-srf06-cc26xx.a
CC ../../../cpu/cc26xx-cc13xx/./fault-handlers.c
CC ../../../cpu/cc26xx-cc13xx/lib/cc26xxware/startup_files/startup_gcc.c
CC client.c
LD client.elf
arm-none-eabi-objcopy -O binary --gap-fill 0xff client.elf client.bin
python ../../../tools/cc2538-bsl/cc2538-bsl.py -e -w -v -p /dev/ttyACM0 client.bin
Opening port /dev/ttyACM0, baud 500000
Reading data from client.bin
Cannot auto-detect firmware filetype: Assuming .bin
Connecting to target...
ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'
make: *** [client.upload] Error 1
rm client.co obj_srf06-cc26xx/fault-handlers.o obj_srf06-cc26xx/startup_gcc.o
如果我使用 SmartRF Flash Programmer
软件删除 TIcc2650 的内容,然后尝试使用上述命令从 Contiki 上传代码,则效果很好。
有人可以指导我如何直接从某些命令中删除内容,而不是使用 SmartRF Flash Programmer
软件吗?
最佳答案
您可以使用SmartRF_INSTALL_DIR/bin/srfprog
作为命令行可执行文件。您可以查看其帮助菜单
Texas Instruments SmartRF Flash Programmer 2 v1.8.0-windows
-------------------------------------------------------------------------------
The following Command Line Options are supported by the Flash Programmer
>srfprog [Target] [Actions] [File] [Address]
The order of the parameters is irrelevant.
Description of a specific option can be obtained with:
>srfprog -h [target | actions | file | address | example | help]
Only the two first letters are required: E.g.: srfprog -h ta
Help notation:
[] Square brackets are used for optional parameters.
%% Percentage mark used for symbols to be replaced.
{} Curly brackets used where one of the options are required.
| Vertical bars for choice of items.
-------------------------------------------------------------------------------
Target: {-t | --target} [soc | lsidx]
soc(%device id%[, %chip id%]) SoC Device
%device id%: Device ID of connected EB. This parameter is case sensitive.
%chip id%: Chip ID. If not given for XDS emulator devices,
probing to determine the connected SoC will be
performed and this will take longer time.
Chip ID is mandatory in combination with COM devices.
lsidx(%index%) List index
%index%: Index of connected device returned from a list command.
-------------------------------------------------------------------------------
Actions: [-ls | --list] | [-e | --erase] | [-p | --program] |
[-v | --verify] | [-r | --read] | [-w | --write] |
[-k | --keep] | [-c | --change] | [-rs | --reset] |
[-j4 | --jtag4]
{-ls | --list} [min | all | auto]
min: List connected Cebal devices(Default).
all: List all connected devices.
auto: List all connected devices and automatically try to find the chip id
for ARM based devices.
{-e | --erase} [all | p | pif | epfw | ep | forced]
all: Erase all unprotected pages(Default).
p(%pages%): Erase given pages.
pif: Erase pages in source file.
forced: Forced Mass erase. Cannot be combined with
other actions.
{-p | --program} [all | epfw | ep]
all: Program all pages in source file(Default).
epfw(%value%): Exclude pages from source file filled with given value.
ep(%pages%): Exclude given pages from source file.
{-v | --verify} [crc | rb] [pif | all | epfw | ep]
crc: Verify pages using CRC checksum(Default).
rb: Verify pages using readback and bytewise comparison.
all: Verify all pages in source file (Default).
epfw(%value%): Exclude pages from source file filled with given value.
ep(%pages%): Exclude given pages.
{-r | --read} [all | p | addr | macpri | macpri154 | macprible |
macsec | macsec154 | macsecble]
all: Read all pages(Default). Output to file.
p(%pages%): Read given pages. Output to file.
addr(0x%address%,%length%):
Read from given address with given length.
macpri: Read Primary IEEE 802.15.4 MAC Address.
macpri154: Read Primary IEEE 802.15.4 MAC Address.
macprible: Read Primary BLE MAC Address.
macsec: Read Secondary IEEE 802.15.4 MAC Address.
macsec154: Read Secondary IEEE 802.15.4 MAC Address.
macsecble: Read Secondary BLE MAC Address.
{-w | --write} {macpri | macsec | macsec154 | macsecble | ccfg | addr | p}
macpri=01.02.03.04.05.06.07.08:
Program Primary IEEE 802.15.4 MAC address.
Write of primary address only supported for CC2538 and
only if information page is not locked.
macsec=01.02.03.04.05.06.07.08 or
macsec154=01.02.03.04.05.06.07.08:
Program Secondary IEEE 802.15.4 MAC Address.
macsecble=01.02.03.04.05.06:
Program Secondary BLE MAC Address.
ccfg({wpp(%pages%) | ldbg | disbl})
Combinations of the following options are possible and must be separated
by a ','
wpp=%pages%: Program CCFG area with page lock
bits for the given pages.
ldbg: Program CCFG area with bit for
locking debug interface
disbl: Program CCFG area with bit for
disabling the bootloader interface
addr(0x%address%,%length%)=0x%value%
Fill the an address range in flash with the given value.
The value must be given as a one byte hexadecimal number
p(%pages%)=0x%value%
Fill the a page range in flash with the given value.
The value must be given as a one byte hexadecimal number
{-k | --keep} {mac | macble | mac154&macble | ccfg}
mac: Keep(or Retain) IEEE Mac address from Target device.
macble: Keep(or Retain) Ble Mac address from Target device.
mac154&macble: Keep(or Retain) IEE and Ble Mac address from Target device.
ccfg: Keep(or Retain) Complete CCFG area from Target device.
{-c | --change} {mac | mac154 | macble | efk | ldbg | wpp | disbl}
Combinations of options are possible and must be separated
by a ','
mac=01.02.03.04.05.06.07.08 or
mac154=01.02.03.04.05.06.07.08:
Change(patch) flash image with IEEE 802.15.4 MAC address.
macble=01.02.03.04.05.06:
Change(patch) flash image with BLE MAC address.
mac154=01.02.03.04.05.06.07.08 macble=01.02.03.04.05.06:
Change(patch) flash image with both addresses.
ekf(%file%, %address%):
Change(patch) flash image with Encryption Key data.
A file with the encryption key certificate and the flash
address must be given.
wpp(%pages%):
Change(patch) CCFG area in flash image with page lock
bits for the given pages.
ldbg:
Change(patch) CCFG area in flash image with bit for
locking debug interface
disbl:
Change(patch) CCFG area in flash image with bit for
disabling the bootloader interface
{-rs | --reset} [normal | none | pin | pinHib]
Pin reset is default.
Please refer to the help documentation for a detailed
description of the different reset options.
The reset action must be combined with the erase or program action.
{-j4 | --jtag4}
Use 4-pin jtag. 2-pin cJTAG is default.
{-up | --updateEmulator}
Update firmware on emulator. Option is applicable for XDS110, and cannot be
combined with other actions. Do not unplug the debug probe during the update.
-------------------------------------------------------------------------------
File: {-f | --file} %file%
%file%: Full or relative path. E.g. C:\myfolder\test.bin.
Path name with spaces must be enclosed between quote characters.
E.g. "C:\myfolder\my test.bin"
or "C:\Program files\myfolder\test.bin"
-------------------------------------------------------------------------------
Address: {-a | --address} [0x]%address%
%address%: Flash address to start programming.
-------------------------------------------------------------------------------
Examples:
>srfprog -ls
>srfprog -ls all
>srfprog -ls auto
>srfprog -t lsidx(0) -e all
>srfprog -t lsidx(0) -r macsec
>srfprog -t lsidx(0) -r all -f C:\myfolder\readback.bin
>srfprog -t lsidx(0) -r p(0-4) -f C:\myfolder\readback.bin
>srfprog -t lsidx(0) -r addr(0x200000,8)
>srfprog -t lsidx(0) -w macsec=01.02.03.04.05.06.07.08
>srfprog -t lsidx(0) -e pif -p epfw(0) -f C:\myfolder\test.bin -a 0x200000
>srfprog -t lsidx(0) -e pif -p epfw(0) -v rb -f C:\myfolder\test.bin -a 0x200000
>srfprog -t lsidx(0) -e all -p -v rb epfw(0x55) -f C:\myfolder\test.bin -a 0x200000
>srfprog -t lsidx(0) -e all -p -v rb ep(0-1) -f C:\myfolder\test.bin -a 0x200000
>srfprog -t lsidx(0) -e pif -p epfw(0) -v crc -f C:\myfolder\test.bin -a 0x200000 -k mac
>srfprog -t lsidx(0) -e pif -p epfw(0) -v crc -f C:\myfolder\test.bin -a 0x200000 -c mac=01.02.03.04.05.06.07.08 >srfprog -t lsidx(0) -e pif -p epfw(0) -v crc -f C:\myfolder\test.hex -c ekf(C:\myfolder\certificate.txt, 0x27FF6C) >srfprog -t soc(XDS-06EB12100300A,CC2538) -e -p -v -f c:\test.hex
>srfprog -t soc(COM1, CC2640) -e -p -v -f c:\test.hex
关于c - 使用命令从 Contiki 删除 cc2650 的所有内容,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/58318477/
Contiki 调度程序是抢占式的吗? Tinyos 不是;有 nanork,我不确定它的发展处于什么状态。 最佳答案 Contiki 支持抢占式线程。引用: https://github.com/c
我想使用 Contiki OS 中的广播函数来广播整数数组。然而,当给出整数数组作为输入时, packetbuf_copyfrom() 函数似乎对我不起作用。当通过 Cooja 的“ radio 消息
我正在使用 Contiki 操作系统编写程序。 我有 remote_firmware.c 文件和一个名为 parser 的文件夹,其中包含文件 parser.h 和 parser.c 我在其中编写了方
我正在尝试在 Contiki 中为 Zolertia REmote 编写一个程序,它将从传感器读取一个值,并且根据这个值以及 Remote 上的用户按钮是否被长时间按下,LED 将被打开打开、变暗或将
我试图理解 examples/cc26xx/cc26xx-ble-client-demo 中存在的 IPv6-over-BLE UDP-client 演示示例,该代码具有以下头文件: #include
嗨,我尝试将 cooja simluator 中的 mqtt mote 连接到桌面上的 mosquitto 服务器。但它一直无法连接,我能够 ping rpl 路由器,但不能 ping 我的 mqtt
我有以下问题,我的模拟结果卡在 while 循环中。在我看来,原因是我们无法在循环结束之前在mote 1.0上执行recv_uc。然而,是 mote 1.0 本身调用 unicast_send(&
我想将模拟的时间戳值作为 int 发送。更清楚地说,如果节点输出是: 00:39.841 ID:6 unicast message ready to be sent 我希望能够在消息中输入值
因为 Contiki 提供的内置列表不符合我的需求(使用太多内存),我实现了自己的列表版本,该版本已针对我打算如何使用它进行了优化。 在任何时候,这些列表中都会有一个由多个进程/原线程对其进行操作(即
在我的一个 Contiki 应用程序中,我从进程 (P) 调用某个函数 (f)。当驻留在 (f) 中的循环中至少有一个 'printf' 时,(P) 中的 'printf' 会正确显示结果。然而,当同
在我的代码中,我需要声明两个进程。在第一个过程中,我想这样调用第二个: PROCESS_THREAD(Initialization_process, ev, data) { PROCESS_
我正在开发一个需要 msp430 数学函数的应用程序。使用 powf、sqrt 等函数时,会发生内存溢出 (ROM)。一个这样的例子是,当我使用这个 float i 变量而不使用静态时,我的代码可以工
是否有可能在 contiki os 中列出所有正在运行的进程并在调试输出(即 UART)上输出结果? 最佳答案 在 contiki platform.c 和 main() 中插入: struct pr
我正在使用无线传感器网络负责人评估其在我的工作中的性能。我想测量延迟和总能耗以找到每个节点中的剩余能量。所以我的问题是我有一些 tx rx cpu cpu_idle 的值,我不知道如何使用它们来计算我
我正在 Contiki 作为我的学术工作,现在我有一个问题,我应该从 Contiki 中的示例文件夹中具体引用哪个文件来模拟场景,例如 - 具有 ipv6 节点的 30 个节点物联网,所有这些节点都将
我刚刚开始研究Contiki-OS。我对 Contiki - Antelope 感兴趣。我尝试使用 AQL(Antelope 查询语言)在串行 Cooja 模拟中创建关系、属性和插入元组。像这样: c
在不更改任何其他文件的情况下,我尝试运行 ccm-star-tests在 cooja 模拟器中的 z1 微粒上。 对于encryption节点输出为: Testing verification ...
我想将全局地址转换为链接级地址(或者即使可以进行相反的操作),我在 uip6.c 文件中有以下函数。我想将 rep (其中 rep 为我提供带有 fe80 之类的前缀的 lladdress)转换为 s
如何在recv_uc 函数中打印接收到的数据?在这种情况下是 var 的值。我使用 packetbuf_copyfrom(&var, 5) 将 var 放入发送的数据包中。 PROCESS(sendi
我想为 Contiki OS 添加一个第三方库。确切地说,我正在尝试添加 nettle 3.0 密码学库。 我是否应该使用 contiki 平台的特殊标志来构建相关库,不确定具体是什么?海合会 msp
我是一名优秀的程序员,十分优秀!