Actions
Forum Thread Details
  • Replies 18 replies
  • Subscribers 412 subscribers
  • Views 1021 views
  • Users 0 members are here
Related

Anyone Have stability issues with Arduino Uno Q?

SensoredHacker0

So im at my PC typing away. The Uno Q ran my code on the first try on the first day i got it, a couple days ago.
made some more tests, for 2 days everything was working great. Then, without warning, did not move it, or touch it, it stopped.
ok fine I guess. Then I tried to upload new test code. it compiles, and claims to have been uploaded. but the code doesnt work. 


The hardware which was attached, when it failed:
a Max33041E shield, and the Ethernet R3 shield. these had been working for a couple days straight. 

Not like the code is buggy, but like it doesn't even init the serial print lines. 
bash my head on the wall for a while. 
Press Reset. nothing. Un plug it, wait, re insert usb power.
$dmesg shows it, loading without issue.  

Pull the shields off, load blink. same thing, it compiles, and claims to upload, but the code never runs. 

I haven't reinstalled the boot-loader, by the time I thought to try that, I'd already gone to bed. 
But I've never had such random problems before. Ive got arduino running in projects that have run for 6 years straight not problem.

besides reloading the bootloader and one have some ideas?


Are there stability issues with the Arduino Uno Q I should know about?

Perhaps the most frustrating thing was that the LED matrix was making little hearts and arduino logos the whole time. 
meanwhile blink wont run. 

Parents

  • The Q can't really be expected to be compared reliability/stability wise with previous Arduinos.  With the new hybird MPU/MCU structure it is going to have a lot more issues than the MCU only boards.  I have found that I encountered different sets of issues depending on the hardware and software configuration and development environment.  You really haven't indicated how you are set up (PC USB host, headless, standalone), how you are powered, and what your development setup is. 

    Based on your description, I assume that you are using AppLab running on a USB host.  How are you determining that it doesn't reach the serial print lines (that would be Monitor rather than Serial in AppLab)?  Your Linux side appears to be running (assume you checked dmesg via ssh).  If you are in AppLab I would guess that the RouterBridge is failing and may be hanging the MCU.  The AppLab Blink example no longer runs only on the MCU.

    I would recommend that you connect a USB to UART adapter (3.3V) between your PC and the MCU.  You could also try one (1.8V) between the PC and the MPU.  That would help with debug.

  • in reply to ralphjy

    I'm glad you guys are investigating the Q and working through the issues. It will help everyone.

    However, got to strongly disagree with this:

    The Q can't really be expected to be compared reliability/stability wise with previous Arduinos.  With the new hybird MPU/MCU structure it is going to have a lot more issues than the MCU only boards.

    That may be the current reality with Q, but is in no way normal. I believe it means that the Arduino people have either (a) treated their creation like a Linux server or desktop PC device, or (b) is simply buggy in their implementation. Either way it's a showstopper as far as I can see.  It's frustrating, I would love to use the Q but not if it cannot be power-cycled with confidence.

    This is not the first device containing a microprocessor and microcontroller, and it needs to start up consistently every single time. I'd be especially concerned if the cause is (a) because then that means there's a complete misunderstanding by them about how people use any typical SBC or any Arduino board for that matter.

  • in reply to shabaz

    I agree with your comments, but just to clarify what I meant - the Q has much more complexity and many more points of failure, both in hardware and software.  I do think the current implementation is faulty and hopefully that will be fixed in time.   

    You're smart to wait for things to settle down, I expect many of the issues to be resolved in the next couple of quarters.  And the media interface should be available soon.

Reply
  • in reply to shabaz

    I agree with your comments, but just to clarify what I meant - the Q has much more complexity and many more points of failure, both in hardware and software.  I do think the current implementation is faulty and hopefully that will be fixed in time.   

    You're smart to wait for things to settle down, I expect many of the issues to be resolved in the next couple of quarters.  And the media interface should be available soon.

Children
No Data