Member | Action | Date |
---|---|---|
|
Replied
to
Using the console on a custom hardware
Your dev radio board sounds like it is using USART 0 to implement the CLI. When you Adapter->Launce Console you are actually opening a terminal program. You can also use Tera Term or Hyperterminal as an alternative. If you where using the SWO, then you would click Adapter ->Open SWO Terminal. The best place to start is the user guide and schematic for your dev board and see how that is wired. Virtual comport and Virtual UART are different things. The Virtual UART is the SWDIO connection on the debugger as you state, and virtual COM port is the USB to USART interface on the dev board. When using the Virtual COM port, you needs to enabled this from the firmware. Which ports and pins the app uses are configured in the configurator. The bare minimum you need for a USART CLI is RX and TX if you are not using flow control
|
47 days ago |
|
Replied
to
Using CSLIB gecko suit 2.6
I should add that have managed to create the missing file. I found an old application that I'd written a couple of years ago. I don't remember, but I think I created by creating a demo that used CSEN touch. I'm just trying to see if I can find which app that was...
Show more
|
57 days ago |
|
Updated
to
Using CSLIB gecko suit 2.6
the stack is Zigbee 6.6.3.0 It this any function in hardware_routines.c. I seem to have been able to get it to compile by removing the code and there are no linker errors so it looks like it's not used. Note I have also removed CSLIB_TRST [] from hardware_config.c
The specific unresolved identifires are TRST_NOISE_THRESHOLD, TRST_DELAY, TRST_ARRAY_SIZE, CSLIB_TRST, TRST_NOISE_EST_RESET
|
57 days ago |
|
Replied
to
Using CSLIB gecko suit 2.6
It this any function in hardware_routines.c. I seem to have been able to get it to compile by removing the code and there are no linker errors so it looks like it's not used. Note I have also removed CSLIB_TRST [] from hardware_config.c
The specific unresolved identifires are TRST_NOISE_THRESHOLD, TRST_DELAY, TRST_ARRAY_SIZE, CSLIB_TRST, TRST_NOISE_EST_RESET
|
57 days ago |
|
Replied
to
.cproject and .isc files changing when generating and building project
I had a similar problem with pre and post build absolute paths making collaboration hard. I fixed it as follows Fixing the pre and post batch file launch command.Go to Project->properties->C/C++ Build->Settings->Build Steps and add the following… …to pre-build stepcmd //c '${ProjDirPath}/iTRVZ3-prebuild.bat' '${BuildArtifactFileBaseName}' '${ProjDirPath}' '${TOOLKIT_DIR}' '${eclipse_home}' …to post build steps:cmd //c '${ProjDirPath}/iTRVZ3-postbuild.bat' '${BuildArtifactFileBaseName}' '${ProjDirPath}' '${TOOLKIT_DIR}' '${eclipse_home}' However it kept changing it back on re-generation, so we ended up specifying the development path, |
58 days ago |
|
Selected an answer for
Unable to delete reports in a sleepy end device
I think I've found the answer: |
Sep 06 2019, 9:50 AM |
|
Replied
to
Unable to delete reports in a sleepy end device
I think I've found the answer: |
Sep 03 2019, 9:04 PM |
|
Replied
to
Unable to delete reports in a sleepy end device
That was something I considered, which is why I tried erasing the whole chip and re-programming.
Sorry, that wasn't that clear. On the ZED, i can delete the reports using CLI commands:-
|
Sep 03 2019, 7:22 AM |
|
Updated
Unable to delete reports in a sleepy end device on
Forum
I've created a sleepy end device and and router / coordinator using stack EmberZNet 6.6.1.0. Working through the CLI of the coordinator I've set up bindings and reports, and these appear to work
However, I now have 2 reports on the ZED that I can not delete using the CLI command plugin reporting clear or plugin reporting remove n.
They are removed when I run the plugin commands, but re-appear if I power off and on again. I've tried erasing and re-programming both the end device and the coordinator, but this doesn't fix the problem (I was thinking that maybe the simulated eeprom may have become corrupt). I am unsure how I got to this stage, but I can add and remove new reports, but I am always left with the above 2. Where am I going wrong?
|
Sep 02 2019, 6:52 PM |
|
Updated
Unable to delete reports in a sleepy end device on
Forum
I've created a sleepy end device and and router / coordinator using stack EmberZNet 6.6.1.0. Working through the CLI of the coordinator I've set up bindings and reports, and these appear to work However, I now have 2 reports on the ZED that I can not delete using the CLI command plugin reporting clear or plugin reporting remove n.
They are removed when I run the commands, but re-appear if I power of and on again. I've tried erasing and re-programming both the end device and the coordinator, but this doesn't fix the problem. I am unsure how I got to this stage, but I can add and remove new reports, but I am always left with the above 2. Where am I going wrong?
|
Sep 02 2019, 6:49 PM |