Objective Development Forums

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-12T16:29:44+02:00

Guessing Christian does not use avrStudio, as a setting changes was needed in the project settings. I stumbled on to it when I got curios and did a compile based on the makefile and the project settings. I then saw this.

-Wl,-section-start=.text=0x3800

but when compiling with makefile I saw

-Wl,--section-start=.text=7800

Then I though hmmmm.. maybe there is a place in the project setting for the address, and sure enough there is.

So what I set in the burn setting does not effect the build, I guess that makes sense... So thank you again Christian your thought was correct. 328p works just fine.

Statistics: Posted by ulao — Sun Sep 12, 2010 4:29 pm

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-03T15:33:34+02:00

Well I could not even get the second boot loader to work. I still need to find a better test. I'm not sure why USBaspLoader wont do a thing for me? Does not do a thing on a 168 also, just sits there. Any others out there?

The avr studio project settings are just the defaults nothing fancy. I set up the right chip and right speed and really no more then that. Although it work for the 168 so I'm not clear on how it would discriminate between the 328.

I tested the code on a 168p and it worked, so its just the 328 that is the problem.

--- ok If I change the code in USBaspLoader I do get unrecognized device, if I unplug it and plug it back in I get nothing. As soon as I make any change to the code and re-burn I get unrecognized device. <-- If that made no sense then you understood it perfectly. Are there any boot loaders with a make file or project file?

See anything wrong here?

When I try the makefile I get
usbdrv/usbdrvasm.o:usbdrv/asmcommon.inc:170: undefined reference to `usbTxStatus1'

Statistics: Posted by ulao — Fri Sep 03, 2010 3:33 pm

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-03T11:56:09+02:00

usbConnect() and usbDisconnect() are emulated when no pull-up pin is defined. That's OK.

Then, let me summarize: You can run any of the example apps on the board, but none of the boot loaders, even if you load them as app (not into boot space).

That's rather strange, because the driver is the same in all cases. I would guess that it's something in the build environment...

Statistics: Posted by christian — Fri Sep 03, 2010 11:56 am

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-02T17:23:21+02:00

huh, well I dont have avr dude but I tried to compile and run.

Guessing this would satisfy the check

#define bootLoaderCondition() (1)

as per the info

If a certain hardware condition is met (this condition can be configured, e.g. a jumper), the boot loader waits for data on the USB interface and loads it into the remaining part of the flash memory. If the condition is not met, control is passed to the loaded firmware.

I dont think the device is powering up. I dont see any new usb devices and dont see an unknown device. I'm just not failure with this loader. how can I wake it up? I had to change the usb pins in the config but still not having any luck. I also noticed they have the pull up define commented out, yet are using usb disconnect/connect. I'm not quite sure how that would work, so I set up the correct defines ( didnt help).

I also grabbed the latest bootloaderHid and I'm still having the same issues.

Statistics: Posted by ulao — Thu Sep 02, 2010 5:23 pm

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-01T16:43:14+02:00

Yes, it's code plus data, so it should fit. If it still fails when flashed to 0 with TEST_MODE defined, you can try to debug it with debug output on TxD. There is no code size limit when you flash it to address 0.

On the other hand: Have you tried other bootloaders, e.g. USBaspLoader?

Statistics: Posted by christian — Wed Sep 01, 2010 4:43 pm

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-01T16:13:36+02:00

2k as in Program and data together?

Code:

AVR Memory Usage
----------------
Device: atmega328p

Program:    1946 bytes (5.9% Full)
(.text + .data + .bootloader)

Data:         59 bytes (2.9% Full)
(.data + .bss + .noinit)

I removed all debug code to shrink it down a bit.

I did not see a define for TEST_MODE, but I do see the #if for it, so I set TEST_MODE 1 and tried to flash without the bootrst fuse bit. This did not seem to help, does this imply its related to code, since all other apps seem to flash correctly?

Statistics: Posted by ulao — Wed Sep 01, 2010 4:13 pm

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-01T11:58:18+02:00

The define in bootloadHID is "TEST_MODE". Did you check the over-all code size? It might exceed the 2k of the boot area.

Statistics: Posted by christian — Wed Sep 01, 2010 11:58 am

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-01T00:21:30+02:00

Sorry I'm using BootloadHID. I can use any v-usb example on the 328p just fine, only the bootloader gives me troubles. I didnt see NO_FLASH_WRITE in there.

Statistics: Posted by ulao — Wed Sep 01, 2010 12:21 am

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-01T00:17:54+02:00

You can first try to load it as normal application at address 0 instead of the boot area. Don't know which boot loader you use, but USBaspLoader has an optional define "NO_FLASH_WRITE". If you set it, it's compiled as normal application which can be loaded at address 0.

Statistics: Posted by christian — Wed Sep 01, 2010 12:17 am

Re: Atmega8535 OK / Atmega328p FAIL

2010-09-01T00:13:28+02:00

Well, thx for all the help Christian. I certainly understand things better now However I do not understand why every thing works when flash to a 168 and not a 328p.

I have the new code that handles the pico bug.
I have the right fuses FF,DA,DF. ( not 100% on the Brown-out but disabled works on 168 ( tried all other options ) )
Tried multiple chips.
Tried burning as if it were a 168 ( dont agree with that but didnt help )
BootRst is check ( at least this is needed for 168 )
Set MCU to 328p in project settings.
Didn't read any changes needed in the Bootloader code.

I continue to get usb device not recognized on this chip. Any more ideas?

Statistics: Posted by ulao — Wed Sep 01, 2010 12:13 am