I'll keep it as short as possible, but please inquire about any missing info. if you can help. I paid a company in an Asian country I'll leave nameless to develop a product for me. I provided the block diagram and which IC's and controller I thought were best and they went to work. A Year and a half latter, many headaches and BS excuses, and a super slow work pace, our relationship was destroyed.
I negotiated the database (Gerber, schematic, BOM, and firmware) and now am left on my own to put it together. I already noticed that the BOM is missing the part numbers, and that leaves me wondering about the firmware.
I just today received the generic Nu-Link programmer and have a development board with the same controller as the one on my device (N76E003AT20). I have been trying to flash the firmware to the dev. board with no success.
The database came complete with the firmware in assembly, and a HEX file. I followed some of the how to's and get to where I'm trying to "build" and get error "C:\KEIL_V5\C51\INC\NUVOTON\N76E003.H(265): error A10: ATTEMPT TO DEFINE AN ALREADY DEFINED SYMBOL"...I found a post on here where a nice gent. explained that's probably because of a redundant file or something of the sort, but I've hit a wall....for the moment at least.
Specific instructions on the the best way to achieve the objective is extremely appreciated. Best to load the HEX file directly or try to "build" it from the assembly written firmware? how to execute the better option please?
I'm in over my head for sure, but I've been here before and I just don't quite.
Thank you Kindly!
I looked the part up, and it seems that the N76E003AT20 is an 8051 family part. This is probably an easier task than one of the ARM parts. Regarding the flashing, does the debugging software talk to the Nu-Link and if so, does the Nu-Link recognize the microcontroller?
Regarding the code, do you know whether or not they actually used the Keil development environment?
Grant, Thank you for your time. Not sure what IDE they used, I asked but never got an answer. when I try to configure the Nu-Link programmer, I get the following....My computer recognized and installed it fine.
Grant, Thank you for your time. Not sure what IDE they used, I asked but never got an answer. when I try to configure the Nu-Link programmer, I get the following....My computer recognized and installed it fine.C:\Users\Eaglefox\Downloads\Nu-Link_Keil_Driver_V3.08.7313r.zip --- Error: failed to execute 'C:\Users\Eaglefox\Downloads\Nu-Link_Keil_Driver_V3.08.7313r.zip '
Rebuild target 'Target 1'
A51 MACRO ASSEMBLER V18.104.22.168 - SN: Eval Version
COPYRIGHT ARM Germany GmbH 2016
"C:\Keil_v5\C51\BIN\A51.EXE" "disda2.asm" SET (SMALL) DEBUG PRINT(.\Listings\disda2.lst) OBJECT(.\Objects\disda2.obj) EP
A51 FATAL ERROR -
ERROR: FILE DOES NOT EXIST
Target not created.
Build Time Elapsed: 00:00:00I guess I'm not setting up the file correctly.
Is disda2.asm in the same folder/directory as startup.a51?
As far as I can tell it is, I've changed the name to disda3 in attempts there after
I suggest moving the files off the desktop. Something like C:\Projects\disda3 . And then show us what project files are in it. See if you can get a whole screen capture of the build result and the directory/folder in Windows (explorer or whatever).
Another thing you can try is to build an example that comes with the Keil package.
I moved the folder to my C drive not sure why it's still showing up on my desktop. All the tutorials I saw put them on the desktop, but maybe I'll start from scratch with a folder in C. I emailed the folks at Nuvoton, but I'll just keep hacking at it till something or someone breaks. Thx again.
Contacted Nuvoton, they sent me documents in Chinese, much like the developers, it's like a one handed clap. What color is the sky you might ask, My cousin Skyler speaks good English might be the answer you get after 2 weeks. My mind is literally numb. Is there a GeekSquad type service for embedded MCU's? or an enterprising soul out there willing to donate or tender a few minutes of phone consult? I used to test sat.signals a while back, it involved a lot of using a loader to flash the EEPROM, this is not much different just the process/sequence is unfamiliar to me.
I could try and build the project from the files if you want. At least that would tell you that you have all the correct pieces (or not).
Success! For the benefit of those who may stumble upon this thread and wonder who won? man or machine?
I won, finally!!! special Thanks to Grant for taking the time to try. Ended up finding an ICP tool from NUVOTON that was much closed to the loaders I'm used to, pretty straight forward and batabing bataboom!!! I even tried it on one of the prototypes and it recognized right away that it was locked.