Hmm....I just opened it up and turned it on now to see what it said (i left it off for a few days), i got a time of almost exactly six hours off. I am suspecting it might be a configuration issue now.

52

(8 replies, posted in Hardware)

Hey dwrob,

Sounds good! Let me know how it goes.

For the senoko, I think you need to tell the EEPROM that you have a senoko attached. That should allow your Novena to boot.  For any other problems, there are a few threads on here that can help you out.

The fact that the green LEDs come on means the senoko is working! Those green LEDs are a battery level gauge, and tell you how much charge the senoko has. If one of the LEDs were blinking while you had the power plugged in, that means it is charging the battery.

53

(8 replies, posted in Hardware)

dwrob,

That is actually a pretty easy fix! For sourcing the new part: here is where you can find the BOM: http://www.kosagi.com/w/index.php?title … ign_Source

I did a bit of looking and I think this is the part, but I would check yourself: https://www.digikey.com/product-detail/ … D/3880323). Any maker place should be able to help you get it soldered (I would imagine Seattle has a maker space).

If you want someone to do it for you, I can talk to the guy I worked with to figure out the problems on my senoko board to see how much he would be willing to fix it for (I am thinking he would do it for the ~$20 range). He replaced the gas gauge on my senoko and does outstanding work. I am in the US.

On a side note, what is wrong with the Senoko board?

54

(55 replies, posted in Hardware)

Unfortunately, I am now at an issue where the battery board can and will discharge, but will not charge. If I plug in AC power, it goes to a current of 0 mA. The Senoko can tell that AC is being plugged in and unplugged.

EDIT: This appears to be normal behavior. After I discharged the battery for a while longer, the battery started charging (when you plug it in, it takes up to 30 seconds for the stats command to show it is charging).

With 4.4, I do not have the time has changed issue anymore (I think part of my issue was the problem with the senoko). However, I turned it off on Sunday and back on Tuesday, and the clock said it was still Sunday (ntp was block on the Internet connection I am on).

Is this expected behavior?

56

(55 replies, posted in Hardware)

I think I have fixed the issue on it. I have been working with a guy at my school that specializes in battery board design. I have a few notes from him that would be helpful for the future:

-  With this Gas Gauge type, the cells must be connected in a certain order, which is as follows: GND, Cell 1, Cell 2, Cell 3, and Cell 4 (if there is one). Then you can connect the larger power molex connector.

- If you are having an issue where the board is refusing to charge or discharge the battery, the cells may be uneven. If they are uneven beyond a certain point (40-100 mV is the point, I am not sure yet), the board assumes the battery is dead and won't charge them.

- There is enough current from the cells that there can be an arc, and this can damage the gas gauge. if there is a revisiion, he recommends some sort of circuit so it won't arc like that.

In my board, I think the connector was damaged and did not provide the right power to the gas gauge. This eventually damaged the IC and I had to replace the gas gauge and the connector.

57

(55 replies, posted in Hardware)

It is one from crows supply.

Do you remember which resistor it was?

58

(55 replies, posted in Hardware)

So what I have learned:

If I leave my laptop unpowered for a long time (think days), the gas gauge comes back to life. I am able to use the battery as normal, but it only lasts for 15 minutes and then goes back into the error 0xfe000000 mode. I have to repeat that.

59

(55 replies, posted in Hardware)

I am unfortunately getting a new error...

When I do stats, I get this:

stats
Manufacturer:       error 0xFE000000
Part name:          error 0xFE000000
Firmware version:   error 0xFE000000
Config version:     error 0x1000000
State:              error 0xFE000000
Time until full:    error 0xFE000000
Time until empty:   error 0xFE000000
Chemistry:          error 0xFE000000
Serial number:      error 0xFE000000
Cycle count:        error 0xFE000000
Battery health:     error 0xFE000000
Wake current:       error
Charge:             error 0xFE000000
Max capacity:       error 0xFE000000
Design capacity:    error 0xFE000000
Temperature:        2184.5 C
Voltage:            error 0xFE000000
Current:            error 0xFE000000
Average current:    error 0xFE000000
Target voltage:     error 0xFE000000
Target current:     error 0xFE000000
Number of cells:    error 0x1000000
Cell 1 voltage:     error 0xFE000000
Cell 2 voltage:     error 0xFE000000
Cell 3 voltage:     error 0xFE000000
Cell 4 voltage:     error 0xFE000000
Charge status:      0x5555
    Charging allowed?   yes
    Can suspend?        suspended
    Can precharge?      no
    Can maintenance?    yes
    Temperature limit?  no
    Temperature limit?  yes
    Can fastcharge?     no
    Pulse charging?     yes
    Pulse disable CHG?  no
Cell balancing?     in-progress
    Precharge timeout?  no
    Fastcharge timeout? yes
    Overcharge OV?      no
    Overcharge OC?      yes
    Overcharge?         no
    Battery empty?      yes
Alarms:
    TERMINATE CHARGE ALARM
    OVER TEMP ALARM
    REMAINING TIME ALARM
Charge state:
    Battery discharging/relaxing
    Battery fully discharged
STATUS ERROR CODE: 0x5
Unable to read safety alerts
Unable to read safety status

Trying to reboot, I get this:

ch> gg reboot
Rebooting the gas gauge chip... Error: FE000000

Trying the flash program from pelrun, I get this

# ./flash xobs-gg.dfi 
Flash length: 2048
Erasing rows 0-1...
Retrying erase...
Retrying erase...
(It happens a lot of times...)
Retrying erase...
Flash verify failed, try running this again.

It seems the gas gauge is in a permanent failure mode, and I have no idea how to fix it (outside of replacing it).

Are there any thoughts?

EDIT: I feel like I have a streak of once I post up my issue on this board, the answer magically comes to me. it turns out that I needed to manually push the "prime" button.

As for why that happened in the first place, the connection issues I thought I solved are not solved. So I need to fix some connections on the battery cells.

60

(39 replies, posted in Software)

Hey All,

One other thing I created for this installer (it's not on the image):

https://github.com/chris4795/novena-kernel-backup

Whenever the kernel is updated (or installed), the current uInitrd, zimage, and novena.dtb are renamed to *.recovery* . That way, if the kernel installation messed up for any reason, you can just press the 'user' button and it will boot up with the previous kernel configuration.

It will work whether you added the microsd card as /boot in fstab, or decided to leave it unmounted.

EDIT (7:12 PM EST): I updated the file, so in the unlikely event that you used it within the first 40 minutes of this post being here, please update to the newest file. It has a bit better file handling.

61

(13 replies, posted in Hardware)

zwick wrote:
bunnie wrote:

No particular recommendation about the keyboard. xobs has his favorite, I have mine. I'm using a Thinkpad Bluetooth keyboard, Lenovo FRU P/N 03X8697, and with the recent patch to Debian Jessie it seems to be working much better than before, although I literally installed it a few hours ago so I'll know more about that later on.

However, you're going to want a regular USB keyboard and mouse around to set up your bluetooth keyboard, so at the very least you'll want one of those around. Novena works with any standard HID device.

Did you have to do anything special (xinput, udev, hal, etc) in order to get the TrackPoint on this keyboard to work with the Novena? I have paired my keyboard and can type and the function keys work as expected, but the TrackPoint and the mouse buttons do nothing. xev doesn't show any output for them either.

Hello,

I have no had any of those problems with the bluetooth keyboard

62

(39 replies, posted in Software)

You're welcome! I hope it was useful.

63

(39 replies, posted in Software)

Here is the uploaded installer image:

https://drive.google.com/folderview?id= … XJvLWNQMTA

The sha512 hash is

5a1a6c834ad4e315084b8051d7f8b4ac09df0936b6921e44c7424d4ae669310b65fa8846df057876a5f1a19654a886dfb2f61dda208061a3390cd7fc10d78780

IAW with the GPLv2, here is the source code:
https://github.com/chris4795/novena-debian-installer

64

(39 replies, posted in Software)

Hey Sourcerer,

I will do that! I am making a new one with a couple of other changes. As soon as that is done, I will post the file.

65

(4 replies, posted in Software)

xobs,

One other note, in working with the installer, I noticed that the standard armmp Debian linux-images depend on

- libuuid-perl
- linux-base
- initramfs-tools

But linux-image-novena does not. I could not find where you have a script for building this package. Where would that be?

66

(39 replies, posted in Software)

Hey Sourcerer,

I made a bunch of upgrades to the installer, and make a new image for it! I made a pull request to merge it with your installer.

What would be the easiest way for me to send the image to you?

Or could we host is on the novena repo?

Good Afternoon,

I am on 4.4 and the issue is still there. Whenever I attempt to reboot, this error comes up. The only way I can fix the issue is to disconnect power and the battery.

EDIT: It seems that the hardware clock was somehow reset the beginning of time. I fixed it by setting the time with ntp (install ntp) and then issing this command:

#hwclock -w

But this seems to only be a temporary fix. Something keeps resetting it.

68

(4 replies, posted in Software)

Good Morning xobs,

What I can do is modify the script so that the backup kernels will not be in the /boot partition of the flash storage (I saw that they go into /usr/share/linux-novena , perhaps put the backups into their so one can just copy and paste old kernels back into boot in case something goes wrong)

I also fixed a couple of the scripts in debian-support, The scripts don't work for anything other than 3.19, so I fixed it to work with any kernel.

I found that in github and I will post my changes.

69

(11 replies, posted in Software)

Hello!

Yes, 2d acceleration is working!

I installed xorg-novena, xserver-xorg-video-armada, xserver-xorg-video-armada-etanviv and added this to my xorg.conf:

Section "Device"
    Identifier "novena"
    Driver "modesetting"
    Option "kmsdev" "/dev/dri/card0"
    Option "SWcursor" "true"
    BusID "platform:sys/devices/soc0/imx-drm.20/drm/card0"
EndSection

After that, try playing a video. assuming ti plays right, you have 2d acceleration working.

EDIT: With the 4.4 kernel, I don't appear to need the xorg.conf file.

Good Evening xobs,

I wanted to make the kernel updates "safer" in which the zimage, uimage, and the .dtb files are backed up in case the kernel update somehow goes wrong and makes the system unbootable (I have had a couple of issues with that).

If i wanted to submit those scripts, how would I go about doing that?

Thanks!

71

(55 replies, posted in Hardware)

Unfortunately, I tried that with no success. I am suspecting one of the chips failed.

With "gg chg +", I have been able to turn on the charge FET (according to stats), but I still get 0 mA for current.

I have access to a lab that I can change out the chips, so I am going to try to change out the ICs that are the gas gauge, ARM, battery charger, and the voltage overprotection circuit ( one at a time, I suspect it is either the gas guage or the battery charger that is acting up so I am going to try that first)

EDIT: It turns out it was an issue with the battery itself, not the board. I fixed the issue with the battery and my senoko works

72

(55 replies, posted in Hardware)

Xobs,

You were right, the power in the senoko was off. I was able to install 'firmware-senoko' and it told me it is up to date.

However, when I ran info, I got this:

ch> info
Kernel:       3.0.0dev
Compiler:     GCC 4.9.2
Architecture: ARMv7-M
Core Variant: Cortex-M3
Port Info:    Advanced kernel mode
Platform:     STM32F10x Performance Line Medium Density
Board:        Senoko STM32F1
Build time:   Aug 12 2015 - 17:13:27

The senoko.hex file said it was modified on Dec 9 2015, so I wanted to confirm I am not getting anything strange.

The battery has normal voltages, but while it is plugged in, the stats still says "Normal Discharge", but the chg command says the charge thread is running:

ch> stats
Manufacturer:       Texas Inst.
Part name:          bq20z95
Firmware version:   0x150
Charge FET:         off
Discharge FET:      off
State:              normal discharge
Time until full:    65535 minutes
Time until empty:   65535 minutes
Chemistry:          LION
Serial number:      0x0001
Cycle count:        6
Battery health:     32%
Charge:             77%
Max capacity:       1593 mAh
Design capacity:    5067 mAh
Temperature:        24.4 C
Voltage:            11909 mV
Current:            0 mA
Average current:    0 mA
Target voltage:     0 mV
Target current:     0 mA
Number of cells:    3 cells
Cell 1 voltage:     3739 mV
Cell 2 voltage:     4076 mV
Cell 3 voltage:     4094 mV
Cell 4 voltage:     0 mV
Charge status:      0x0
    Charging allowed?   yes
    Can suspend?        no
    Can precharge?      no
    Can maintenance?    no
    Temperature limit?  no
    Temperature limit?  no
    Can fastcharge?     no
    Pulse charging?     no
    Pulse disable CHG?  no
    Cell balancing?     no
    Precharge timeout?  no
    Fastcharge timeout? no
    Overcharge OV?      no
    Overcharge OC?      no
    Overcharge?         no
    Battery empty?      no
Alarms:
    TERMINATE CHARGE ALARM
    TERMINATE DISCHARGE ALARM
Charge state:
    Battery initialized
    Battery discharging/relaxing
No errors detected
No safety alerts
No safety status messages
ch> chg
Charger information:
        Charge thread:    running
        Manufacturer ID:  0x0040
        Device ID:        0x0007
        Current:          1024 mA
        Voltage:          12592 mV
        Input:            3328 mA
Command usage:
  chg set [c] [v] [[i]]  Set charge current to c mA @ v mV
  chg input [i]          Set max input AC current to [i] mA
  chg pause              Pause charge control
  chg resume             Resume charge control

Also to note: I tried "gg chg +" to force it to charge, but after doing that and running "stats", it still showed the charge FET as off.

73

(55 replies, posted in Hardware)

Also, on a whim, I reinstalled firmware-senoko. I got this error:

Setting up firmware-senoko (2.3.3-r1) ...
Error: Read failed
Error: Read failed
/var/lib/dpkg/info/firmware-senoko.postinst: 14: /var/lib/dpkg/info/firmware-senoko.postinst: arithmetic expression: expecting primary: " * 256 + "
dpkg: error processing package firmware-senoko (--configure):
 subprocess installed post-installation script returned error exit status 2

74

(55 replies, posted in Hardware)

Manoj or Velerio,

Where you able to solve your problems with the senoko? Yesterday, i Had the same issue of there it would go between 0 mV for Cell 1 and 57 V or 8V for cells 2 and 3.

Rightnow it seems to have found my battery, but it refuses to use the battery.

This is the output of my stats:

ch> stats
Manufacturer:       Texas Inst.
Part name:          bq20z95
Firmware version:   0x150
Charge FET:         off
Discharge FET:      off
State:              normal discharge
Time until full:    65535 minutes
Time until empty:   65535 minutes
Chemistry:          LION
Serial number:      0x0001
Cycle count:        6
Battery health:     98%
Charge:             95%
Max capacity:       4955 mAh
Design capacity:    5067 mAh
Temperature:        24.8 C
Voltage:            12334 mV
Current:            0 mA
Average current:    0 mA
Target voltage:     0 mV
Target current:     0 mA
Number of cells:    3 cells
Cell 1 voltage:     4109 mV
Cell 2 voltage:     4111 mV
Cell 3 voltage:     4114 mV
Cell 4 voltage:     0 mV
Charge status:      0x0
    Charging allowed?   yes
    Can suspend?        no
    Can precharge?      no
    Can maintenance?    no
    Temperature limit?  no
    Temperature limit?  no
    Can fastcharge?     no
    Pulse charging?     no
    Pulse disable CHG?  no
    Cell balancing?     no
    Precharge timeout?  no
    Fastcharge timeout? no
    Overcharge OV?      no
    Overcharge OC?      no
    Overcharge?         no
    Battery empty?      no
Alarms:
    TERMINATE CHARGE ALARM
    TERMINATE DISCHARGE ALARM
Charge state:
    Battery initialized
    Battery discharging/relaxing
No errors detected
No safety alerts
No safety status messages
ch> 

But when I run chg, I get:

ch> chg
Charger information:
        Charge thread:    running
        Manufacturer ID:  0x0040
        Device ID:        0x0007
        Current:          1024 mA
        Voltage:          12592 mV
        Input:            3328 mA
Command usage:
  chg set [c] [v] [[i]]  Set charge current to c mA @ v mV
  chg input [i]          Set max input AC current to [i] mA
  chg pause              Pause charge control
  chg resume             Resume charge control

So to me it looks like it sees the battery and is running the charging thread, but it is not actually charging the battery or using it.

75

(54 replies, posted in Hardware)

Hello,

Would it be too late to get in for one?