Won't flash using IDE 2.2.1 #312

bmentink · 2024-02-21T21:41:41Z

Hi, I am trying to program LGTBF328P - MiniEVB nano board. I get the following error:

avrude error: protocol expects OK byte 0x10 but got 0xfc
avrdude error: unable to read signature data for part ATmega328P, rc=-3
avrdude error: unable to read signature data, rc=-3
Failed uploading: uploading error: exit status 1

Any idea's ?

The text was updated successfully, but these errors were encountered:

bmentink · 2024-02-21T22:07:39Z

Update: I wonder if I got some bad boards. I have 5 boards, 3 program ok, 2 won't.

hmeijdam · 2024-02-21T22:37:01Z

You could try to use one of the working ones for attempting to burn the bootloader on one of the defective boards.

bmentink · 2024-02-22T00:07:51Z

You could try to use one of the working ones for attempting to burn the bootloader on one of the defective boards.

Can you show me how to connect the SPI pins? It is not clear from the board which ones connect to MOSI and MISO, CLK etc, seems to have a pin missing. Cheers (can only see SWC and SWD)

hmeijdam · 2024-02-22T06:35:47Z

You need LGTISP to burn the bootloader via SWD and SWC.

bmentink · 2024-02-22T19:13:56Z

Thanks, will give it a try.

bmentink · 2024-02-22T20:03:07Z

I loaded up a good LGT board with the LGTISP.ino sketch ok. However, when I go to program the bootloader to another LGT board connected with SWC,SWD etc it gives error.

avrdude error: programmer is out of sync
 ***failed;
avrdude error: programmer is out of sync
 ***failed;

I am somewhat confused as the instructions say to use AVR ISP as programmer, even though there is an " LGTSWD markii as ISP" option ??

hmeijdam · 2024-02-22T20:43:56Z

There is a LarduinoISP sketch amongst the examples. Did you compile and load that one?
It also mentions how to wire it up. You need to look at the right column under LGT8FX8P:

The LGTSWD Mark II is this one. Probably not what you have.

bmentink · 2024-02-22T21:41:13Z

You linked the github site, it only shows these files, no examples. Please be specific.

You show me an Arduino as ESP, in your example above, I am using LGT to program LGT. ARe the pin connections the same?

hmeijdam · 2024-02-22T21:45:36Z

This is the example I mean. It comes with this core.

bmentink · 2024-02-22T21:46:56Z

Right, you did not link that initially, now I understand. BUt the question remains, If I use LGT as ESP are the pin connections the same?

hmeijdam · 2024-02-22T21:49:22Z

LGT as ISP has these connections.

If that does not work, I will dig up my LGT's and hook them up. Has been a few years since I had to bootload one.

bmentink · 2024-02-22T21:49:46Z

I don't have those examples .... maybe I have the wrong LGT library?

I got the library from here:
https://raw.githubusercontent.com/dbuezas/lgt8fx/master/package_lgt8fx_index.json

bmentink · 2024-02-22T21:53:32Z

LGT as ISP has these connections. If that does not work, I will dig up my LGT's and hook them up. Has been a few years since I had to bootload one.

I don't have those names, please give the corresponding D8,D10) etc ..

hmeijdam · 2024-02-22T21:56:47Z

Well.... you are posting your question in the Github forum of the core I am using, so I assumed you will have the LarduinoISP as well. But apparently not

Here are the pins

bmentink · 2024-02-22T21:57:48Z

I have added the core I am using above, is it incorrect?

hmeijdam · 2024-02-22T21:58:33Z

That's the one I use.

bmentink · 2024-02-22T21:59:05Z

That's the one I use.

So why no examples?

hmeijdam · 2024-02-22T22:00:32Z

I honestly have no clue.
Here is the LarduinoISP sketch


// 20 July 2020 David Buezas
// - Bundled and added menu utility
// * When uploading to the programmer,
//   select in the menu: Tools/Arduino as ISP/SERIAL_RX_BUFFER_SIZE to 250)
// * Before using the ISP to program another board, 
//   connect (in the ISP board) the reset pin to gnd via a capacitor,
//   or (at your own risk) short reset to vcc.
// https://github.com/dbuezas/lgt8fx/
//
// author : brother_yan (https://github.com/brother-yan/LGTISP)
//
// LarduinoISP for LGT8FX8P series
// Project fork from
//    - ArduinoISP version 04m3
// Copyright (c) 2008-2011 Randall Bohn
// If you require a license, see 
//     http://www.opensource.org/licenses/bsd-license.php
//
// This sketch turns the Arduino into a AVRISP
// using the following arduino pins:
//
// pin name:    Arduino:          LGT8FX8P:
// slave reset: 10:               PC6/RESET 
// SWD:         12:               PE2/SWD
// SWC:         13:               PE0/SCK
// Make sure to 
// Put an LED (with resistor) on the following pins:
// 9: Heartbeat   - shows the programmer is running
// 8: Error       - Lights up if something goes wrong (use red if that makes sense)
// 7: Programming - In communication with the slave
//
// 23 July 2011 Randall Bohn
// -Address Arduino issue 509 :: Portability of ArduinoISP
// http://code.google.com/p/arduino/issues/detail?id=509
//
// October 2010 by Randall Bohn
// - Write to EEPROM > 256 bytes
// - Better use of LEDs:
// -- Flash LED_PMODE on each flash commit
// -- Flash LED_PMODE while writing EEPROM (both give visual feedback of writing progress)
// - Light LED_ERR whenever we hit a STK_NOSYNC. Turn it off when back in sync.
// - Use pins_arduino.h (should also work on Arduino Mega)
//
// October 2009 by David A. Mellis
// - Added support for the read signature command
// 
// February 2009 by Randall Bohn
// - Added support for writing to EEPROM (what took so long?)
// Windows users should consider WinAVR's avrdude instead of the
// avrdude included with Arduino software.
//
// January 2008 by Randall Bohn
// - Thanks to Amplificar for helping me with the STK500 protocol
// - The AVRISP/STK500 (mk I) protocol is used in the arduino bootloader
// - The SPI functions herein were developed for the AVR910_ARD programmer 
// - More information at http://code.google.com/p/mega-isp

// LarduinoISP for LGTF8FX8P Series
#include "swd_lgt8fx8p.h"

#if SERIAL_RX_BUFFER_SIZE < 250 // 64 bytes的RX缓冲不够大
#error : Please change the macro SERIAL_RX_BUFFER_SIZE to 250 (In the menu: Tools/Arduino as ISP/SERIAL_RX_BUFFER_SIZE)
#endif

#define RESET	10
#define LED_HB    9
#define LED_ERR   8
#define LED_PMODE 7
#define PROG_FLICKER true

#define HWVER 3
#define SWMAJ 5
#define SWMIN 1

// STK Definitions
#define STK_OK      0x10
#define STK_FAILED  0x11
#define STK_UNKNOWN 0x12
#define STK_INSYNC  0x14
#define STK_NOSYNC  0x15
#define CRC_EOP     0x20 //ok it is a space...

void pulse(int pin, int times);

void setup() 
{
  SWD_init();
  Serial.begin(115200);
  
  //pinMode(LED_PMODE, OUTPUT);
  //pulse(LED_PMODE, 2);
  //pinMode(LED_ERR, OUTPUT);
  //pulse(LED_ERR, 2);
  //pinMode(LED_HB, OUTPUT);
  //pulse(LED_HB, 2);
}

uint8_t error=0;
uint8_t pmode=0;

// address for reading and writing, set by 'U' command
int address;
uint8_t buff[256]; // global block storage

#define beget16(addr) (*addr * 256 + *(addr+1) )
typedef struct param {
  uint8_t devicecode;
  uint8_t revision;
  uint8_t progtype;
  uint8_t parmode;
  uint8_t polling;
  uint8_t selftimed;
  uint8_t lockbytes;
  uint8_t fusebytes;
  uint8_t flashpoll;
  uint16_t eeprompoll;
  uint16_t pagesize;
  uint16_t eepromsize;
  uint32_t flashsize;
}  parameter_t;
parameter_t param;

// this provides a heartbeat on pin 9, so you can tell the software is running.
uint8_t hbval=128;
uint8_t hbdelta=8;
void heartbeat() 
{
  if (hbval > 192) hbdelta = -hbdelta;
  if (hbval < 32) hbdelta = -hbdelta;
  hbval += hbdelta;
  analogWrite(LED_HB, hbval);
  delay(40);
}

void loop(void) 
{
  // is pmode active?
/*
  if (pmode) digitalWrite(LED_PMODE, HIGH); 
  else digitalWrite(LED_PMODE, LOW);
  // is taddress an error?
  if (error) digitalWrite(LED_ERR, HIGH); 
  else digitalWrite(LED_ERR, LOW);
*/
  // light the heartbeat LED
  //heartbeat();
  if (Serial.available()) 
    avrisp();
}

uint8_t getch() {
  while(!Serial.available());
  return Serial.read();
}

void fill(int n) 
{
  for (int x = 0; x < n; x++) {
    buff[x] = getch();
  }
}

#define PTIME 30
void pulse(int pin, int times) 
{
  do {
    digitalWrite(pin, HIGH);
    delay(PTIME);
    digitalWrite(pin, LOW);
    delay(PTIME);
  } 
  while (times--);
}

void prog_lamp(int state) 
{
  if (PROG_FLICKER)
    digitalWrite(LED_PMODE, state);
}

void empty_reply() 
{
  if (CRC_EOP == getch()) {
    Serial.print((char)STK_INSYNC);
    Serial.print((char)STK_OK);
  } 
  else {
    error++;
    Serial.print((char)STK_NOSYNC);
  }
}

void breply(uint8_t b) 
{
  if (CRC_EOP == getch()) {
    Serial.print((char)STK_INSYNC);
    Serial.print((char)b);
    Serial.print((char)STK_OK);
  } 
  else {
    error++;
    Serial.print((char)STK_NOSYNC);
  }
}

void get_version(uint8_t c) 
{
  switch(c) {
  case 0x80:
    breply(HWVER);
    break;
  case 0x81:
    breply(SWMAJ);
    break;
  case 0x82:
    breply(SWMIN);
    break;
  case 0x93:
    breply('S'); // serial programmer
    break;
  default:
    breply(0);
  }
}

void set_parameters() 
{
  // call this after reading paramter packet into buff[]
  param.devicecode = buff[0];
  param.revision   = buff[1];
  param.progtype   = buff[2];
  param.parmode    = buff[3];
  param.polling    = buff[4];
  param.selftimed  = buff[5];
  param.lockbytes  = buff[6];
  param.fusebytes  = buff[7];
  param.flashpoll  = buff[8]; 
  // ignore buff[9] (= buff[8])
  // following are 16 bits (big endian)
  param.eeprompoll = beget16(&buff[10]);
  param.pagesize   = beget16(&buff[12]);
  param.eepromsize = beget16(&buff[14]);

  // 32 bits flashsize (big endian)
  param.flashsize = buff[16] * 0x01000000
    + buff[17] * 0x00010000
    + buff[18] * 0x00000100
    + buff[19];

}

void start_pmode(uint8_t chip_erase) 
{
  digitalWrite(RESET, HIGH);
  pinMode(RESET, OUTPUT);
  delay(20);
  digitalWrite(RESET, LOW);
  
  SWD_init();
  SWD_Idle(10);
  
  pmode = SWD_UnLock(chip_erase);
  if (!pmode)
    pmode = SWD_UnLock(chip_erase);
}

void end_pmode()
{
  SWD_exit();
  pmode = 0;
  
  digitalWrite(RESET, HIGH);
  pinMode(RESET, INPUT);
}

void universal() 
{
  fill(4);

  if(buff[0] == 0x30 && buff[1] == 0x00) {
    switch(buff[2]) {
    case 0x00:
      breply(0x1e);
      break;
    case 0x01:
      breply(0x95);
      break;
    case 0x02:
      breply(0x0f);
      break;
    default:
      breply(0xff);
      break;  
    }
  } else if(buff[0] == 0xf0) {
    breply(0x00);
  } else {
    breply(0xff);
  }
}

void write_flash(int length) 
{
  fill(length);
  if (CRC_EOP == getch()) {
    Serial.print((char) STK_INSYNC);
    Serial.print((char) write_flash_pages(length));
  } 
  else {
    error++;
    Serial.print((char) STK_NOSYNC);
  }
}

uint8_t write_flash_pages(int length)
{
  int addr = address / 2;
  /*
  lgt8fx8p的flash是按4字节编址的，而avr是按2字节编址的，avrdude传过来的是按2字节编址的address
  avrisp()函数中也有证实：
  case 'U': // set address (word)
  */
  
  SWD_EEE_CSEQ(0x00, addr);
  SWD_EEE_CSEQ(0x84, addr);
  SWD_EEE_CSEQ(0x86, addr);
  
  for (int i = 0; i < length; i += 4)
    {
      SWD_EEE_Write(*((uint32_t *)(&buff[i])), addr);
      ++addr;
    }
  
  SWD_EEE_CSEQ(0x82, addr - 1);
  SWD_EEE_CSEQ(0x80, addr - 1);
  SWD_EEE_CSEQ(0x00, addr - 1);
  
  return STK_OK;
}

#define EECHUNK (32)
uint8_t write_eeprom(int length) 
{
  // address is a word address, get the byte address
  int start = address * 2;
  int remaining = length;
  if (length > param.eepromsize) {
    error++;
    return STK_FAILED;
  }
  while (remaining > EECHUNK) {
    write_eeprom_chunk(start, EECHUNK);
    start += EECHUNK;
    remaining -= EECHUNK;
  }
  write_eeprom_chunk(start, remaining);
  return STK_OK;
}

// write (length) bytes, (start) is a byte address
uint8_t write_eeprom_chunk(int start, int length) 
{
  // this writes byte-by-byte,
  // page writing may be faster (4 bytes at a time)
  fill(length);
  prog_lamp(LOW);
  for (int x = 0; x < length; x++) {
    int addr = start+x;
    // do e2prom program here
    // donothing for lgt8fx8d series
    delay(45);
  }
  prog_lamp(HIGH); 
  return STK_OK;
}

void program_page() 
{
  char result = (char) STK_FAILED;

  // get length
  uint16_t length = getch() << 8;
  length += getch();

  char memtype = getch();
  // flash memory @address, (length) bytes
  if (memtype == 'F') {
    write_flash(length);
    return;
  }
  if (memtype == 'E') {
    result = (char)write_eeprom(length);
    if (CRC_EOP == getch()) {
      Serial.print((char) STK_INSYNC);
      Serial.print(result);
    } 
    else {
      error++;
      Serial.print((char) STK_NOSYNC);
    }
    return;
  }
  Serial.print((char)STK_FAILED);
  return;
}

char flash_read_page(int length)
{
  int addr = address / 2;
  /*
  lgt8fx8p的flash是按4字节编址的，而avr是按2字节编址的，avrdude传过来的是按2字节编址的address
  avrisp()函数中也有证实：
  case 'U': // set address (word)
  */
  
  SWD_EEE_CSEQ(0x00, 0x01);
  
  uint32_t data;
  for (int i = 0; i < length; ++i)
    {
      if (i % 4 == 0)
        {
          data = SWD_EEE_Read(addr);
          ++addr;
        }
      Serial.print((char)((uint8_t *)&data)[i % 4]);
    }
  
  SWD_EEE_CSEQ(0x00, 0x01);
  
  return STK_OK;
}

char eeprom_read_page(uint16_t length) 
{
  // address again we have a word address
  uint16_t start = address * 2;
  for (int x = 0; x < length; x++) {
    uint16_t addr = start + x;
    // do ep2rom read here
    // but donothing for lgt8fx8d series (by now...)
    Serial.print((char) 0xff);
  }
  return STK_OK;
}

void read_page() 
{
  char result = (char)STK_FAILED;

  uint16_t length = getch() << 8;
  length += getch();
  char memtype = getch();
  if (CRC_EOP != getch()) {
    error++;
    Serial.print((char) STK_NOSYNC);
    return;
  }
  Serial.print((char) STK_INSYNC);

  if (memtype == 'F') result = flash_read_page(length);
  if (memtype == 'E') result = eeprom_read_page(length);
  Serial.print(result);
  return;
}

void read_signature() 
{
  if (CRC_EOP != getch()) {
    error++;
    Serial.print((char) STK_NOSYNC);
    return;
  }
  
  Serial.print((char) STK_INSYNC);
  Serial.print((char) 0x1e);
  Serial.print((char) 0x95);
  Serial.print((char) 0x0a);
  Serial.print((char) STK_OK);
}

//////////////////////////////////////////
//////////////////////////////////////////


////////////////////////////////////
////////////////////////////////////
volatile uint8_t chip_erased;
int avrisp() 
{ 
  uint8_t data, low, high;
  uint8_t ch = getch();
  switch (ch) {
  case '0': // signon
    error = 0;
    empty_reply();
    break;
  case '1':
    if (getch() == CRC_EOP) {
      Serial.print((char) STK_INSYNC);
      Serial.print("AVR ISP");
      Serial.print((char) STK_OK);
    } else {
      error++;
      Serial.print((char) STK_NOSYNC);
    }
    break;
  case 'A':
    get_version(getch());
    break;
  case 'B':	// optional for lgt8fx8d series
    fill(20);
    set_parameters();
    empty_reply();
    break;
  case 'E': // extended parameters - ignore for now
    fill(5);
    empty_reply();
    break;

  case 'P':
    if (pmode) {
      pulse(LED_ERR, 3);
    } else {
      start_pmode(0);
      chip_erased = 0;
    }
    if (pmode)
      empty_reply();
    else
      {
        if (CRC_EOP == getch()) {
          Serial.print((char)STK_INSYNC);
          Serial.print((char)STK_FAILED);
        } 
        else {
          error++;
          Serial.print((char)STK_NOSYNC);
        }
      }
    break;
  case 'U': // set address (word)
    address = getch();
    address += (getch() << 8);
    empty_reply();
    break;
  case 0x60: //STK_PROG_FLASH
    low = getch();
    high = getch();
    empty_reply();
    break;
  case 0x61: //STK_PROG_DATA
    data = getch();
    empty_reply();
    break;
  case 0x64: //STK_PROG_PAGE
    if (!chip_erased)
      {
        error = 0;
        end_pmode();
        start_pmode(1);
        chip_erased = 1;
      }
    program_page();
    break;
  case 0x74: //STK_READ_PAGE 't'
    read_page();    
    break;
  case 'V': //0x56
    universal();
    break;
  case 'Q': //0x51
    error=0;
    end_pmode();
    empty_reply();
    break;
  case 0x75: //STK_READ_SIGN 'u'
    read_signature();
    break;
    // expecting a command, not CRC_EOP
    // this is how we can get back in sync
  case CRC_EOP:
    error++;
    Serial.print((char) STK_NOSYNC);
    break;

    // anything else we will return STK_UNKNOWN
  default:
    error++;
    if (CRC_EOP == getch()) 
      Serial.print((char)STK_UNKNOWN);
    else
      Serial.print((char)STK_NOSYNC);
  }
}

bmentink · 2024-02-22T22:06:48Z

THanks, these are the examples I have:

So just put the above code on the LGT board that has to act as ISP, right?
In that case, what is the LGTISP.ino I put on from github do then?

hmeijdam · 2024-02-22T22:10:43Z

LGTISP.ino may be a newer or older version. I have not used it myself as I usually grab my dedicated SWDICE programmer.

The sketch I just uploaded here I have used a while back. But I just found my box with LGT's so let me try if it still works.

bmentink · 2024-02-22T22:23:21Z

Thanks will wait. Meantime I tried connecting the programming pins at the end of the board to the target board pins, but that did not work either. So Still unsure of pin connections.

hmeijdam · 2024-02-22T22:25:54Z

Just tested and works fine

First burn the LarduinoISP.ino to your working Nano

Then hook it up like

// pin name:    Programmer NANO         Target LGT8FX8P:
// reset:                   10:            PC6/RESET 
// SWD:                     12:           PE2/SWD
// SWC:                     13:           PE0/SCK

Keep AVRISP as programmer and press "burn Bootloader"

I burned it to a "promini style" LGT board, as my second Nano has no pinheaders yet. But you will select the board you have to get the bootloader that goes with your board.

bmentink · 2024-02-22T22:33:40Z

First burn the LarduinoISP.ino to your working Nano

I keep teling you, I am not using an Arduino Nano as ISP, I am using LGT Nano, do I still use pins 10,12,13 on the ISP side ?

hmeijdam · 2024-02-22T22:34:14Z

I also used LGT Nano

bmentink · 2024-02-22T22:37:11Z

Well I get this using those pinouts:

avrdude error: programmer is not responding
avrdude warning: attempt 1 of 10: not in sync: resp=0x00
avrdude warning: ignoring mismatch in unused bits of lock
        (device 0xff != input 0x3f); to prevent this warning set
        unused bits to 1 when writing (double check with datasheet)
avrdude error: programmer is not responding
avrdude warning: attempt 1 of 10: not in sync: resp=0x00
avrdude warning: ignoring mismatch in unused bits of lock
        (device 0xff != input 0x3f); to prevent this warning set
        unused bits to 1 when writing (double check with datasheet)

bmentink · 2024-02-22T22:38:47Z

I have to go out, will pick this up later. Thanks for the help.

hmeijdam · 2024-02-22T22:39:53Z

This is how I wired it up

bmentink · 2024-02-22T22:40:51Z

I have exactly that!

bmentink · 2024-02-23T00:46:14Z

I'm back now if you have any more suggestions. I am using LarduinoISP.ino, but LGTISP.ino does not work either.

dbuezas · 2024-02-23T07:50:08Z

Have you seen the tutorial in this repo?
https://github.com/dbuezas/lgt8fx/blob/master/lgt8f/libraries/LarduinoISP/readme.md

wollewald · 2024-06-06T19:29:54Z

Hi @Devilscave, I can reproduce the issue with the purple LQFP32. It does not work as a programmer, at least when following the standard procedure. I tried burning the bootloader on a green LQFP32 as well as on a purple LQFP32 using the purple LQFP32 as programmer. I also tried a purple LQFP48 as a programmer and that worked perfectly. So, it is a specific problem of the purple LQFP32.

I don't know what the problem is and how to fix it. My gut feel says it is related to the CH9340C USB-to-TTL Chip on the purple LQFP32 board and how it is wired. But I have no proof for that.

dbuezas · 2024-06-06T20:53:40Z

That's very odd.
isp.zip
I don't have a purple LQFP32 to test it my self, would you test this isp code with it?
The only difference is that the pins change:

SWD -> PC5 - A5
RESET -> PC4 - A4
SWC -> PC3 - A3

Since the pcb layout is different, I wonder if some pin is either not connected or has some unwanted pulldown or capacitive coupling with the xtal on PB6 and 7 (same port as the original isp code uses).

(I use the ISP like this so that the pins between programmer and programmed are aligned)

Regarding the USB to TTL chip, what is your hunch based on? the serial part should only affect pc <-> isp, and that obviously works if serial burning works.

Also, it may be worth trying setting the clock differently, e.g using the external one.

Devilscave · 2024-06-06T22:53:53Z

I have to try it again now, because yesterday I must have shot something on one of the purple LGTs, it works to load sketches on it, but runs much too fast and the sketches only make measurements, it almost seems to me as if the bootloader is wrong.

wollewald · 2024-06-07T17:00:06Z

Hi @dbuezas , I have tried your sketch and get the same error like before:

In order to confirm that I have not wired something wrongly, I have done the same with green LQFP32 and it worked.

Then I found something interesting. I changed back to the purple LQFP32 and uploaded the standard LArduinoISP sketch. Then I connected the purple LQFP32 to a USB-to-TTL Adapter instead of the PC directly:
VCC -> VCC
GND -> GND
RX -> TX
TX -> RX

It looked like this:

All the rest is set up as one would do using the normal procedure. And it works! I was able to burn the the bootlader and to upload sketches using the purple LQFP32 as a programmer. I really think the problem is the CH9340C Chip.

There are also purple LQFP32 boards available which other USB-to-TTL Chips than the CH9340C. I have order some from China, so it will take a while until I can test. If anyone reads this and has such a board, it would be great to know if these can be used as programmer.

@Devilscave, can you check which chip you have on your board?

Devilscave · 2024-06-07T17:30:01Z

@Devilscave, can you check which chip you have on your board?

I also have the CH340C on all the purple ones.
The green LGT has the HT42B534-2

wollewald · 2024-06-07T18:05:33Z

@Devilscave , thank you. But I don't have the CH340C, I have the CH9340C. It's a small difference in the name, but these are dfferent chips. Sorry, but can you double check?
@Devilscave , danke. Aber ich habe nicht den CH340C, ich habe den CH9340C. Es ist nur ein kleiner Unterschied im Namen, aber es sind verschiedene Chips. Entschuldigung, aber können Sie das noch einmal überprüfen?

dbuezas · 2024-06-07T18:08:27Z

That's very interesting, i really didn't expect that. Serial communication works normally at any baudrate otherwise?

Übrigens, lass uns auf Englisch bleiben, das hier wird wahrscheinlich von anderen auch gelesen.

Or maybe the reset line is held too long? I think that's controlled by the usb-ttl chip. The capacitor trick could serve to test that.

Devilscave · 2024-06-07T18:30:18Z

@Devilscave, danke. Aber ich habe nicht den CH340C, sondern den CH 9 340C. Es ist ein kleiner Unterschied im Namen, aber das sind unterschiedliche Chips. Tut mir leid, aber können Sie das noch einmal überprüfen?

No it's a CH340C

Übrigens, lass uns auf Englisch bleiben, das hier wird wahrscheinlich von anderen auch gelesen.

Sorry, I worked with a page translator and he simply translated my English answer as well. I've changed it.

wollewald · 2024-06-07T18:41:26Z

@Devilscave , thank you. Helpful information. Then it's something else on the board. Yesterday I tried to use a purple LQFP48 board which uses a CH340C hip like yours and that work as a programmer.

@dbuezas , usually I take a 10µF capacitor. I also tried a 100 µF and a 100 nF capacitor and no capacitor. It all didn't work. Or what do you mean with capacitor trick?

dbuezas · 2024-06-07T19:21:11Z

Yes I meant a cap at the reset pin. I thought maybe the programmer maybe was reset for too long by dtr.

I burnt my isp without bootloader to avoid accidentally flashing it instead of the target device. I wonder if the purple ones come with a different bootloader?

wollewald · 2024-06-07T19:37:54Z

I have just burned a new bootloader on the purple LQFP32 and tried again to use it as programmer. But no success. Maybe I will have a good idea over night.

dbuezas · 2024-06-09T19:22:08Z

Could it be that the serial doesn't work well at the specific baudrate used when isp programming?

wollewald · 2024-06-10T14:38:42Z

At least worth a try to change the baud rate. I am quite busy currently and so I cannot promise trying this within the next days.
It might also help to compare the circuit diagrams of the purple LQFP32 board vs the green one and the purple LQFP48 board which do work. Unfortunately, I have not found circuit diagrams for the purple boards.

wollewald · 2024-06-17T21:37:01Z

I have some news. I have now received purple LQFP32 boards with a CH340C from two different shops and both work as programmers as they should. I double checked that the purple board with the CH9340C still did not work. Since @Devilscave tried a board with a CH340C chip, which did not the difference between the CH340C and the CH9340C should not be the reason. I have burned on all boards the same bootloader, so this is also not the reason. I have no idea yet why some of these boards do not work. Maybe a bad batch of the PCBs? Here's a photo of one board that is working and another which does not. I can't see obvious differences:

So, good that this is no general issue, but bad that we don't know why the problematic boards behave like they do and how to identify them (before you buy them!).

Devilscave · 2024-06-18T10:21:35Z

@wollewald Maybe you could, since you own both boards and they seem to be identical, simply swap the CH340 chips across. If the error moves, it is the chip, if it stays, it is the board.
If the non-functioning one happens to be the top one on yout picture, I almost assume it is a fake ch9340, the labeling is different and much worse executed. This often tests for counterfeits as the manufacturers usually have very good labeling.
EDIT: ahh i see thet the upper one is the CH9340C
But change it across.

wollewald · 2024-06-18T11:51:29Z

Hi @Devilscave , good idea. Let me check if get the chip desoldered and transferred without damage.

Devilscave · 2024-06-18T20:27:17Z

here the Pinouts from the two ICs

LaZsolt · 2024-06-19T04:11:16Z

I have an idea about the problematic serial converter chip, CH9340C.
The pin 8 low level selecting the dedicated baud rate mode, whatever that means.
So lift up pin 8 from PCB for deselect the dedicated baud rate mode.

wollewald · 2024-06-19T07:28:50Z

Hi @LaZsolt , you are the hero! I cut the pin 8 and then it worked. To be absolutely sure, I reconnected pin 8, then it did not work, disconnected again and it worked. And it does not seem to have negative side effects. I can still upload sketches to the board when not used as programmer. Cutting the pin is not the nicest workaround, but at least we know what that issue is. However, this is only an explanation for the boards that I used. It does not explain why the board of @Devilscave does not work as a programmer since his one has a CH340C chip. @Devilscave , do you still know where you ordered your board? I would buy a board from the same source and hope that they have not changed the design meanwhile.

Devilscave · 2024-06-19T19:04:16Z

@wollewald
I have just checked my source of supply, (aliexpress) )unfortunately the shop no longer has an LGT8 in its range.

dbuezas · 2024-06-20T11:56:27Z

@Devilscave there's dozens of other shops offering them, they're all fine :)

Devilscave · 2024-06-20T13:55:29Z

@dbuezas I know, I don't want to buy any, but Wollewald asked for my source of supply.

wollewald · 2024-06-28T19:20:24Z

Things are getting weird. I have tested some additional purple LQFP32 boards and found different behaviour when trying to use them as programmers. In summary I found four types:

Boards with CH9340C:
a) Some work if you cut pin 8
b) For others this workaround does not help
Boards with CH340C:
a) Some just work without any trick
b) Others don't

The behavior of each board is reproducible, i.e. it's no a random effect. In some cases I get the "out of sync" meassage, in other cases AVRDUDE reads 0x0000 as device signature. All boards look identical apart from the USB-to-TTL chip. I burned the bootloader on all boards but this had no effect. Whenever I tested several boards from one shop, they all behaved the same. I.e. this is not a random phenomenon.

dwillmore · 2024-06-28T21:30:01Z

Are these with a known bootloader?

…

On Fri, Jun 28, 2024 at 3:20 PM Wolfgang (Wolle) Ewald < ***@***.***> wrote: Things are getting weird. I have tested some additional purple LQFP32 boards and found different behaviour when trying to use them as programmers. In summary I found four types: 1. Boards with CH9340C: a) Some work if you cut pin 8 b) For others this workaround does not help 2. Boards with CH340C: a) Some just work without any trick b) Others don't The behavior of each board is reproducible, i.e. it's no a random effect. In some cases I get the "out of sync" meassage, in other cases AVRDUDE reads 0x0000 as device signature. All boards look identical apart from the USB-to-TTL chip. I burned the bootloader on all boards but this had no effect. Whenever I tested several boards from one shop, they all behaved the same. I.e. this is not a random phenomenon. — Reply to this email directly, view it on GitHub <#312 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPEX7EK6DPSPXBSHZ22MXTZJWZRDAVCNFSM6AAAAABDTZ5F42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGQ4TMMJWGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

wollewald · 2024-06-29T10:18:04Z

I have tested the boards with the bootloader which was on them when they arrived but I also burned the bootloader again using a green board as bootloader. This made no difference.

dbuezas · 2024-06-29T10:36:16Z

I really don't get this. Once the isp starts up the communication between the pc and programmer is serial, and programmer <=> target is just gpio.

we know its not the bootloader (you flashed it, and the reset cap inhibits dtr resets)
we know it's not the gpio (you tested my variant with different gpios)
we know it's not UART in general (otherwise they wouldn't be flasheable via serial)
we know it's not the clock speed since the isp is flashed to use the internal clock (confirm?)

The only candidates left I see are specific baud rates, and here there's something odd:

Boards.txt sets isp flashing baudrate to 19200: https://github.com/dbuezas/lgt8fx/blob/master/lgt8f/programmers.txt#L13
The ISP code sets baudrate to 115200: https://github.com/dbuezas/lgt8fx/blob/master/lgt8f/libraries/LarduinoISP/examples/LarduinoISP/LarduinoISP.ino#L88

That shouldn't work at all in any board (I don't understand how it works on any board), it may be worth trying:

That the malfunctioning boards can do serial at 19200
Changing those baud rate configurations to other values
Making those baud rate match

SuperUserNameMan · 2024-06-29T12:20:33Z

Duno if it may help, but I remember that CHxxx UART IC that use internal clock source instead of an external crystal tends to fail more often (at certain baudrate speed).

dbuezas · 2024-06-29T13:04:08Z

Interesting, then changing the baud rate in platforms.txt and the isp code may work

wollewald · 2024-06-30T09:34:41Z

I spent some hours playing with different baudrates with no success. I will stop here, at least for the moment.

dbuezas · 2024-06-30T10:14:56Z

A mystery.
Since the baudrate in the isp code and platforms.txt don't match, There may be something else setting the baudrate

Won't flash using IDE 2.2.1 #312

Won't flash using IDE 2.2.1 #312

Comments

bmentink commented Feb 21, 2024

bmentink commented Feb 21, 2024

hmeijdam commented Feb 21, 2024

bmentink commented Feb 22, 2024 • edited Loading

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

bmentink commented Feb 22, 2024 • edited Loading

hmeijdam commented Feb 22, 2024 • edited Loading

bmentink commented Feb 22, 2024 • edited Loading

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024 • edited Loading

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024 • edited Loading

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024 • edited Loading

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

bmentink commented Feb 22, 2024

hmeijdam commented Feb 22, 2024

bmentink commented Feb 22, 2024

bmentink commented Feb 23, 2024 • edited Loading

dbuezas commented Feb 23, 2024

wollewald commented Jun 6, 2024

dbuezas commented Jun 6, 2024 • edited Loading

Devilscave commented Jun 6, 2024

wollewald commented Jun 7, 2024

Devilscave commented Jun 7, 2024 • edited Loading

wollewald commented Jun 7, 2024

dbuezas commented Jun 7, 2024

Devilscave commented Jun 7, 2024 • edited Loading

wollewald commented Jun 7, 2024

dbuezas commented Jun 7, 2024

wollewald commented Jun 7, 2024

dbuezas commented Jun 9, 2024

wollewald commented Jun 10, 2024

wollewald commented Jun 17, 2024

Devilscave commented Jun 18, 2024 • edited Loading

wollewald commented Jun 18, 2024

Devilscave commented Jun 18, 2024

LaZsolt commented Jun 19, 2024

wollewald commented Jun 19, 2024

Devilscave commented Jun 19, 2024

dbuezas commented Jun 20, 2024

Devilscave commented Jun 20, 2024

wollewald commented Jun 28, 2024

dwillmore commented Jun 28, 2024 via email

wollewald commented Jun 29, 2024

dbuezas commented Jun 29, 2024 • edited Loading

SuperUserNameMan commented Jun 29, 2024 • edited Loading

dbuezas commented Jun 29, 2024

wollewald commented Jun 30, 2024

dbuezas commented Jun 30, 2024

bmentink commented Feb 22, 2024 •

edited

Loading

bmentink commented Feb 22, 2024 •

edited

Loading

hmeijdam commented Feb 22, 2024 •

edited

Loading

bmentink commented Feb 22, 2024 •

edited

Loading

bmentink commented Feb 22, 2024 •

edited

Loading

hmeijdam commented Feb 22, 2024 •

edited

Loading

bmentink commented Feb 22, 2024 •

edited

Loading

bmentink commented Feb 23, 2024 •

edited

Loading

dbuezas commented Jun 6, 2024 •

edited

Loading

Devilscave commented Jun 7, 2024 •

edited

Loading

Devilscave commented Jun 7, 2024 •

edited

Loading

Devilscave commented Jun 18, 2024 •

edited

Loading

dbuezas commented Jun 29, 2024 •

edited

Loading

SuperUserNameMan commented Jun 29, 2024 •

edited

Loading