Uploading to replica Arduino Mega2560 fails - serial-communication

everyone
I could really need some help. I built an ArduinoMega2560, see schematic. I tested the PCB.
I loaded the driver for the Mega16u2 on it. I loaded the Bootloader for the atmega2560-Chip per SCK/MOSI/MISO-Pins successfully. But uploading sketches with the arduino-IDE fails with the error message "timeout". I also ran the loopback test successfully.
I guess i have some wiring problem or forgotten something important.
Maybe one of you knows this very well and can give me a hint. I do not know how to continue.
loopback test
multiple bootloader flashing and 16u2-flashing

Related

Why is my Solana wallet autoconnect React code faily?

Why does the provider from #solana/wallet-adapter-react fail to actually make my Phantom wallet to autoconnect upon launching the app? It has worked erratically in the past but I just do not see any pattern and now it just won't connect.
Edit: after some tests, I found out the problem is not code dependant. The code may or may not work depending on some unknown issue.

How to ensure bootloader is started

I am working with openmote-cc2538 for the project: https://github.com/cetic/6lbr/wiki
Here when I was trying to flash openmote with this command
sudo make TARGET=cc2538dk BOARD=openmote-CC2538 bootload0/dev/ttyUSB0 slip-radio.upload
This error message is displayed
ERROR:Cant CONNECT TO TARGET:Ensure bootloader is started(no answer on sync sequence)
cc2538 bsl.py script is available for uploading binary to openmote. But I don't have much experience about this. Can anybody give me some suggestions regarding how to proceed??
Grab a scope and probe different digital I/O pins on the CC2538. Typically a bootloader will initialize all the ports on the chip and you will see them change state, which is an indication that the bootloader is indeed running. I would guess one of the LEDs would change state as well (which doesn't require a scope).

MCP25625 doesnt send CAN messages

Im using MCP25625 which is MCP2515+integrated MCP2551 and trying to send messages in a loop.
For some reson I dont see any signal at all on CANH, CANL lines.
SPI communication works correctly
I use software reset procedure
There is clear 20Mhz sinewave from Crystal
There is TXCAN signal
At the moment there is nothing at all connected to CANL,CANH, just the probe.
I also tried to run in LOOPBACK mode and it works, but in the NORMAL modethere is nothing coming out.
Seems like transciever is broken? I changed 2 chips already, so it shouldnt be the problem.
Any suggestion guys?
Schematics
have you considered the modes of operation of the CAN transceiver?
In your schematic, the pins value is not clear.
If you have connected it to the MCU, Please pull it to LOW to select the normal operation mode for the transceiver (it is different configuration then the CAN controller settings, hence might cause some confusion!).
Controlling it by MCU is a good choice as it gives more control to prevent network communication from being blocked, due to a CAN controller which is out of control.
Else, connect it to ground to ensure normal operation mode specifically for the build in transceiver.
I have referred the data-sheet's of MCP25625, MCP2515 and TJA1050 to bring out this conclusion.
TJA1050 has pin-S for selecting high-speed mode and silent mode. Both modes are similar to normal mode and standby mode respectively of the transceiver of MCP25625.
Also, pin-S configuration in TJA1050 is similar to pin-STBY configuration in MCP25625.
0(LOW) for high-speed/normal mode of TJA1050/MCP25625-Transceiver
1(HIGH) for silent/standby mode of TJA1050/MCP25625-Transceiver
Hope this helps.
At the moment there is nothing at all connected to CANL,CANH, just the probe.
Hope you have connected the termination resistor? It is on the schematic, but ...

Memory cache is not working properly

I'm working on a uboot test application that will work with a special DMA engine. The DMA engine will transfer data between memories without "notify" cache. Therefore, I expect that if I keep transferring different data to the same destination, I should get the stale data.
However, I found that I always get the correct data the DMA engine sent. This makes me think that maybe the dcache is not enabled. So I tried the uboot build-in cmd - dcache. It shows my data cache is enabled. And I checked the TLB table and all pages are marked as "write back write allocate". So it means the cache is enabled?
And more interesting thing I found is that, I wrote a simple program that just keeps reading the same address. And I found that by disabling the dcache using the dcache cmd, the time to run the test just tripled. I tried a similar simple test in Linux on the same hardware and the cache can enable more than 15 times performance boost. So this must not be a hardware issue.
In summary, I found that my cache is working to some extent but not fully working. And it might be a configuration issue. Is there any theory can explain what I found? How can I continue to debug... Thanks
Let me answer it myself...
Code in Uboot is a little misleading... it run
set_section_dcache(i, DCACHE_WRITEBACK_WRITETHROUGH)
but after checking the MMU, it turns out that the memory type is set to be device.

JMeter crashes XP when performing JDBC request

I'm using JMeter 2.3.2 and XP SP3. When I try a JDBC request, XP crashes. This is not very convenient.
This is the first time I've used JMeter, so I'm looking for inspiration as to where to look.
Its with a fairly simple JDBC request (simple select, without parameters, aggregated report etc).
The database is SQL server, the correct jar is in the lib directory, all of the setup is correct as far as I can tell.
Does anyone have any experience of this problem?
I've found the problem, it was that the IP address of the URL wasn't correct.
I changed the IP address and now it works. There were lots of 'Cannot connect to IP address' in the logfile, and I think either Jmeter or XP was keeping theses connections around, until a buffer overflowed.
Its strange, but now that I know the answer, I can't reproduce the problem any more. Maybe it wasn't that after all. Anyway, it works now.
Sounds like Java was running out of memory and freezing your system.

Resources