Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flasher and passthrough cycle w/ SREG message #2

Open
beckdac opened this issue Apr 2, 2014 · 1 comment
Open

flasher and passthrough cycle w/ SREG message #2

beckdac opened this issue Apr 2, 2014 · 1 comment

Comments

@beckdac
Copy link

beckdac commented Apr 2, 2014

Hi,
I'm trying to use the flasher app with your modified optiboot for over the air flashing of an AVR. When I run the flasher.hex on my atmega328p, I get the SREG message which repeats every few seconds, something like:

SREG: 0x0002, MCUCR: 0x0000 , our addr: sl0

Maybe it is resetting? I run the flasher.hex overtop your modified optiboot boot loader. Scoping the I/O lines to nRF24L01+ I can see typical behavior for the setup. With passthrough.hex running and in minicom, I can delay the reset by pushing characters. Interestingly, the I/O lines to the radio are silent. I suppose I thought I would see them pulse as it tried to send something.

Any thoughts?

  • DB
@balrog-kun
Copy link
Owner

Hi, sorry for the slow response...
That hasn't happened to me, but I can imagine one possible cause: have you compiled the optiboot bootloader and flashed it onto this atmega328p? The thing is that this modified optiboot will reset the board every 4-5 seconds unless the application takes care of disabling the watchdog, and it would result in what you're seeing.

Personally I've only used the modified optiboot on the "remote" atmega, and standard optiboot on the "local" atmega, which runs flasher.hex. As a result I didn't think of disabling the watchdog inside flasher.hex but I'll be sure to modify it and upload the change to github on the next occasion.

Please let me know if you succeed in over-the-air flashing or if you hit any other issue, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants