NLNetfound
/
dsendcomm
2
2
Fork 0
Código Incidencias 82 Pull Requests 0 Lanzamientos 5 Wiki Actividad
Etiquetas Hitos
Nueva incidencia

#148 Using openocd(1) on SAMR34 is undocumented

Abierta
abierta hace 4 años por Michael Schloh von Bennewitz · 1 comentarios
Michael Schloh von Bennewitz comentado hace 4 años

Using openocd(1) on SAMR34 is undocumented

Problem environment

GDB programming tools like openocd(1) allow portable use when programming chip flash regions.

Steps to reproduce

  1. Refer to online documents
  2. Locate programming information

Expected result

There is a sample command line informing of the proper syntax to program firmware to the flash storage of a SAMR34 chip using openocd(1) software.

Actual result

No documentation exist for programming flash storage using openocd(1) software.

Workaround

Use the Microchip Studio built in programming tool, as documented in Microchip web sites.

Severity level

This is low priority because project requirements do not mandate a training path towards chip programming.

# Using openocd(1) on SAMR34 is undocumented ## Problem environment GDB programming tools like *openocd(1)* allow portable use when programming chip flash regions. ## Steps to reproduce 1. Refer to online documents 1. Locate programming information ## Expected result There is a sample command line informing of the proper syntax to program firmware to the flash storage of a SAMR34 chip using *openocd(1)* software. ## Actual result No documentation exist for programming flash storage using *openocd(1)* software. ## Workaround Use the Microchip Studio built in programming tool, as documented in Microchip web sites. ## Severity level This is **low priority** because project requirements do not mandate a training path towards chip programming.
Michael Schloh von Bennewitz ha añadido la etiqueta
enhancement
hace 4 años
Michael Schloh von Bennewitz ha añadido la etiqueta
question
hace 4 años
Michael Schloh von Bennewitz ha añadido esto al hito Postproject catchall hace 4 años ' issues.change_milestone_at=`modificó el hito de %!s(MISSING) a %!s(MISSING) %!s(MISSING)
Michael Schloh von Bennewitz comentado hace 4 años
Propietario

This is partially solved by 062c71b.

This is partially solved by 062c71b.
Inicie sesión para unirse a esta conversación.
Ninguna Rama/Etiqueta especificada
Ramas Etiquetas
Etiquetas
Limpiar etiquetas
bug
Something is not working derivative
Regarding a derived product duplicate
This issue or pull request already exists enhancement
New feature help wanted
Need some help invalid
Something is wrong question
More information is needed wontfix
This won't be fixed
Sin etiquetas
bug
derivative
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Limpiar Milestone
Sin Milestone
Postproject catchall
Asignados
Limpiar asignados
No asignados
1 participantes
Fecha de vencimiento

Sin fecha de vencimiento.

Dependencias

Esta incidencia actualmente no tiene ninguna dependencia.

Escribir Vista previa
Cargando…
Cancelar
Guardar
Aún no existe contenido.
Eliminar la rama con el nombre '%!s(MISSING)'

Eliminar una rama es permanente. NO PUEDE deshacerse. ¿Continuar?

No
Sí