-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenprog with JN516x #3
Comments
To avoid confusion, you are using the "-c ftdi" connection of jenprog, right? If so, according to the JN-RD-6021 doc you need to change the pins that are used jenprog -c ftdi --reset-pin=13 --spimiso-pin=14 -s returns some useful results. If all else fails you can of cours just measure the Let me know if that worked. On Wed, Feb 12, 2014 at 10:34:30AM -0800, riccardosabatini wrote:
|
Hi, |
jenprog does work under linux. However I never worked with the jn5168, so you On Thu, Nov 20, 2014 at 12:16:04PM -0800, usmanadeel wrote:
Embedded Sensing Systems - TU Darmstadt Tel.: +49 6151 16 75023 |
Thanks. |
Hi ! |
@JulesThuillier I Have reimpliented the jenprog with c, now it support jn5168, you chould referr to https://github.com/pengphei/jennic-utils.git . I hope it will work |
Dear,
I'm trying to use the jenprog with a devkit board for the JN5168. Ftdi drivers and utilities are working good (I can access the FTDI Model and ID with no problem), but the communication is broken.
In particular, after some debugging, I notices the talk function in the ftdi modules fails for the read_len == ans_len condition. It seems in fact that the chip spits out some non-sensical (w.r.t. the Bootloader manual) results.
I went through all the doc of Jennic (NXP) and it seems the bootloader for the JN5168 is the same as for the older chips supported by jenprog.
If it can be of any help to better understand, I'm using the dev board DK4 and the procedure to put the chip in configuration mode consist in pressing the pwr button once while the FlashBoot (windows) is launched, after this everything works ... in windows.
Very much help for any suggestion, and thanks for the great work
R
The text was updated successfully, but these errors were encountered: