I'm new at zynq board. I am trying to work with XADC of zynq-xc7z020 and want to see its quality for my application through vivado and xilinx SDK.
I tested two ways of designing through lab3 and lab4 tutorials. Synthesis, implementation and generating bitstream are OK in vivado. in the Xilinx SDK, after programming of the board, when I run a simple printf through system debugger or GDB but I get "AHB AP transaction Error". I googled it a lot and spent few days for it, but didn't get any solution. Additional, I tried to connect to the arm core of the board through XMD console by "connect arm hw" command. but console get JTAG connection error, while JTAG cable is connected and programming of the board is done.
suggested solutions of here didn't help.
thank you.
I understand what my mistake was.
Through XSCT console in SDK, I run mrd command to access DDR and read its address. but I couldn't. So I got that the problem was from DDR configurations.
I create a new project and at the first step of designing, after adding ZYNQ7 Processing System to block design, click on 'run block automation' and continue all previous steps and it worked. The point was that automation run. It sets some auto configuration of block that have to be set; and my mistake was this, that I connected DDR port manually.
Related
For all of these scenarios, I am able to upload the firmware and monitor via serial usb. But after creating my first firmware, for all new firmware, I can't upload Lua scripts using the nodemcu-tool without getting the following:
Error Message
F:\Development\NodeMCU\helloworld>nodemcu-tool -p COM3 upload init.lua
[NodeMCU-Tool]~ Unable to establish connection
[NodeMCU-Tool]~ Invalid node.chipid() Response: 6935962
Observations
Can reset the board using nodemcu-tool. Leads me to assume the baud rate is fine.
Can see the file system being created from PuTTy after loading any of the firmware. Leads me to assume the firmware is OK.
Have tried multiple dev boards, same results
Found the source of the error message device-info.js. either line 45 or 49
I have no idea what "Response: 6935962" means. Is that my chip id or an error code?
A new commit was made to the firmware source during the last couple of days. No idea if this is relevant.
Was hoping to get this resolved before I go down the Docker rabbit hole. Lazy. I know.
9/6/2019 - created first firmware to start development
Built a firmware using https://nodemcu-build.com/ with these modules (cron, file, gpio, i2c, mdns, mqtt, net, node, sjson, tmr, uart, wifi)
Uploaded the firmare using NodeMCU-PyFlasher-4.0
No issues with this firmware. I've been able to upload lua scripts and test them successfully. Even now, I can revert back to this firmware and use it without issues. I've even redownloaded this firmware from the original link, and it works fine.
9/7/2019 - created a new firmware to use adc and other goodies
Built a firmware using https://nodemcu-build.com/ with these modules (adc, cron, file, gpio, i2c, mdns, mqtt, net, node, rtctime, sjson, tmr, uart, wifi)
Uploaded the firmare using NodeMCU-PyFlasher-4.0
Having the problem described above.
9/8/2019 - built firmware with minimal modules
Built a firmware using https://nodemcu-build.com/ with these modules (file, gpio, net, node, tmr, uart, wifi)
Uploaded the firmare using NodeMCU-PyFlasher-4.0
Having the problem described above.
Platform & Tools
Windows 10
Development board: HiLetgo ESP8266 NodeMCU LUA CP2102 ESP-12E Internet WiFi Development Board Open Source Serial Wireless Module
Firmware builder: https://nodemcu-build.com/
Serial Monitor: PuTTy 0.72
Firmware Loader: NodeMCUPyFlasher 4.0
Lua script loader: nodemcu-tool 3.0.2
fetchDeviceInfo() first calls node.info() at https://github.com/AndiDittrich/NodeMCU-Tool/blob/master/lib/connector/device-info.js#L9. Then it does an if-else to figure out whether it's running on ESP8266 or ESP32.
With the recent upgrade to SDK 3.0 node.info() was changed in PR #2830. See documentation at https://nodemcu.readthedocs.io/en/latest/modules/node/#nodeinfo. It now returns values the script doesn't consider to be coming from ESP8266. The script then calls node.chipId() in the else branch. So, it's getting a chip id from ESP8266 but it is expecting one from ESP32. Hence, the exception.
I have no idea what "Response: 6935962" means. Is that my chip id or an error code?
It's your chip id.
To cut a long story short: NodeMCU-Tool needs to be adjusted as laid out above to work with the current NodeMCU version.
I cached the same issue from the recent cloud build(https://nodemcu-build.com/). It works when i switch back to the old ones. It looks like a problem of the build system or recent source code. You can switch to other build method and try use the older code.
Background: We are looking to release a commercial product based on the Android Things OS and Pi 3 hardware. The OS seems to become corrupt over time. Usually after several weeks of continuous testing. By corrupt, the Android screen will no longer appear on startup and putting SD into new hardware does not remedy. We are using an application Factory Image base on the 0.5.1-devpreview created in the Console.
My question: Is there a way to debug or monitor what caused this state in the OS? Direct serial connection?
try to clean the sd card with the diskpart command and start again from scratch.
And to debug, maybe a USB to TTL cable may help. As explained here.
Regards!
My goal is to create a simple LED controlled by my iPhone through Homekit.
I'd like to do it using only a NodeMCU (ESP8266).
I found lots of solutions using a NodeJS library (HAP-NodeJS), which works well on my PC, but obviously can't run on a NodeMCU board.
As I understand, all these solutions require a RaspberryPI (or similar board running Linux) that talks with the NodeMCU board. But I don't like this solution.
Is there a way to achieve this goal only with a NodeMCU board?
Update 1 (25/01/2017)
Ok, I'm reading lots of blogs and watching some videos, and I'm understanding more about this topic.
I found NodeMCU Flasher to install the firmware on the board, and I found the firmware I'd like to use (I think I could be more comfortable with Lua).
First problem... I'm using a Mac, and NodeMCU Flasher is for Windows... Is there an alternative?
I downloaded also ESPlorer. Does it provide the same functionality as NodeMCU Flasher?
Please check this.
Public Apple's HomeKit protocol code has been around for some time for more potent processors (notably HAP-NodeJS). This is a rewrite for the ESP8266 to make the server foundation. This project uses ESP8266_RTOS_SDK and WolfCrypt 3.9.8 for the crypto. It will however NOT deliver a certified HomeKit device.
I try example from ST for baseboard STM32F4DIS_BB + STM32F4-discovery.
I want to use RTOS example httpserver_socket. Before I use standalone (NO RTOS) httpserver example without problems. But in RTOS example the server was freeze on every web connection. It means that task are OK for LED toggle,DHCP is OK etc. Ping from CMD is OK. But when I make connection from web client the board was freezed and go to HardFault_Handler().
Any opinion?
Have you tried debugging the hard fault to see which instruction caused it? Once you know that you will be able to place a break point in the code to see how you got there.
As an aside, we have FreeRTOS+TCP running on an STM32F4 now, but on the larger eval board, rather than the Discovery board.
thanks to Richard. I found by debug and CFSR register that problem is in mem management :
"processor attempted an instruction fetch from a location that does
not permit execution. This fault occurs on any access to an XN region,
even when the MPU is disabled or not present"
But I dont understand how can ST make example for the same hardware what I have with this error? Now I try to find a problem.
I found that problem is in FPU option in project setting. Original project has set use FPU .When I set not used then project are OK. Problem in use of FPU and freeRTOS .
I got the SainSmart Mega2560 LCD Keypad Shield Sarter Kit and want to upload the demo program for this LCD keypad. The IDE runs under Win7 x64 and the driver is correctly installed, I think.
I only get error messages
avrdude: stk500v2_ReceiveMessage(): timeout
avrdude: stk500v2_getsync(): timeout communicating with programmer
avrdude: stk500v2_command(): failed miserably to execute command 0x10
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
How can I check, if the connection really exists? Are there any know issues?
It seems, that many users have the same problem. My solution was now, that I removed the LCD Panel and the upload worked.
It is very strange problem, I encountered this problem when I attempted to connect IO expansion shield with Arduino 2560. I have tried many things but it didn't work. After many attempts I removed IO expansion shield from Arduino and then upload, It was worked. There is no clue why it can't upload when IO expansion shield is plugged. So this is a workaround solution but it is working. It is enough for me now.
--- FIXED ---
The problem has been fixed by checking all wiring on RS-485 network. GND and Termination wiring was missing after set these wiring properly the problem was fixed automatically. If you have this problem, I suggest that checking wiring once again.