dearsky/pico-fido
1
0
Fork 0
Code Issues 46 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

Code base for esp32s3 #103

New Issue
Open
opened 2025-01-30 09:35:05 +08:00 by kingsmen732 · 4 comments
kingsmen732 commented 2025-01-30 09:35:05 +08:00 (Migrated from github.com)
Copy Link

Codebase for esp32S3

  • I wanted to have the esp codebase for esp32 architecture so i can try some experiments on top of it .

Plans to integrate Fingerprint stack

  • essentially for user presence in biometric
  • makes more safer 2 factor authentication
# Codebase for esp32S3 - I wanted to have the esp codebase for esp32 architecture so i can try some experiments on top of it . ## Plans to integrate Fingerprint stack - essentially for user presence in biometric - makes more safer 2 factor authentication
polhenarejos commented 2025-01-31 19:03:41 +08:00 (Migrated from github.com)
Copy Link

Don't understand this issue.

Don't understand this issue.
kingsmen732 commented 2025-02-01 19:51:13 +08:00 (Migrated from github.com)
Copy Link

this is not a issue , we are not able to label this as question. So coming back to the point, where do we have the esp32s3 codebase which is being flashed currently through the web.
I was planning to increase some functionality available in the esp32 like adding up userpresence using fingerprint module which is fido compliant.

this is not a issue , we are not able to label this as question. So coming back to the point, where do we have the esp32s3 codebase which is being flashed currently through the web. I was planning to increase some functionality available in the esp32 like adding up userpresence using fingerprint module which is fido compliant.
ihavetenfingers commented 2025-02-04 15:16:20 +08:00 (Migrated from github.com)
Copy Link

this is not a issue , we are not able to label this as question. So coming back to the point, where do we have the esp32s3 codebase which is being flashed currently through the web. I was planning to increase some functionality available in the esp32 like adding up userpresence using fingerprint module which is fido compliant.

It is in the same source files as everything else if you read it.. not separated from the 2040 code.

Here: https://github.com/polhenarejos/pico-fido

> this is not a issue , we are not able to label this as question. So coming back to the point, where do we have the esp32s3 codebase which is being flashed currently through the web. I was planning to increase some functionality available in the esp32 like adding up userpresence using fingerprint module which is fido compliant. It is in the same source files as everything else if you read it.. not separated from the 2040 code. Here: https://github.com/polhenarejos/pico-fido
kingsmen732 commented 2025-02-11 05:01:53 +08:00 (Migrated from github.com)
Copy Link

this is not a issue , we are not able to label this as question. So coming back to the point, where do we have the esp32s3 codebase which is being flashed currently through the web. I was planning to increase some functionality available in the esp32 like adding up userpresence using fingerprint module which is fido compliant.

It is in the same source files as everything else if you read it.. not separated from the 2040 code.

Here: https://github.com/polhenarejos/pico-fido

So for rpi2040 the flashing method is different but for the esp instance there is only web flashing methodology. I wanted to do offline flashing of esp by my serial. Did you do that methodology ?, cause i want to seek for debugging dev tools to listen for board signals. I need the code separate for it so i will be able to help contribute BIO-FIDO on it.
@polhenarejos @ihavetenfingers

> > this is not a issue , we are not able to label this as question. So coming back to the point, where do we have the esp32s3 codebase which is being flashed currently through the web. I was planning to increase some functionality available in the esp32 like adding up userpresence using fingerprint module which is fido compliant. > > It is in the same source files as everything else if you read it.. not separated from the 2040 code. > > Here: https://github.com/polhenarejos/pico-fido So for rpi2040 the flashing method is different but for the esp instance there is only web flashing methodology. I wanted to do offline flashing of esp by my serial. Did you do that methodology ?, cause i want to seek for debugging dev tools to listen for board signals. I need the code separate for it so i will be able to help contribute BIO-FIDO on it. @polhenarejos @ihavetenfingers
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/pico-fido#103
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?