avr-objcopy: 'aes.elf': No such file ...

Go To Last Post
68 posts / 0 new

Pages

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

i did compile but it still not run OK.

Last Edited: Wed. Jan 15, 2020 - 10:28 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

PM sent!

/Jakob Selbing

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No mention of what currency the offer is in. It could be rupiah for all we know!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It does say $500 - but I guess the are various different "dollars" around ...

 

The vagueness doesn't inspire confidence to make a bid.

 

Perhaps would be better on somewhere like  https://www.freelancer.com/  or  https://www.peopleperhour.com/  ... ?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm guessing the $ means USD and not the former imperial currency of my country, now used only in Cape Verde...

 

Anyway, I can't help, I'm not familiar with the software you are using to even make an assessment of the costsad

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

i can Pay in BTC is the fastest Online payment this days.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When i Flash The IC atmega168/328 The Led's are two led one red and one blue are always on, when i restart the device but the blue LED Must flash like after 1,2 seconds after for 1, or 2 seconds, i think the reason is one is the byte are not at the correct address are 3 files .eep(1kb) .hex (intel)(38kb) and .rom(91kb) then i make the botloader but i don't think i make the bootloader correct, is posible the fuses can be the problem to.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just for the benefit of whoever attempts to do this it seems OP has dug up some ancient old piece of crap called AVRUB which is a bootloader (japanese with little sensible documentation) that purports to be able to do AES. It seems the PC side of things are written in a dialect of Pascal called Lazarus. There could be all types of issue at either end (encrypting the image or the bootloader decrypting/flashing).

 

If I was doing this I would forget that completely. Go to Microchip, get their app note and code for their own AES bootloader (which includes source for the PC tool) and concentrate on making that work. You are far more likely to find knowledge/support for the use of that than this anonymous other software.

 

EDIT: That is.

 

https://www.microchip.com/wwwAppNotes/AppNotes.aspx?appnote=en591242

 

having sid that there also seem so tbe:

 

http://atmel-studio-doc.s3-website-us-east-1.amazonaws.com/webhelp/GUID-E67D40A5-DD02-4379-82B4-9BE2A7E7BEA0-en-US-2/index.html

 

Not entirely clear (without further study) how "AVR231" and "AN2462" are related. Perhaps they are really two names for the same thing??

Last Edited: Wed. Jan 15, 2020 - 01:34 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
AVRUB

Presumably not this:  https://www.avrub.com/

 

But this:  https://sourceforge.net/projects/avrub/

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you for your time, i will Not try any more as it looks like is true what clawson mentioned the hex file it generate is like incomplete or invalid i think.

 

Thank you everyone for trying to help.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
But this
Yes, the latter. For those interested/concerned take a read through this entire thread and see how it progressed. I did find that if I got the latest issue of AVRUB (5.2) from Sourceforge that AS7 was happy to build it without error but there is some configuring to be done (bootcfg.h). You need to switch on encryption (Decrypt = 1) and you need to pick the algorithm (presumably AES-128 or AES-256) then you need to ensure that the "key" array is actually set to your AES key. But this is when your fun may start as you need something to build the encrypted packages you will deliver to the bootloader and this is where the PC side Lazarus project comes in. Presumably you have to ensure it uses the same AES key and then you have to be able to build it after updating? That could be "fun". Now maybe "Lazarus" is something that's easy to install and use and building the PC app turns out to be easy. But if you hit an issue there you could find yourself all at sea!

 

PS Lazarus is this I guess:  https://www.lazarus-ide.org/

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


clawson wrote:
Perhaps they are really two names for the same thing??

I think so:

  • AVRxxx are the old Atmel names;
  • ANyyyy are the new Microchip names.

 

eg, 

 

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

the PC part use 32 digits to decrypt the downloaded File from the Memory and is one more Atmel Memory.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Lazarus  is ok is just 1234 and 32 digits written in the IC

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

inside bootldr.c

 

//=============================================================================
// Starts here!
//=============================================================================

/**
 *
 * The bootloader is disabled by default, so we can program the
 * firmware together with the bootloader and the device will
 * work.
 *
 * ACTIVATION:
 *  1. By writing the eeprom when programming the bootloader.
 *  2. When the app section fails the CRC check. This will also
 * hang the bootloader so it won't result in an endless loop
 * that rewrites the eeprom continuously (when the cable is not
 *  plugged in). This hang is in here because there is no more
 *  space to write any other instruction.
 *  3. By the application.
 *
 *  DEACTIVATION:
 *
 *  The bootloader can be deactivated after a successful
 *  programming.
 *
 *
 */

int main(void)
{
    /** seting up the reset pin is not really required because if
     *  the device is rebooting during firmware update, it can
     *  always be programed later; however it is a good idea to
     *  set set it in order to avoid troubles */
    PORTC = PORTC_VALUE;

    // enable pullup - give port time to settle
    busInit();

    // Loop forever (loops only if Application Section is damaged)
    for(;;)
    {
        if (eeprom_read_byte((uint8_t*)BOOTLOADER_FLAG_ADDR) == BOOTLOADER_FLAG_ENABLE)
        {
            loader();
        }

    #if defined(CRC_CHECK)
        // Check that the Application Section contents is undamaged
        // by calculating the CRC of the whole memory.
        {
            #ifndef RAMPZ
                uint16_t p = 0x000000;
            #else
                uint32_t p = 0x000000;
            #endif

            uint16_t crc = 0;

            do
            {
            #ifndef RAMPZ
                crc = CRC(crc, pgm_read_byte(p));
            #else
                crc = CRC(crc, pgm_read_byte_far(p));
            #endif
            }
            while (++p < MEM_SIZE);

            // Application Section damaged or forced into bootloader mode by connector
            //   -> do not jump to Reset Vector of the Application Section
            if(crc)
            {
                eeprom_write_byte((uint8_t*)BOOTLOADER_FLAG_ADDR, BOOTLOADER_FLAG_ENABLE);
                for(;;); /* hang to avoid executing invalid apps or rewrite eeprom when the cable is unplugged */
            }
        }
    #endif

        asm volatile ("jmp 0");
    }

}

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

you are right, the create folder is created to make the specific bootloader, and i think there is the problem,

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you all for help.

Pages